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 guide.
Nightly Environments
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
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.
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.
Last updated