How truly decentralized validators are born

Diva Staking
5 min readMar 13, 2025

--

Imagine a staking network where decentralization isn’t just a buzzword to hide the fact that a few operators are running all the validators, but a fully realized system. A network where anyone, anywhere, can contribute to the security and scalability of Ethereum without needing 32 ETH sitting idle in their wallet. This is the story of Diva — a protocol that’s redefining staking by making it collaborative, efficient, and truly decentralized.

Let us take you behind the scenes of how Diva works and why it’s such a game-changer.

The Brain Behind It All: The Diva Smart Contract

At the core of Diva lies the Diva Smart Contract (DSC), a powerful piece of code with one mission: to gather ETH from stakers into the Diva Pool and orchestrate the creation of distributed validators. Here’s why this matters: in Ethereum, activating a validator requires exactly 32 ETH. For most people, that’s a steep barrier. But Diva changes the game by pooling smaller deposits together into bundles of 32 ETH.

Figure 1: Each allocation of 32 ETH is assigned to a random seed.

Every time the pool hits this magic number, something exciting happens. The DSC generates a random seed using Ethereum’s RANDAO mechanism. Think of this seed as a spark — one that ignites the creation of a new distributed validator. Each bundle of 32 ETH gets its own unique identifier, called ValidatorID, which is generated through cryptographic hashing (using keccak256 for those who love the technical details).

This process is like a lottery, where every bundle gets its own ticket to become part of Ethereum’s decentralized future.

The Guardians of the Network: Diva Operators and Nodes

But the DSC doesn’t work alone. Enter the Diva Operators and their trusty Diva Nodes — the real heroes of this story. Operators are individuals or entities who deposit collateral into the system and manage nodes to help run the network. In return, they earn rewards generated by the protocol.

Here’s where things get interesting: operators can manage multiple nodes, but their role in creating distributed validators isn’t tied to how many nodes they have. Instead, it’s all about their unique operator identity. This ensures fairness and prevents any single operator from dominating the system while reducing sybil attacks.

When it’s time to create a new validator, Diva Nodes take on one of two roles:

  • Participants, who generate distributed keys for the validator.
  • Coordinators, who oversee and optimize the process.

Such precisely orchestrated communication between participants and coordinators ensures everything runs smoothly.

The Magic of Collaboration: How Distributed Validators are born

So how does this all come together? Let uswalk you through it step by step:

1. The Seed Is Planted
When enough ETH is pooled (32 ETH), the DSC generates a random seed (Seed0) and uses it to create a unique ValidatorID. This identifier represents the new distributed validator.

2. Nodes Raise Their Hands
Diva Nodes interested in participating send requests to join the Distributed Key Generation (DKG) process via a peer-to-peer network. This step is like saying, “Pick me! I want to help create this validator!”

3. The Best Team Is Selected
Coordinators evaluate all potential participants based on their “weights.” These weights depend on factors like how much collateral an operator has deposited. Think of it like buying lottery tickets — the more weight you have, the higher your chances of being selected (but you can only win once per round).

4. Keys Are Generated
Once selected, participants work together to generate a shared BLS public key (a cryptographic standard used in Ethereum). This key is essential for activating the new distributed validator.

5. The Validator Comes to Life
Coordinators submit the results back to the DSC, which chooses the best proposal according to the aggregated weight of the set of participants and officially creates the new distributed validator.

It’s an elegant system designed for efficiency, fairness, and decentralization. If you want to check the details of this process, please take a look at the official Diva documentation.

A Real-Life Example: Bringing It All Together

Let’s make this concrete with an example. Imagine five operators are registered in Diva:

Figure 2: Diva Operators with a different number of Diva Nodes registered.
  • Operator1: 0x0123…
  • Operator2: 0x4567…
  • Operator3: 0x89AB…
  • Operator4: 0xCDEF…
  • Operator5: 0x9876…

Now suppose the DSC detects that there’s more than 32 ETH in the pool. It generates a random seed (Seed0)—let’s say 0xBB9b…. From this seed, it calculates a unique ValidatorID for our new distributed validator:

Next, participants with the lowest weights are chosen as part of an optimal team to create this validator. Meanwhile, coordinators with higher weights oversee everything to ensure it runs smoothly.

Finally, once all participants have collaborated to generate a valid BLS public key, one coordinator submits it back to Diva Smart Contract — and just like that, another distributed validator is born!

Why Diva Matters

What makes Diva so revolutionary is how it combines cutting-edge technology with fundamental principles of decentralization. By pooling resources and enabling collaboration between operators and nodes, Diva lowers barriers for staking while ensuring fairness and security at every step.

This isn’t just about creating validators — it’s about building a more inclusive Ethereum ecosystem where anyone can contribute to decentralization without needing massive amounts of capital upfront.

Join Us on This Journey

If you’re excited about what Diva is building and want to be part of this decentralized revolution, follow us on X or join our community on Discord. Together, we’re shaping the future of staking — one distributed validator at a time.

Follow Diva on X and Discord
Visit our
Website and Docs

--

--

Diva Staking
Diva Staking

Written by Diva Staking

https://divastaking.net - Diva is an Ethereum Liquid Staking protocol powered by Distributed Validation Technology

No responses yet