Validator Consolidation Eligibility Dashboard for Large Pool Operators

[JamesEjembi]

Problem Statement / Feature Objective

Validator consolidation (EIP-7251) allows operators to merge multiple validators into fewer, larger-stake validators. Operators with thousands of validators need a dashboard that scans their entire fleet, identifies consolidation-eligible validator pairs/groups, computes the optimal merge strategy to minimize operational overhead, and estimates gas cost savings.

Technical Invariants & Bounds

• Consolidation eligibility requires both source and target validator to have the same withdrawal credentials
• Optimal merge grouping: minimize validator count while respecting the 2048-ETH effective balance cap per consolidated validator
• Gas savings estimation = (current_validator_count - merged_validator_count) × avg_gas_per_validator_per_epoch × 365.25 days
• Fleet scanning must support up to 10,000 validators without blocking the main thread (web worker + chunked processing, 500 validators per chunk)
• Results must be sortable by: potential savings (desc), validator count, and consolidation readiness score
• Readiness score = 0.5 × (matching_withdrawal_creds_ratio) + 0.3 × (balance_proximity_to_32) + 0.2 × (activation_epoch_proximity)

Codebase Navigation Guide

• src/hooks/useConsolidationEligibility.ts – hook for eligibility scanning
• src/workers/consolidationScannerWorker.ts – web worker for chunked fleet scanning
• src/components/validators/ConsolidationDashboard.tsx – main dashboard component
• src/utils/gasEstimator.ts – gas calculation utilities
• src/utils/ethMath.ts – base Ethereum math operations
• src/pages/validators/ValidatorDashboard.tsx – integration point

Implementation Blueprint

1. Create src/utils/consolidationEligibility.ts – core algorithm that groups validators by withdrawal credentials, finds optimal merge sets under 2048-ETH cap, and computes readiness scores
2. Build src/workers/consolidationScannerWorker.ts – processes validators in chunks of 500, returns merge recommendations via postMessage
3. Implement src/hooks/useConsolidationEligibility.ts – manages worker lifecycle, aggregates chunk results, handles loading/error states
4. Create src/components/validators/ConsolidationDashboard.tsx with sortable table showing (group_id, current_count, merged_count, savings, readiness_score)
5. Add src/utils/gasEstimator.ts – estimates per-validator gas costs for attestations, proposals, and withdrawals
6. Mount in ValidatorDashboard.tsx as a new tab "Consolidation" alongside existing tabs

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@clintjeff2's PR #82 was approved and merged by @JamesEjembi.

🏆 @clintjeff2: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,131 total points). Track your full progress on GrantFox.

👏 Great work, @clintjeff2! Keep contributing to VeriNode-Labs.