What is Enso (ENSO) ?

2025-11-21

Enso is a decentralized Layer 1 network designed to simplify developers’ interactions with Smart Contracts across multiple blockchains, rollups, and appchains. It acts as a Coordination Layer, connecting Smart Contracts from different networks so developers can build cross-chain applications without dealing with complex technical details.

How Enso Works

Shared Network State

Enso maintains a shared network state, functioning like a global database that stores Smart Contract data from multiple blockchains and rollups in one place. This allows developers to access consistent information without connecting to each blockchain individually.

Each Smart Contract is recorded as an Entity, containing all necessary details to generate executable bytecode used by blockchains to process commands. Entities are also linked with their respective Chain IDs, so the system knows where each contract is deployed.

For example, Aave’s lending protocol on Ethereum is stored as a “Lend” entity. When a developer wants to interact with lending protocols across chains, Enso can automatically gather the required components from the shared network state and generate ready-to-use bytecode. This approach simplifies multi-chain development by transforming complex Smart Contract interactions into reusable standard components.

Enso Workflow


1. Intent Creation

Users or customers submit an Intent, specifying the desired outcome (e.g., token swap or lending) without defining the steps.

2. Action Contribution

Action Providers are developers who create or publish Smart Contract modules. They provide pre-built Actions that describe how to execute each step toward the desired outcome.

3. Pathfinding

Graphers analyze the shared state to combine relevant Actions and generate the most efficient bytecode.

4. Validation

Validators in the network verify the generated bytecode by simulating its execution in the network’s state to ensure correctness and safety.

5. Solution Selection

The network selects the most efficient code (e.g., best outcome, lowest cost) and discards less optimal solutions.

6. Execution

The final solution is executed for the user. Processing fees embedded in the bytecode are distributed to Graphers, Validators, and Action Providers in ENSO tokens.

Enso Use Cases

Enso can integrate with DeFi applications that require liquidity management, asset movement, and automation

DEX / Aggregators:
Reduce friction in liquidity provision with simple zaps, making position movement and liquidity adjustments easier.

Wallets:
Enable token swaps, cross-chain transfers, and direct access to DeFi earning opportunities.

Stablecoins:
Mint from a single origin and bridge across chains securely, enabling yield-bearing stablecoins without redeployment.

Vault Deposits:
Support deposits of any token and simplify asset movement between vaults while keeping funds productive.

Market Makers:
Facilitate market making, arbitrage, and automated liquidity pool balancing to maximize capital efficiency.



What ENSO Token Does

ENSO is the native token of the Enso protocol, with a maximum supply of 127,339,703 tokens. It is released gradually with controlled inflation that decreases over time and ends after 10 years. Key use cases include

Holders can stake ENSO to vote on protocol upgrades. Voting does not yield immediate rewards, and proposals must reach quorum to be effective, Stake ENSO to help validate and secure the network using Proof of Stake (PoS) and simulation tools, Holders can delegate staked tokens to Validators to earn a share of validation revenue without running validation nodes themselves.


Token Distribution

  • Investors: 31.84%

  • Team: 25%

  • Foundation: 21.5%

  • DAO: 15.16%

  • Coinlist: 5%

  • Advisors: 1.5%

Maximum Supply: 127.33M ENSO, Circulating Supply: 20.59M ENSO

Closing Thoughts

Enso is designed to simplify the development and connection of cross-chain applications by using Intent-based requests, allowing users to simply specify the desired outcome while the network handles all the execution steps.