Skip to main content
The Routes protocol is a small set of contracts deployed on every supported chain, plus a modular settlement layer the user picks at intent-creation time.

​
The contracts

​
The modular settlement layer

The Portal accepts any contract that implements the IProver interface. Six provers ship today; the user picks one per intent.

​
Information flow

Sequence of every contract call from intent publication to reward release: publishAndFund, lock reward, fulfill, execute route calls, emit and dispatch proof, withdraw, verify proof, release and transfer reward.

​
Design principles

Non-upgradable. The Portal has no proxy, no admin keys, no upgrade path. Audited once, valid forever. Stateless executor. The Executor has no persistent storage. Each intent’s calls run in isolation. A malicious call cannot corrupt Portal state. Per-intent vaults. Funding is a vanilla ERC-20 transfer to a CREATE2 address. Cold wallets, hardware devices, multisigs, exchanges, PSPs all participate without changes. Modular settlement. New messaging protocols plug in via IProver without changes to Portal, vaults, or solver tooling. Cross-VM. EVM, SVM, and TVM are first-class. Address fields use bytes32 to hold any chain’s address format.