π§βπ»Protocol Design (AVS)
Ditto Network consists of both on-chain and off-chain components that work as one mechanism. User interacts with Ditto SDK (Ditto Smart Contracts) and our execution layer.
Introduction
At Ditto, we are developing a system that allows users to execute on-chain transactions based on various triggers in a reliable way. This means users can set up automations without worrying about whether the transactions will be executed or missed. Our solution includes off-chain operators, which any user can run to ensure an affordable and dependable protocol flow. On-chain smart contracts are used to manage the protocol and distribute punishments and rewards.
Architecture
Our inspiration comes from the Ethereum consensus specs, ERC-4337 account abstraction, and the tooling provided by EigenLayer. You can see the overall architecture for Stage 0 in the following diagram:
To follow the logic sequentially, read the arrows from left to right in the following order: pink β blue β green β orange. Here's what happens at each stage:
Pink: Register on-chain to be included in the active pool in future epochs.
Blue: Periodically check the DEP contract for your role in the current slot.
Green: Retrieve active workflows from DEP.
Orange: Determine a batch of workflows that should be executed. If your role is attester, retain this information. If you're an executor, send a transaction on-chain.
At some point in the epoch, an attesting task is created. By this time, every attester has a history of workflows that should have been executed and can check on-chain to see if the executor really carried them out. Votes on this are then aggregated and sent to the chain.
Why itβs all matters:
We believe automation platforms and truly decentralized keeper networks are vital components of the Web3 ecosystem. Developing such automation infrastructure can attract millions of new users to Web3, enhance the utility of the EigenLayer, and provide additional rewards for restakers.
We aim to fully leverage the potential of the EigenLayer for external projects as opposed to compromise-filled dual token models. This will be a robust demonstration of EigenLayer's capabilities, both in validation and governance.
Offering a user-friendly infrastructure for automating interactions with the EigenLayer protocol. For instance, addressing main friction points for scheduled liquidity addition to the protocol, automation for asset diversification across all EigenLayer pools, and user interaction notifications with the pools.
Last updated