Direct route (one node)
| Per GB | |
|---|---|
| User pays | node price + 20% |
| Operator receives | 80% of what the user pays = 0.96 × node price |
| Platform keeps | 20% of what the user pays |
2-hop route (edge + origin)
| Per GB | |
|---|---|
| User pays | (edge price + origin price) + 20% |
| Origin's operator receives | 0.96 × origin price |
| Edge's operator receives | 0.96 × edge price |
| Platform keeps | 20% of what the user pays |
Each node is credited 80% of its own part of the charge, exactly as on a direct route, so a node earns the same per GB whichever kind of route its traffic takes. When each operator claims, the contract takes that operator's part of the charge from the user's deposit and pays out 80% of it, so the two claims together take exactly what the user was charged.
olcRTC traffic is the exception: from 20 November 2026 it is charged at the network's olcRTC price, the exit's operator receives 80% of that price, and an edge earns nothing from it, because olcRTC never passes the entry.
Prices are locked per route
When a user adds a route, the session records the origin's and the edge's price at that moment, and billing uses them for as long as the route stays in the user's subscription. An operator's later rise does not reach it; a drop does, once the lower price has stood for 3 hours. olcRTC traffic aside: from 20 November 2026 it is charged at the network's olcRTC price. See Price locking.
Integer math
Every charge and split is computed in whole nano-TON with integer arithmetic: no floating point, no rounding drift. Each node's share is rounded down, so the operators' claims never take more from a deposit than the user was charged; the fraction of a nano-TON that rounding leaves goes to the platform.
Your own traffic
A node earns nothing from traffic by its owner's own account. On a 2-hop route where you own only one of the two nodes, only your node's credit is skipped.