Enso

• Enso provides a single interface for reading from and writing to smart contracts across many blockchains.

• Developers describe an intended outcome and Enso resolves the route across protocols and chains.

• ENSO is used for transactions, rewards and governance.

• Supply allocated across community sale, ecosystem and contributors.

• Used to pay for network usage and reward action providers.

Pros:

• Removes substantial integration work for developers building multi-protocol applications.

• Intent-based routing rather than requiring explicit transaction construction.

• Used in production by teams shipping cross-chain products.

Cons:

• Abstraction layers add a dependency and a failure point between the application and the protocols.

• Revenue depends on developer adoption, which is slower than user adoption.

• Competes with both direct integration and other abstraction providers.

• Exposure to developer infrastructure rather than an end-user application.

• Intent-based execution is a direction much of the industry is moving toward.

• Weigh the dependency risk an abstraction layer introduces.

• A single endpoint for interacting with any protocol on any supported chain, replacing per-protocol integration work.

• Building an application that touches several protocols across several chains requires integrating each one separately.

• A shared abstraction layer collapses that into one interface, at the cost of trusting the layer.

• Founded by Connor Howe and Gorka Cesium.

• Backed by Polychain and Dialectic.

• A community sale was held ahead of launch, alongside ecosystem allocations.

• Abstraction layer failure affects every application depending on it.

• Developer adoption is slow and hard to forecast.

• Competition from direct integration and rival abstraction providers.

• Smart contract risk across many integrated protocols.