iLayer for DeFi protocols, wallets and AI agents
Three industries, one Order struct. What a dex, a wallet and an agent each get from encoding their action as an intent.
/Blog.
Crosschain, explained one intent at a time.
Technical breakdowns, developer guides, ecosystem notes and releases from the iLayer team. Start with the Intent series, then follow the developer track when you are ready to integrate.
/01 · Posts.
Latest from the team.
16 posts across four tracks. Every post ends with what to read next.
Why Waku for the RFQ
A central quote server would have been easier. It would also have been a single point of failure, censorship and front-running. What Waku gives us instead.
How solvers fill orders and make money
The bots behind every fill: what they watch, how they quote, why they keep a single numeraire balance, and how they rebalance across chains.
Multi-token outputs: one order, three assets
Give SHIB, receive WBTC, WETH and DAI in the proportions you choose. How weighted outputs are encoded, validated and filled.
Example: a cross-chain contract call
An order with empty outputs and a hook. Encode the selector, put the calldata in the Order, and a solver runs it on the destination chain.
Example: LP on Aave from another chain
Bridge and supply in one signature. WETH on Base in, aUSDC on Arbitrum out, and the solver does the staking.
Choosing a bridge: the Router and the Bridge enum
One argument selects LayerZero, Axelar or same-chain execution. What the Router does with it, what it refuses, and which routes are coming.
Integrate iLayer in under an hour
Three steps: find the Hub address, build and sign an OrderRequest, call createOrder(). Everything you need to store, and the two calls you may need later.
Intent 107: Execution hooks, paying for cross-chain code
callRecipient, callData, callValue. The three optional fields that turn a swap into any DeFi action, and how the Executor keeps them safe.
Intent 106: Deadlines, withdrawals and the time buffer
Every order carries two deadlines and the Hub adds a third clock. Here is what each one protects, and the attack the time buffer was built to stop.
Intent 105: RFQ, how quotes reach you
Before the order there is a request. How iLayer broadcasts your RFQ to every solver over Waku, and how each answer comes back to you alone.
Intent 104: Hub & Spoke, how an order travels
Two contracts on every chain, one message each way. Follow an order from createOrder() on the Hub to fillOrder() on the Spoke and back.
Security first: our LayerZero integration audit
iLayer’s first independent third-party audit is complete. It covers the LayerZero integration, and it is the first of a series.
Intent 103: Anatomy of an Order
The whole iLayer network revolves around one struct. Here are its thirteen fields, grouped by the question each one answers.
Intent 102: Not All Intents Are Equal
Why true intent-based systems coordinate outcomes instead of moving tokens, and a five-question test to tell them apart.
Intent 101 – A beginner guide
What an intent is, where it came from, and how iLayer turns one signature into escrow, solver auction and settlement.