Diva Staking

@stakediva

22 Following

234 Followers

Diva Staking pfp

5/ What’s this mean for us? Diva is getting ready to launch our own testnet once Pectra activates on Hoodi. Stay tuned for updates! Join our Discord 👇 https://discord.com/invite/divastaking

0 reply

0 recast

0 reaction

Diva Staking pfp

4/ Meanwhile, Fusaka planning is underway! Key dates: - March 24: Deadline for EIP proposals - March 31: Client teams share scope preferences - April 10: Fusaka scope freezes The next big upgrade is already taking shape

1 reply

0 recast

0 reaction

Diva Staking pfp

3/ Why Hoodi? It’s built to tackle validator exit testing, an issue that appeared during the Pectra upgrade on Holesky.

1 reply

0 recast

0 reaction

Diva Staking pfp

2/ Hoodi’s key milestone: Pectra activation is set for March 26th. This will be a critical test run for the upgrade. A mainnet fork for Pectra will only be scheduled after it succeeds on Hoodi and client teams are confident in the testing.

1 reply

0 recast

1 reaction

Diva Staking pfp

1/ The Hoodi testnet is live. A new long-lived testnet with a short-term focus on testing validators exits. Here’s what you need to know about Hoodi and what’s next for Diva. 🧵👇

1 reply

0 recast

1 reaction

Diva Staking pfp

The Pectra upgrade on Holesky exposed critical validator issues Per the postmortem (https://github.com/ethereum/pm/blob/master/Pectra/holesky-postmortem.md), 3 of 5 Execution Layer clients used mainnet’s deposit contract address instead of Holesky’s, splitting the chain’s perception across clients. Let’s see all the details, and what is Diva’s situation 🧵👇

1 reply

1 recast

1 reaction

Diva Staking pfp

7/ Join our Discord for real-time updates and technical discussions https://discord.gg/divastaking More to come as we progress.

0 reply

0 recast

0 reaction

Diva Staking pfp

6/ Progress update: a new Diva client image is expected early next week, targeting devnet validation first. Post-devnet, we’ll advance to testnet phases with a hardened implementation. Precision over haste—expect further details soon.

1 reply

0 recast

0 reaction

Diva Staking pfp

4/ In our case, Pectra lowers initial slashing penalties to 0.008 ETH from 1 ETH, but a correlation penalty after 18 days (https://eth2book.info/capella/part2/incentives/slashing/#the-correlation-penalty) claims full balances. Inactivity leak limits losses to 16 ETH over ~3 weeks, while mass slashing accelerates finality at a steeper cost. Client sync issues and incomplete slashing waves (https://dora-holesky.pk910.de/validators/slashings) signal needed upgrades.

1 reply

0 recast

0 reaction

Diva Staking pfp

5/ On our end, Diva’s prior testnet wasn’t Pectra-compatible and was already nearing deprecation. We’ve opted to decommission it and align with the next public testnet, ensuring resources focus on a robust, future-ready deployment rather than patching legacy setups.

1 reply

0 recast

0 reaction

Diva Staking pfp

3/ Natural recovery via inactivity leak (https://eth2book.info/capella/part2/incentives/inactivity/) is possible—validators lose balance until ejected below 16 ETH effective stake. However, this requires ~3 weeks and significant capital loss. Current efforts lean toward mass slashing to expedite finality.

1 reply

0 recast

0 reaction

Diva Staking pfp

1/ Initial mitigation—shutting down misconfigured clients, clearing databases, and resyncing with correct peers—failed. The Consensus Layer issue compounded the problem: an invalid chain state was justified at an incorrect epoch, creating a cascading failure.

1 reply

0 recast

0 reaction

Diva Staking pfp

2/ Validators attesting to the justified invalid checkpoint faced “surround” slashing conditions when pivoting to the valid chain. With consensus clients favouring the attestation-heavy invalid chain, the valid chain struggled with low block production and peer support, stalling recovery.

1 reply

0 recast

0 reaction

Diva Staking pfp

The Pectra upgrade on Holesky exposed critical validator issues Per the postmortem (https://github.com/ethereum/pm/blob/master/Pectra/holesky-postmortem.md), 3 of 5 Execution Layer clients used mainnet’s deposit contract address instead of Holesky’s, splitting the chain’s perception across clients. Let’s see all the details, and what is Diva’s situation 🧵👇

1 reply

1 recast

1 reaction

Diva Staking pfp

https://warpcast.com/stakediva/0x1a9fee78

0 reply

0 recast

0 reaction

Diva Staking pfp

6/ Find out all the details Medium Blogpost: https://medium.com/@stakediva/how-truly-decentralized-validators-are-born-c2e91e4e0a93 Updated docs: https://docs.divastaking.net

0 reply

0 recast

0 reaction

Diva Staking pfp

5/ 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.

1 reply

0 recast

0 reaction

Diva Staking pfp

4/ How Distributed Validators Are Born Step 1: Seed Generation DSC detects 32 ETH pooled → triggers RANDAO to create Seed0 (e.g., 0xBB9b...). Step 2: Node Participation Nodes signal interest via P2P network: “I want to help!” Step 3: Key Generation Selected participants collaborate to create a shared BLS public key. Step 4: Validator Activation Winning key set is submitted to DSC. Validator goes live on Ethereum, secured by distributed nodes.

1 reply

0 recast

0 reaction

Diva Staking pfp

3/ The Guardians: Diva Operators & Nodes ▶ Operators: Stake collateral to run nodes, earning rewards while securing the network. ▶ Nodes: Split into two roles: - Participants: Generate distributed validator keys (BLS standard). - Coordinators: Optimize the process, ensuring efficiency. - Operators’ influence depends on their collateral weight, not node count. This thwarts Sybil attacks and centralization.

1 reply

0 recast

0 reaction

Diva Staking pfp

2/ The Brain: The Diva Smart Contract (DSC) ▶ Core Function: Aggregates ETH from stakers into 32 ETH bundles. ▶ RANDAO Magic: Uses Ethereum’s native randomness to generate seeds (e.g., Seed0). ▶ ValidatorID Creation: Each bundle gets a unique ID via cryptographic hashing (keccak256). Why it matters: No single entity controls validator creation—it’s a provably fair lottery.

1 reply

0 recast

0 reaction