Private and Safety Routes
Toward The Future
Private routing is a balance of performance and security
Applications can make use of higher node hop counts if they desire
Future private routing advancements will be transparent to users
Per-Hop Payload KeyingEnsuring that there is nothing common between packets at each hop will reduce the risk of mass data collection being able to deanonymize routes.
Simplify DirectionalityRoutes are currently bidirectional, but are allocated directionally. We may be able to simplify our allocation mechanism by enforcing bidirectionality. Bidirectional routes are faster, but directional routes could provide more anonymity.
Elimination of Hop CountingCurrently the protocol keeps an internal hop count that is not necessary. Efforts should be made to ensure that individual nodes don’t know how far along in a route they are.
Hop CachingRoute hop NodeInfo could be cached to save on-the-wire size as well as speed things up.
Increasing Hop Count
Currently the default is one hop chosen by the Safety Route, and one hop chosen by the Private Route, which leads to three hops total once compiled.
It may be important to increase hop count to 2 for users with critical safety needs and to protect from nation-state-level deanonymization where appropriate.
Existing research (on Tor) suggests that our existing hop count should be sufﬁcient and provide comparable anonymity, but this should be revisited.
IP Privacy means your location is safe too
Users don’t have to do anything to use it
No IP address means no tracking, collection, or correlation