Epoch Protocol

• Name: Epoch Protocol
• URL: https://epochprotocol.xyz/
• Category: intent-solver coordination layer / account-abstraction automation infrastructure / cross-chain state-routing middleware
• Summary: Epoch is solver-orchestration middleware. The point is not just that it routes intents. Plenty of stacks do that. The point is that it moves control up into the layer that decomposes intents, chooses solver composition, watches conditions, and decides when execution is good enough to fire.
• What it does:
  • Lets users and dapps submit declarative intents with approvals, constraints, deadlines, triggers, optimization factors, and preferred solvers
  • Uses SIOs to break a user intent into sub-intents, query multiple solver modules, and assemble the best end-to-end state transition
  • Uses Hyperions as pluggable observers that monitor onchain and offchain state so intents can execute when specified conditions are met
  • Routes settlement through smart-contract wallets, plugins, hooks, registry/gatekeeper contracts, paymaster support, and ERC-4337-style bundling
  • Maintains permissioned liquidity pools intended to give near-instant destination-chain execution while source-chain assets remain escrowed until proofs and partner flows rebalance the system
  • Exposes an SDK and public GitHub surfaces for creating, signing, and submitting intents against the protocol
• Key claims:
  • The litepaper defines Epoch as an intent-solver coordination layer meant to hide chain, protocol, gas, and execution-path complexity from users and dapps
  • The docs are unusually explicit that the real product is the overseer/controller layer, not just a nicer route finder
  • SIOs are the main control surface: they deconstruct intents, query internal and external solvers, weigh partial state transitions, and assemble the final path
  • Node runners can tweak SIO logic or use their own business logic, which means orchestration policy is not a neutral constant
  • Hyperions extend the stack into condition-based automation by watching offchain and onchain state and only allowing execution when specified conditions are met
  • Epoch says funds remain non-custodial because SAFE smart-contract wallets hold assets while users or wallet owners remain the only signers
  • Registry/gatekeeper contracts, hooks, paymaster support, and permissioned liquidity pools show where proof rules, settlement policy, and liquidity relationships can centralize
  • The SDK exposes intent creation, nonce retrieval, signing, and submission against Epoch nodes, which reinforces that the node/operator layer is part of the actual product
• Whitepaper: The main current technical source is the official litepaper/docs stack at https://docs.epochprotocol.xyz/litepaper; no standalone local PDF was pulled in this pass. The strongest operational sources were the overview docs, litepaper, contracts docs, and public GitHub surfaces collected in ../whitepapers/epoch-protocol-primary-sources-2026-05-08.md.
• Sources:
  • https://epochprotocol.xyz/
  • https://docs.epochprotocol.xyz/
  • https://docs.epochprotocol.xyz/litepaper
  • https://docs.epochprotocol.xyz/litepaper?ask=What%20are%20Epoch%27s%20main%20components%20and%20how%20does%20solver%20coordination%20work%3F
  • https://docs.epochprotocol.xyz/litepaper?ask=How%20does%20Epoch%20keep%20user%20funds%20non-custodial%20and%20what%20on-chain%20contracts%20does%20it%20use%3F
  • https://docs.epochprotocol.xyz/epoch-overview.md
  • https://docs.epochprotocol.xyz/use-epoch-sdk/contracts.md
  • https://github.com/epochprotocol
  • https://github.com/epochprotocol/epoch-intents-sdk
  • https://raw.githubusercontent.com/epochprotocol/epoch-intents-sdk/main/README.md

Control surface

• The leverage sits in SIO logic, solver admission, Hyperion condition policy, permissioned liquidity access, and the proof / escrow rules around final settlement.

• That is the only read worth keeping. Epoch is not just another intent front end. It is orchestration middleware deciding how many lower-level components get composed on the user’s behalf.

• Last reviewed: 2026-06-15 UTC