Supported Networks

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.

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
BNB Smart Chain 56	bsc	0xdA93D7e68a1d2dA234954f0E5c727E9966496FEC

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
Beam Testnet 13337	beam-testnet	0xB74E650BbE764E3B2CE0f61D4b82bF3deB0fFB27
BNB Smart Chain Testnet 97	bsc-testnet	0xf207a4d1430d2524793A542dee7Fa103b0fbe44B

Nightly Environments

Chain Name & Id	Config Value	AVS Factory address
Holesky 17000	holesky:nightly	0x545fb8EE4FD2F6Dd102C7Aa79846a5b23b71Eb9C
Amoy 80002	amoy:nightly	0x10030AD20b98EFA80ff80985149D1B0388b12540
Base Sepolia 84532	base-sepolia:nightly	0xD63728099eAbE2bf2DE400E930277DA066a63bE6
Mantle Sepolia 5003	‎mantle-sepolia:nightly‎	0x06A0ECa10B0463dbf84d8e91C8ecbf6D6e1Af86F
Arbitrum Sepolia 421614	arbitrum-sepolia:nightly	0xCD1B601Cb11802bB005782BcdB451b730aD5B2eA
Beam Testnet 13337	beam-testnet:nightly	0x969C151A6e358d925c685941D60F0eF1D6f6B478
BNB Smart Chain Testnet 97	bsc-testnet:nightly	0x67E2ef39E9F01Fe0BFd57109541Ff6b241e6557E

Othentic maintains unaudited nightly environments for testing new and upcoming features. These environments are not intended for production.

To use these environments, use the corresponding values for the L1_CHAIN , L2_CHAIN environment variables, or pass them to the --l1-chain and --l2-chain flags while running commands.

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

If you need support for a particular chain not listed here, please reach out to us via Discord.

---

Extend to non-EVM Networks

Developers can leverage the Othentic Stack to build solutions for non-EVM ecosystems such as Solana, Move, and others.

Usage

AVS functions as an off-chain service, which means that Tasks 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

Trigger 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.