[CHECKLIST] Tangle AVS Implementation

[Tjemmmic]

Overview

The Tangle AVS is a blueprint that is able to run either a Tangle validator or operator node.

An Eigenlayer operator should be able to participate in Tangle using the precompile interface we have for Tangle operators. We want to use a bridge to dispatch these messages through. When we receive messages on Tangle, we expect to process it as normal in the precompile on Tangle.

For example, we handle Eigenlayer registration as dispatching a message to setup a validator on Tangle. We could have the ability to register as a validator, an operator, or both. Each would have a unique flow and its own message to dispatch.

Checklists

Overall AVS Steps and Requirements

• Registers for EigenLayer and AVS
• AVS runs Tangle Node in Validator mode and exposes the session keys and account key
• We bridge the registration to some arbitrary contract on Tangle
• That contract has TNT which is given to that address
• AVS listens for it's balance/transfers regularly, checking its TNT balance. When it's non-zero it submits all the validator registration extrinsics.
• The AVS's validator should be in the waiting set at this point.

Steps to Getting on the Testnet

• [TASK] Trust Modeling
• [TASK] Operator and End User Instructions
• [TASK] Communication Channels for AVS Upgrades
• [TASK] Node Specifications
• [TASK] Deployment

Onboarding/Registration Flow

Offboarding/Deregistration Flow