A1

ZK Proof of Validator (ZK-PoV)

Identity & Credentialing Research

Description

An anonymous credential system that allows nodes to prove they are active beacon chain validators without revealing their specific identity or IP address.

Relationships

Target	Type	Note
P3	benefits	Severing the IP-to-identity link via ZK credentials.
P4	benefits	Prevents Sybil attacks by requiring proof of active stake.
P6	benefits	Enables high-trust meshes without exposing validator schedules.
P7	hurts	Requires complex ZK proof generation logic in clients.
P1	hurts	Proof generation time can approach slot time limits on low-end hardware.
A2	complements	ZK-PoV secures the endpoints of the OHTTP shuffle.
A3	benefits from	Anonymous meshes need global rate limiting to prevent DoS.
A8	complements	ZK credentials can gate access to the mixnet to prevent Sybil flooding.

Open questions

Computational overhead of proof generation on consumer hardware.
Trusted setup requirements for specific SNARK schemes (e.g. Caulk+).

References

Proof of Validator: A simple anonymous credential scheme

Relationships

Dir	Target	Type	Note
→	P3 Identity Unlinkability	benefits	Severing the IP-to-identity link via ZK credentials.
→	P4 Sybil Resistance	benefits	Prevents Sybil attacks by requiring proof of active stake.
→	P6 BFT Compatibility	benefits	Enables high-trust meshes without exposing validator schedules.
→	P7 Implementation Complexity	hurts	Requires complex ZK proof generation logic in clients.
→	P1 Latency Bound	hurts	Proof generation time can approach slot time limits on low-end hardware.
→	A2 OHTTP-Style Two-Hop Shuffles	complements	ZK-PoV secures the endpoints of the OHTTP shuffle.
→	A3 Rate Limiting Nullifiers (RLN)	benefits from	Anonymous meshes need global rate limiting to prevent DoS.
←	A5 Privacy Pass (RFC 9576)	complements	Privacy Pass principles inform the ZK-PoV architecture.
→	A8 Sphinx-based Mixnets	complements	ZK credentials can gate access to the mixnet to prevent Sybil flooding.