The Athena Journey: Running, Exiting & The Bia Attack Net

The Athena Journey: Running, Exiting & The Bia Attack Net
Obol Roadmap to Mainnet

5000+ signups, 200+ successful Distributed Key Generation (DKG) ceremonies, 100+ Distributed Validator Clusters signing attestations across 40+ countries. To say the least, the level of interest in our first public testnet wildly exceeded our expectations. THANK YOU for all of the support you, our community, gave us in testing our Distributed Validator Technology middleware, Charon.

This is probably one of the best testaments of how important a role Distributed Validator Technology (DVT) will play in the coming months, especially following the merge, as DVT becomes the most critical primitive on the Ethereum roadmap. At Obol, we feel privileged to lead the effort to decentralize stake and are confident that together with our community, we can tackle the next big challenge for Ethereum.

Here’s what’s in store for Athena.


  1. Athena Final Stage: Running Clusters
  2. Athena Wave 2
  3. Athena Exiting
  4. Next Testnet: Bia Attack Net

Useful Links

  1. Obol Website & Jobs
  2. Discord (look for the #faq-athena channel for all your questions)
  3. Quickstart Guide

Athena Final Stage: Running Clusters for 30 days

Getting at-home validators to successfully run DVT clusters with peers was important to us as they represent one of the key stakeholders for Obol and the wider Ethereum staking community. We learned a lot about the needs of this group and how we can better serve them. This was one of the objectives of Athena: improving the user journey and we feel confident with our learnings.

Now that 100+ clusters are running, we have started with Athena's second objective, monitoring health and collecting data from running clusters. This is important to help us understand how well Charon is integrating with the entire validator stack over longer periods of time.

Thus, the next stage for Athena participants is to keep their cluster running for 30 days. To monitor cluster health properly, we have issued monitoring tokens to be added to Prometheus as explained in Step 6 of the quickstart. Only cluster captains need to perform this step. To get your token, you can query our discord Cluster Info Bot with /info <cluster name>. You can get your cluster name by typing /cluster.

As a token of appreciation for those of you who run a cluster for 30 days and provide useful feedback in that process, we will be dropping an exclusive POAP. Stay tuned for more info on this.

Athena Wave 2

This is just the beginning for Athena and we know a lot of operators are waiting for sign-ups to reopen. We are glad to announce that we are working on a full self-serve version of Charon which will allow operators to join without restrictions. Stay tuned on our discord for more updates in the coming weeks.

Athena Exiting

After running clusters for 30 days, the final task for operators will be to be good testnet stewards and exit their validator from the network, rather than just turning it off. The steps to perform this optional step can be found at #6 in the quickstart FAQ.

From there, the Core Team will spend several weeks collating information and analyzing the observed performance of all distributed validators. Performance will be scored and a research post will be published outlining the strengths and weaknesses identified in the client and the entire UX flow of creating and running a distributed validator.

This date also coincides with the beginning of Dappcon (12-14 Sep) and EthBerlin (16-18 Sep). The Obol team will be sponsoring and presenting at both events and we intend to invite testnet participants to a wrap-up event during that week in Berlin. More details to follow.

Next testnet: Bia Attack Net

To this point, we have tested best-effort, happy-path validation with supportive participants. The next critical step towards building a mainnet-ready client is to begin to disrupt and undermine it as much as possible.

This testnet needs a consensus implementation as a hard requirement, where it had been optional for Athena. The intention is to create a number of testing tools to facilitate the disruption of Charon, including releasing a p2p network abuser, a fuzz testing client, k6 scripts for load testing/hammering an RPC endpoints and more.

The aim is to find as many memory leaks, DoS vulnerable endpoints and operations, missing signature verifications and more. This testnet may be centered around a hackathon if suitable and will likely include a bounty.

The different actions to be taken on this testnet will be synced between Athena and our Obol Operator Community with an expected start date in mid-Q4. Actions will likely follow a schedule with various attack vectors tested progressively.

If you are up for the challenge, we encourage you to keep your cluster running until then and participate in our attack net with your node. This is not a mandatory step for Athena participants. We also expect to release our frontend dapp to make DKGs and cluster setup easier, so it will be simpler to take part in the attack net even if you decide to exit your current cluster.


Athena participation has been a success so far, and we are excited to release the full performance report after this next phase of running clusters.

  1. If you are a cluster member, keep running for 30 days. If you would like to exit after that period, follow the quickstart guide.
  2. If you're still willing to join Athena, we'll reopen a self-serve track in the coming weeks.
  3. For those that want to continue to contribute, the next step will be the Bia Attack Net.

We are already looking forward to working with the community to continue on our path to creating Distributed Validators across the globe! LFG 🚀