Decentralized VPN: Open Nodes, One Coordinator

• An open network. Any operator can add an entry or exit node, in any country, by staking 1 TON. There is no approval step; the stake and the network's checks are the gate. If a node disappears or slows down, you pick another.
• Prices are set per node. Each operator sets a price per GB, and the marketplace lists it with the node's uptime and measured speed. You pick a country or a specific node.
• Entry and exit are separate nodes. On a 2-hop route the entry node sees your IP address but not where you go, and the exit sees where you go but not your IP address. That keeps both out of one operator's hands only when the two nodes have different operators, and the marketplace does not show who runs a node.
• Your money is not in a company account. Deposits sit in the contract, and the platform can withdraw only the fees it has collected.

• One coordinator. It runs on ProofKit's servers, and new sessions, billing, payouts and co-signed withdrawals all depend on it.
• Signatures stay with ProofKit. Operators cannot claim without the coordinator's signature, and your everyday withdrawals need its co-signature. The exception is the emergency withdrawal after the contract has been paused for 30 days in a row.
• Operators are vetted by stake, not identity. The stake and the network's checks are all that stand behind a node. The default node configuration keeps no access logs, but whoever runs a node has root on that server.
• Proofs still rely on ProofKit. The TLSNotary notary is run by ProofKit, so proofs make the records auditable, not independent of it.

The coordinator connects through each node's tunnel and fetches real pages. It compares the bytes reported by the entry and the exit with each other and with WireGuard's kernel counters, and it looks for statistical anomalies such as sudden jumps or repeating patterns. Three or more critical flags on a node within 24 hours cost it 10% of its stake.

Traffic checkpoints are signed, and the notarised ones are listed in the Proofs explorer. Node status is public on the Network page.

Every node serves VLESS Reality. Operators can also switch on Hysteria2, XHTTP and, on exit nodes, olcRTC, which carries traffic inside a video call. Reality works in most Xray- and sing-box-based apps, Hysteria2 and XHTTP need an Xray-core based one, and olcRTC needs an olcRTC-capable client. They are compared on the protocols page.