How It Works
Technical deep-dive into the proof-of-ownership mechanism
Step-by-Step Process
Generate Proof
The validator operator uses the standard ETHStaker deposit CLIto generate the BLS TO Execution Change Keystore output using their validator key instead of their withdrawal key. The output should look similar to the below.
Message Structure:
{
"message":{
"to_execution_address":"0x621351604e300f3f4990aafcc17d0bb23f98ff6e"
"validator_index":9213
}
"signature":"0xa1af11c70092550c303c6d263e7b948df93.."
}The signature proves the operator controls the validator's signing key without requiring the mnemonic seed phrase.
Submit Proof
The generated proof is uploaded to this dashboard and automatically verified. Once verified, it will be stored and submitted to a public GitHub repository via pull request (in batches). This ensures complete transparency and enables community review.
Verification Process
Signatures can be verified by anyone as they are publicly available in the repository.
Verification Checks:
Future On-Chain Integration
After sufficient community review and consensus, verified proofs may be recognized during the post-quantum hard fork implementation.
Future Pathway
The confirmed lost registry serves as input for potential EIP proposals. If consensus is reached, the PQ transition could include special handling for verified lost validators, enabling balance recovery to their proven withdrawal addresses.
Off-Chain Verification Benefits
By conducting proof collection and verification off-chain, we achieve several important goals:
Transparency
Public GitHub repository enables community audit and independent verification
Reproducibility
Anyone can re-verify signatures and cross-check beacon chain data
Safety
No protocol changes required until community reaches consensus
Time-stamping
Git history provides immutable record of proof submission dates
Security Considerations
Review assumptions, limitations, and fraud prevention measures
Read Security Details