Parties

Provides an overview of the ditto network participants

Parties

There are multiple participants in the ditto network, let's walk over them.

Executor - actively simulating, validating and executing calldata participant of the network:

1. Define the workload (a set of blocks and automations), simulate execution, and check compliance with policies (e.g., ensuring that the state changes according to the user's intent as a result of the simulation—currently, all policies exist within smart contracts).

2. Execute the automation and wait for full compensation for the gas spent, plus a reward after the quorum has approved the decision.

3. Anyone can raise a dispute if the automation could have been executed but was not. To do so, the disputer has to lock a stake, and in case of a positive decision by general consensus, receive an additional reward.

Orchestration Network - main communication and synchronisation channel:

1. Collect the mainnet state to determine the set of executors and create a schedule for execution.

2. In case of a dispute, assess the performance of the responsible executors.

3. Make decisions on gas policies at the entry points in the execution networks.

4. Make decisions regarding reward distribution.

Interop - subset of nodes that propagate cross chain messages:

1. Observe a decision from the Orchestration Network to propagate to the target network or mainnet.

2. Gather signatures from all interop participants and execute the state transfer from the Orchestration Network to the target network (distribute rewards, change gas policies, initiate slashing) via Relayer that executes the message on target chain.

3. Continuously maintain an up-to-date list of validators on each target chain to ensure decentralized delivery of the Orchestration Network state.

4. Currently we work with Axelar stack to provide seemless interoperability between the Orchestration Network and the target EVM chains.

Entry points - contracts on target chains controlling execution and compensation:

1. Calculate the gas compensation during the execution and charge the vault

2. Store the compensations untill released by interop

3. Enable executors to claim the rewards with merkle root

Flow:

Apps submit meta transactions to the executor network using the Ditto SDK through multiple endpoints (each executor provides an endpoint for apps to submit transactions). This data gets included in the block and becomes the part of the common state of the ditto Orchestration Network. Ditto consensus rules manage transaction allocation. Executors query the Orchestration Network state to determine whether transactions have been allocated to them and if that is the case, they proceed to batch and submit the transactions. The system guarantees that no other executor gets assigned the same transactions within a block window. Any executor transaction that attempts to submit the same meta transaction will fail to receive compensation for spent gas and the reward.