Supported Networks

Othentic provides CLI support for over 15+ networks and is actively adding more chains.

For contract deployment, you can use the configuration values specified and pass them as --l1-chain and --l2-chain options, as described in the contract deployment section.

You can use holesky-l2 or mainnet-l2 options if you want to deploy both L1 and L2 contracts on the same chain. For example:

othentic-cli network deploy --l1-chain holesky --l2-chain holesky-l2

Testnet

Chain Name & Id	CLI config value	AVS Factory address
Holesky 17000	holesky	0xf053F341C021F57f4a17C25476DF4761b0728D53
Holesky 17000	holesky-l2	0xb2d2648F02b633491d16C69A99CcF05cdaC9d36d
Amoy 80002	amoy	0xc2a881Dd3e6a9C21C18A998E47f90120BC9D87Aa
Base Sepolia 84532	base-sepolia	0xC9D62Af2d0Dd94bDdFEb54fd2c4Cf3B860cEDf1a
Mantle Sepolia 5003	mantle-sepolia	0x91Acfd45ebf3d6659114e44aFC271877Fb19f905
Arbitrum One Sepolia 421614	arbitrum-one-sepolia	0x390c4f2047250C8494963A6d2f1faE7935866D23
Manta Sepolia 3441006	manta-sepolia	0x8ce618b5cFD8E27012eBaA3287c1588059215585
Mode Sepolia 919	mode-sepolia	0x9CBA6B009B357EBe181963a032d70aC47EE7F1c6
Beam Testnet 13337	beam-testnet	0xB74E650BbE764E3B2CE0f61D4b82bF3deB0fFB27

Mainnet

Chain Name & Id	CLI config value	AVS Factory address
Ethereum 1	mainnet	0x64EA2F2DEE9eED5439468e92cf8Af8cD9ea0A994
Ethereum 1	mainnet-l2	0xf8492808e30AC993Aa9Bd2FFF77E4dC8aC80B6cB
Polygon 137	polygon	0x28e06CE6B25529e736D45Aff7c82Ef4Fc6F710bE
Base 8453	base	0x750e442F3C5b897F5518e50Eb8aBB8644340B42b
Mantle 5000	mantle	0x28e06CE6B25529e736D45Aff7c82Ef4Fc6F710bE
Arbitrum One 42161	arbitrum-one	0xB9ac7e784b8aE6754FCe47653f5F8F53f5a838D8
Manta 169	manta	0x28e06CE6B25529e736D45Aff7c82Ef4Fc6F710bE
Mode 34443	mode	0x28e06CE6B25529e736D45Aff7c82Ef4Fc6F710bE

If you are looking for a particular chain support, reach out to us via Discord.

Extending AVSs to Non-EVM Ecosystems

While AVS derives its security from EVM-based chains through Shared Security Providers like EigenLayer, supporting use cases on non-EVM ecosystems is possible. Developers can leverage AVS to build solutions for Solana or Move ecosystems.

Usage

AVS functions as an off-chain service, which means an AVS Task can involve executing specific computations related to non-EVM contracts. These tasks can be triggered by events or transactions occurring within the non-EVM chains.

Triggering AVS Tasks

AVS Tasks can be triggered based on specific events or transactions within non-EVM chains using Task Trigger.

Example Use Cases

1. Liquidation Bot on Solana: The bot ensures timely liquidation of under-collateralized positions. AVS can secure this bot designed to monitor Solana's DeFi protocols.

   • Create an AVS Task that executes the logic for monitoring collateral positions. When a relevant event occurs (e.g., a position becomes under-collateralized), trigger the AVS Task.

2. Automation in Move-based Ecosystems: Developers can implement automation workflows using AVS for various tasks such as transaction batching, governance voting, or executing other operations within Move-based environments.