Source linked

La dVPN de RaccoonLine divise la visibilité sur trois types de nœuds

hackernoon.com@systems_wire3 hours ago·Systems Engineering·2 comments

Le trafic est crypté en couches ; chaque nœud déchiffre une seule instruction hop. Aucun participant ne voit l'origine, la destination et le contenu en même temps.

raccoonlinedecentralized vpnaes 256perfect forward secrecydistributed directoryprivacy

No single node in RaccoonLine's network sees the origin IP, the destination IP, and the encrypted content at the same time — that's the structural guarantee that centralized VPNs can't match.

The Distributed Directory Eliminates Central Registry Risk

On launch, the client queries a distributed directory — a record of active nodes spread across the network with no single authoritative copy. No company server gets assigned the VPN location. There is no central registry to subpoena or compel to reveal connection patterns.

Layered Encryption Forces Each Hop to Know Only Its Job

The client encrypts traffic in layers, one per node in the chain. Each node decrypts exactly one layer, reads only the next-hop instruction, and forwards the packet. AES-256 encrypts the tunnel between nodes, with perfect forward secrecy via ephemeral key exchange — compromise one session's keys, you learn nothing about any other session.

Three Roles, Three Blind Spots

First node knows the originating IP but not the destination. Last node (exit node) knows the destination but not who originated it. Middle nodes know neither. The exit node operator makes the final connection, so the visited site sees only the exit node's IP. The company itself doesn't operate any nodes — independent participants run the software and earn ROCC tokens for bandwidth.

What the Company Can't See

RaccoonLine maintains the protocol, directory system, and client apps. It does not sit in the traffic path and cannot produce connection logs that don't exist. That's not a policy promise; it's an architectural consequence.

The handshake uses standard, auditable cryptographic primitives — no proprietary schemes to hide behind. If you trust AES-256 and ephemeral Diffie-Hellman, you trust this foundation. The next step is seeing whether independent node operators deliver the bandwidth the network needs to compete with centralized providers on latency and throughput.


Source: RaccoonLine Publishes an Explanation of Its Decentralized VPN Protocol
Domain: hackernoon.com

Read original source ->

External source stays available while the OJO article and comment thread stay local.

Comments load interactively on the live page.