Explore frequently asked questions about Ava Protocol, covering its features, benefits, integration with DeFi platforms, and more.
Ava Protocol is an event-driven EigenLayer AVS that enables seamless autonomous transactions for Ethereum and beyond. It empowers developers to improve crypto transactions with intelligent automation, enhanced privacy, effortless composability, and significant cost savings.
Ava Protocol automates key aspects of DeFi development, such as on-chain interest rate updates, liquidity management, and liquidation processes. This reduces the need for manual monitoring, lowers operational costs, and improves platform reliability.
Ava Protocol improves platform reliability by automating functions and optimizing processes. This saves developers time, reducing inefficiencies and allowing them to focus on innovation. Ava Protocol ensures timely updates, precise liquidations, and streamlined operations.
Ava Protocol supports both Ethereum and Polkadot, providing broad compatibility with existing applications and services. Developers can seamlessly integrate automation and advanced transaction functionalities across EVM-compatible and Substrate-based chains.
Ava Protocol enhances transaction privacy and security through advanced MEV (Maximal Extractable Value) protection mechanisms. This approach prevents external entities from intercepting or manipulating transactions, ensuring that transactions are confidential and shielded from front-running and other malicious activities.
Ava Protocol's enhanced automation benefits developers, DeFi traders, gaming projects, NFT artists, real-world asset applications, and users of practically any web3 vertical. By empowering seamless automation through super-transactions, Ava Protocol opens up new possibilities and use cases across the web3 ecosystem.
You can start by trying our testnet. Visit Ava Protocol Testnet to begin exploring the features and capabilities of Ava Protocol.
Ava Protocol’s wallet introduces a controller that works in tandem with the EOA so that users don’t need to directly manage their private keys. The controller has the ability to execute future actions based on the user’s preferences without direct input. This dual-control structure allows the protocol to execute autonomous transactions on the user’s behalf without requiring direct access to their private key, streamlining wallet automation while maintaining security.
The Ava Protocol smart wallet simplifies automated transactions while keeping the user’s assets secure. The wallet automatically generates and packs multiple transactions into a User Operation, as defined by ERC-6900, combining the steps into a single process.
Yes, the UserOps (or task payload) is generated by the AVS Aggregator because the action details of the user’s task are stored in it.
There are a few ways to pay for automated transactions:
The transaction authorization process functions similarly to OAuth. The authentication can be achieved by a variety of methods:
This session token then provides controlled, time-limited access to the user’s smart wallet. While there are other ways to allow controlled access, option #1 is the most familiar for web3 users, while options #2 and #3 cater to those familiar with web2 experiences.
For example, if a user wants to set a limit order with a three-week expiration, they could simply authorize via Google, requesting a session token that’s valid for the three-week period.
Note: OAuth (Open Authorization) is a widely used web2 protocol that allows applications to access resources on behalf of a user without exposing their credentials (like passwords). It works by granting third-party applications secure, limited access to user accounts on other platforms through tokens rather than sharing sensitive information directly.
With respect to permissions:
Much like the concept of “scopes” in Google OAuth, Ava Protocol attaches specific permissions, or “scopes”, to the session token during authentication. For instance, when a user logs in via Google and creates a smart wallet, the protocol first asks which permissions they want to enable for this wallet. If a scope is defined to permit only ETH and USDC transfers with a monthly limit of $500, then any attempts to transfer other ERC20 tokens or exceed this limit will be rejected by the AVS Aggregator, which manages the creation of task payloads and enforces these permissions.
In the AVS network, operators are responsible for monitoring onchain events and signals (such as subgraphs) to determine when task conditions are met. Currently, operators function as a large group, though we plan to introduce randomized smaller groups in the future to reduce the risk of collusion. Each group of operators is assigned specific tasks to monitor and actively listen for relevant onchain events. When conditions are met at the designated time or block, the group reaches a consensus, or “verdict,” on whether to trigger the task and notifies the Aggregator.
After receiving the verdicts, the Aggregator creates the necessary task payloads and submits them onchain for execution. The Aggregator also monitors each transaction’s execution status. If a transaction fails, there are two user-configurable options for handling it: either retry on the next block (or after a defined interval), or abort the task altogether. Additionally, users can opt to receive execution status notifications through channels like email or Telegram.
Once submitted, the execution status is logged as onchain events that can be queried via chain RPC or future aggregation tools like Dune Analytics for reporting purposes. To effectively track these task submissions, we’ve developed an innovative task data structure that has been iteratively refined over the years. This data structure functions as a priority queue, enabling efficient grouping, filtering, and prioritization to meet Ava Protocol’s core requirements:
Absolutely! Ava Protocol acts as a Retool or Zapier for web3 by allowing developers to build and automate dapps without needing extensive backend infrastructure. Similar to how Retool eliminates the need for companies to create internal tools from scratch, Ava Protocol abstracts away much of the backend complexity for dapps. It enables developers to set up automated transactions, event-triggered smart contract interactions, and other essential dapp functions without maintaining a custom backend.
Ava Protocol brings similar benefits to web3. It aims to help developers launch dapps on time and achieve their KPIs by reducing development time from three months to a week, cutting costs by 90%, and enabling seamless MEV protection and multi-chain deployment with a single click.
Ava Protocol’s Studio is designed to integrate seamlessly with tools web3 developers are already familiar with. Filtering NFT events falls under the Smart Contract Events category, where you could use standard Ethereum query syntax to filter specific topics within the NFT smart contract. For example, you might format queries like topic0=”<method_name>” and event_data.field1=”<input_parameter_1>” to target specific event data fields.
Here’s how you can feed your own data to Ava Protocol automation:
For additional questions or suggestions to improve this documentation, please create a GitHub Issue on our Repository.