Network layer validator privacy is vital to strengthen Ethereum's robustness and censorship resistance.
Attestations are the strongest deanonymization signal: they're recurring, deterministic, and correlatable. But they're also time-sensitive, requiring strict latency and deliverability guarantees to ensure chain stability.
The direction I'm exploring for attestation propagation (as a native networking layer feature):
→ OHTTP-like two-hop shuffle (breaks IP-to-attestation link) while bounding delivery time (targeting 300ms p90)
→ Prioritized validator meshes via a ZK "proof of validator" (sybil-resistant without revealing identity)
→ Rate limiting nullifiers (prevents spam/garbage flooding)
→ Decoy traffic injection (obfuscates behavioural patterns)
If you're interested in contributing, reach out!
Attestations are the strongest deanonymization signal: they're recurring, deterministic, and correlatable. But they're also time-sensitive, requiring strict latency and deliverability guarantees to ensure chain stability.
The direction I'm exploring for attestation propagation (as a native networking layer feature):
→ OHTTP-like two-hop shuffle (breaks IP-to-attestation link) while bounding delivery time (targeting 300ms p90)
→ Prioritized validator meshes via a ZK "proof of validator" (sybil-resistant without revealing identity)
→ Rate limiting nullifiers (prevents spam/garbage flooding)
→ Decoy traffic injection (obfuscates behavioural patterns)
If you're interested in contributing, reach out!
https://x.com/raulvk/status/1998112138364084371
• • •
Missing some Tweet in this thread? You can try to
force a refresh
