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.
/Ecosystem. · 03.
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.
The Order struct does not care who signed it. That is why the same integration serves very different products. Here are the three we see most, plus the developer profiles behind them.
/01 · Chapter.
DeFi protocols: dexes, perps, marketplaces
With a simple intent and a quick integration a protocol adds multi-token swaps and bridging, cross-chain rebalancing, or NFT minting with full gas sponsorship. A single-chain dapp going cross-chain finds iLayer easier to integrate than LayerZero, Axelar or Across directly, with more functionality out of the box: RFQ pricing, custody, deadlines and hooks come with the contracts.
Chain-specific protocols such as Morpho or GMX can be reached without exposure to the underlying chain: the user’s funds stay on the source chain until a solver delivers the position.
/02 · Chapter.
Wallets: chain abstraction
A wallet can offer a chain-abstracted experience: consolidate a portfolio across chains cheaply, or move into the L1 or L2 that launched this morning, in one signature. Multi-token outputs turn “rebalance” into a single order. Sponsored orders remove the “you need gas on that chain first” problem entirely. New chains such as Monad, Berachain and megaETH become one-click destinations with gasless UX.
/03 · Chapter.
AI agents: any web3 action
An agent produces a plan in natural language or JSON. Encoding that plan as a transaction sequence across chains is where most agent frameworks break. With iLayer the agent encodes the outcome as an Order (inputs, outputs, an optional hook) and offloads execution to the solver network. One struct can express “buy the dip on SOL and stake it”; solvers figure out the route, and the contracts guarantee the agent’s funds move only when the outcome is delivered.
/04 · Chapter.
Rebalancers and treasuries
Cross-chain rebalancers such as yearn, nashpoint or beefy allocate assets across chains without multi-bridging: instead of a chain of bridge transactions they create multiple intents, each settled independently, each withdrawable if it expires. Treasury operations get the same property: no wrapped assets, no half-completed routes.
/05 · Chapter.
Why it is the same integration
Every case above is the same three calls from the integration guide, with different fields filled. That is the argument for an intent-based design in one sentence: the product decides what should happen, the network decides how, and the struct between them never changes.
/Read next.
Our first audit.
Next: what was reviewed in the LayerZero integration audit and what comes after it.