Multichain
Last updated
Last updated
The Othentic Stack allows AVS developers to deploy L2 smart contracts on multiple L2 networks to extend capabilities across multiple chains seamlessly.
Hooks contract execution operates independently on each L2.
All L2s remain fully synchronized, ensuring consistent operator registration, voting power distribution, and governance settings.
Each L2 network independently manages its reward accounting.
You may implement logic to execute tasks on particular chains based on predefined conditions.
This feature will be supported in an upcoming release.
The othentic-cli tool utilizes consolidated environment variables for all supported L2 networks:
If targetChainId is not provided, the transaction will be submitted to the first chain in the list (e.g., <chain_id_1>).
Specify the RPC endpoints for all L2 chains, separated by commas(,)
Specify all the AttestationCenter contracts for all L2 chains, separated by commas(,)
Example:
Processing infinite orders of magnitude of financial strategies from DeFi protocols is infeasible for human consumption. An AVS-verified agent system that autonomously interacts with DeFi protocols across multiple chains on behalf of users—handling tasks like yield farming, rebalancing, or collateral management. The AVS coordinates agent task execution across chains, verifies interactions with DeFi protocols, and slashes malicious behavior.
This AVS coordinates a pool of independent solvers that execute user intents—swaps, transfers, contract calls—across multiple L2s. It assigns solver roles, verifies execution conditions, and finalizes results through a consensus process, slashing those who front‑run or misreport. Built‑in MEV‑reduction strategies make execution fairer and more efficient, while users gain confidence that their intents will be filled optimally and verifiably on any supported chain.
This AVS design decentralizes message passing by replacing multisig accounts and trusted relayers with an economically aligned operator set. Operators monitor several L2s, verify messages and states via light clients or ZK‑proofs, and authorize transfers using threshold signatures. Misbehavior triggers slashing, while built‑in liveness guarantees prevent stuck funds. The result is a bridge that inherits on‑chain economic security and removes single points of failure.
Keepers play a crucial role in maintaining the health of DeFi protocols by acting as incentivized parties who take advantage of arbitrage opportunities to boost the overall health of the protocol. AVS‑run keepers simultaneously monitor lending markets on any L2 for positions that slip below required collateral ratios. They rely on real‑time price and position data, validated with light clients or ZK proofs, to act the moment a threshold is breached. Once triggered, operators execute the liquidation, preserving protocol solvency without centralized bots or race conditions.
Using a Uniswap V4 hook, this AVS maintains one shared orderbook that matches buyers and sellers across different L2s. Operators collect orders, verify their validity, and settle trades atomically—often with optimistic relays or similar trust‑minimized techniques. Traders on Chain X can fill liquidity on Chain Y without leaving their home network, breaking down silos and deepening overall liquidity. The unified orderbook increases capital efficiency while preserving on‑chain security guarantees.
Operators in the AVS subscribe to event logs and contract deployments on every supported chain and trigger predefined actions—such as contract calls, token mints, or governance executions—on target chains. Because decisions are made collectively and enforced with slashing, applications get low‑latency, trustless automation instead of relying on a single off‑chain scheduler. This lets multi‑chain dApps react to on‑chain events promptly, safely and transparently, improving UX and reducing operational risk.
An AVS‑backed lending layer lets users post collateral on one L2 and borrow on another without trusting middlemen. Operators continuously verify collateral and debt positions across chains using light clients or zk‑proofs, then coordinate borrow and repay actions with threshold‑signed transactions. This unifies fragmented liquidity, expands borrowing power, and keeps positions safe through cryptoeconomic enforcement. Users enjoy seamless credit across L2s and avoid bridge costs and risks, while protocols avoid custodial risk.
The AVS continuously analyzes protocol activity across chains, using rule‑based checks or ML models to spot anomalies like sudden liquidity drains or oracle manipulation. When suspicious behavior is detected, operators can vote to pause affected contracts or de-risk positions by executing transactions on any supported network. Rapid, decentralized response prevents an exploit on one chain from cascading through shared liquidity or logic. By embedding economic penalties for negligence or collusion, the system aligns everyone on early detection and containment.
All L2 contracts - including , , and will be deployed on all selected L2 networks.
The execution of Tasks across different L2s is facilitated by the same peer-to-peer network, operator set and consensus engine used by the AVS. For more information, please refer to the .
To get started, follow the guide for detailed setup instructions and explore for a working implementation.
Specify the chain Ids of all the L2 chains, separated by commas (,). You can use the targetChainId parameter in the sendTask RPC endpoint of the to indicate which L2 chain the transaction should be executed on.
A multichain oracle AVS delivers uniform, secure, and cost-effective operations across multiple L2s. It aggregates quotes from multiple L2s plus trusted off‑chain sources, validates them, and posts the final value on each network in real time. By closing data gaps that invite arbitrage and systemic risk, the oracle provides developers and users with accurate data. Data feeds can be written directly to on‑chain storage or broadcast through that automatically update downstream protocols.
