README.md

Obol Distributed Validator Blueprint 🌐

A Tangle Blueprint for running a Obol Distributed Validator Cluster

📚 Overview

This Tangle Blueprint provides a specification for running a group Obol Distributed Validator Cluster as an AVS on the Tangle Network.

🚀 Features

• Automated devops for running DVT clusters.
• Automatically performs Obol's DKG process
• Tangle Network integration for on-demand instancing of DVT clusters

🛠️ How It Works

1. Cluster Configuration: The blueprint defines the structure for configuring a Distributed Validator Cluster, including the number of operators, threshold for signing, and validator details.
2. Leader Selection: For simplicity, the leader is simply the first operator.
3. Distributed Key Generation: Automatically performs Obol's DKG ceremony process
   • Each operator creates an ENR, and then shares them with the leader.
   • The leader uses these ENRs to create the DKG config
   • The leader distributes the DKG config back to the other operators
   • The DKG ceremony starts, generating the cluster definition files.
4. Tangle Integration: Allows on-demand instancing of Obol DVT clusters using Tangle's operator set.

📋 Pre-requisites

• Docker
• Docker Compose
• cargo-tangle

💻 Usage

To use this blueprint:

1. Review the blueprint specifications in the src/ directory.
2. Follow the Obol documentation to understand the Distributed Validator setup process.
3. Adapt the blueprint to your specific cluster configuration needs.
   • For simplicity, this blueprint by default will simply copy the sample Holesky config. This can be changed here.
4. Deploy the blueprint on the Tangle Network using the Tangle CLI:

$ cargo tangle blueprint deploy

5. Activate the DV
   • See the Obol documentation for this section. Once the operators have finished the DKG ceremony, the deposit-data.json file will be generated, and can be taken from any of the operators.

🔗 External Links

• Obol Documentation
• Tangle Network
• Ethereum 2.0 Staking

📜 License

Licensed under either of

• Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

📬 Feedback and Contributions

We welcome feedback and contributions to improve this blueprint. Please open an issue or submit a pull request on our GitHub repository. Please let us know if you fork this blueprint and extend it too!

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.