A2

OHTTP-Style Two-Hop Shuffles

Routing & Transport Development

Description

A multi-hop routing primitive inspired by Oblivious HTTP that separates identity (Relay) from application data (Gateway).

Relationships

Target	Type	Note
P3	benefits	Gateway only sees the Relay IP, not the validator IP.
P6	benefits	Maintains consensus compatibility through low-latency routing.
P1	hurts	Additional network hop adds 50-100ms latency.
P7	hurts	Requires new relay infrastructure and connection management.

Open questions

Managing pre-warmed connections at scale.
Geographic distribution of reliable relay nodes.

References

Relationships

Dir	Target	Type	Note
→	P3 Identity Unlinkability	benefits	Gateway only sees the Relay IP, not the validator IP.
→	P6 BFT Compatibility	benefits	Maintains consensus compatibility through low-latency routing.
→	P1 Latency Bound	hurts	Additional network hop adds 50-100ms latency.
→	P7 Implementation Complexity	hurts	Requires new relay infrastructure and connection management.
←	A1 ZK Proof of Validator (ZK-PoV)	complements	ZK-PoV secures the endpoints of the OHTTP shuffle.
←	A6 Pre-warmed QUIC/TCP Connections	enables	Pre-warmed connections are required to meet OHTTP latency targets.
←	A7 Flashnet Anonymous Broadcast	complements	Flashnet provides a threshold-based evolution of the OHTTP relay model.