Enso

• Name: Enso
• URL: https://www.enso.build/
• Category: onchain execution / intent-routing / DeFi workflow infrastructure
• Tags: ethereum-ecosystem
• Summary: Enso turns high-level DeFi intents into executable calldata. The product is a shared action graph plus operator-heavy routing and simulation, not some mystical abstraction layer. Useful when wallets, apps, or agents want broad venue coverage without integrating every contract stack themselves.
• What it does:
  • Maps isolated smart-contract interactions into reusable Actions and combines them into shareable Shortcuts for wallets, apps, agents, and other integrations
  • Converts high-level DeFi workflow specifications into runnable calldata through Route and Bundle APIs, including cross-chain routing and multi-step flows
  • Exposes protocol, network, aggregator, and project data APIs so integrators can build on top of a broad library of supported actions and venues
  • Operates a network model in which graphers seek efficient solutions and validators simulate and verify that generated calldata is executable and safe
  • Publishes SDKs, widgets, audit repositories, and an Ethereum transaction simulator through its public GitHub organization
• Key claims:
  • Homepage describes Enso as “the fastest way to build and launch onchain” and says every onchain interaction is mapped to a shared engine so developers do not need manual blockchain or smart-contract integrations
  • Official site claims more than 100 apps use Enso, more than 250 protocols are supported, more than 1,900 developers are building with it, transaction volume exceeds $1B, more than 240K accounts have been created, and more than 1.90M transactions have been settled
  • Get Started docs say “Enso Shortcuts convert high-level specifications of crosschain DeFi operations into runnable calldata” and distinguish optimized routing from custom bundled workflows
  • Network docs say validators secure the network by simulating generated calldata and proving it can be executed safely
  • Tokenomics docs describe ENSO as the native network token with 100,000,000 genesis supply and a capped inflation schedule that decays over time before ceasing
• Whitepaper: No single canonical whitepaper or litepaper was found during this pass. The strongest primary materials were Enso’s homepage, developer docs, tokenomics / network-participant docs, and public GitHub organization; see ../whitepapers/enso-primary-sources-2026-04-25.md.
• Sources:
  • https://www.enso.build/
  • https://docs.enso.build/
  • https://docs.enso.build/llms.txt
  • https://docs.enso.build/pages/build/get-started/overview
  • https://docs.enso.build/pages/network/network-participants/validators
  • https://docs.enso.build/pages/network/token
  • https://github.com/EnsoBuild

Internal linkages

• Keep this note on the strongest reads: across, socket, and erc-7683.
• Useful cut: Enso is route-and-calldata packaging, not the settlement rail underneath it.

Control / operating edge

• Contracts settle the result, but the leverage sits in action indexing, shortcut curation, simulation, validator policy, and route-default selection.

• The real questions are who decides which Actions and Shortcuts become canonical, how validators are chosen and paid, and how much opaque generated calldata an integrator is willing to inherit.

• Last reviewed: 2026-06-01 UTC