Multi-Prover AVS (EigenLayer)

TEE AVS on EigenLayer are bound by machine trust and cryptoeconomic security

Decentralized systems bootstrap a secondary TEE Prover to minimize network-breaking bugs and achieve better security and decentralization. This rigorous approach is augmented by the introduction of TEE Committees.

Proof verification plays a crucial role in the security and efficiency of any rollup. Traditionally, most frameworks rely on a single prover, which leaves them vulnerable to bugs and single points of failure. Interacting with the Multi-Prover AVS on EigenLayer is inventive in a number of ways:

• Economic bonds protect against liveness risks with the ability to slash inactive or offline vendors. This is also known as liveness slashing.

• Likewise, the issue of ‘lazy’ validators is tackled by cryptoeconomic trust, with the correctness of execution guaranteed by the TEE.

• TEE Committees composed of heterogeneous vendors (such as Intel, AMD, AWS) raise the bar for malicious actors and increase security through redundancy.

• 'Swift' lane for optimistic on-chain attestation where claims are accepted optimistically with a bond that is forfeited if later invalidated. This can remove key performance bottlenecks around verifier costs and sequential congestion.

• Reduces observable latency within multi-prover systems by allowing quick provers to issue proofs for initial confirmation, followed by more secure, final confirmations from slower but secure provers. This proves especially advantageous in use cases where rapid feedback is essential, such as payments.

How the Multi-Prover AVS works:

1. Task Submission: Protocol builders participate in the AVS and submit multi-proving tasks. In a rollup scenario, this includes sampling and proving batched transactions submitted by the L2 to L1.

2. Prover Registration: Independent operators register to take on these tasks. Operators leverage reproducible builds to run the TEE Prover, verified by Automata’s TEE Compile to ensure the integrity of the build process.

3. Execution and Attestation: Each operator (Prover) executes the task on their TEE platform of choice. An attestation is generated to validate the correctness and integrity of execution.

4. On-chain Verification: Attestations are submitted to the blockchain, where the smart contract assumes the role of the attestor and conducts verification on-chain.

5. Rewards Distribution: Rewards are distributed to the operators upon successful completion of the task.