The price is per GB of traffic through your node, upload and download together (1 GB = 1024³ bytes). The marketplace shows it with the 20% network fee added, and that total is what users pay.
What you receive
- Direct route (your origin alone): the user pays your price + 20%. When you claim, the escrow contract pays you 80% of that and keeps 20% as the platform fee, so you receive 0.96 × your price per GB.
- 2-hop route (an edge in front of an origin): the user pays the edge's price plus the origin's price, plus 20%. Each node is credited 80% of its own part of that charge, so whichever of the two nodes is yours, you again receive 0.96 × your price per GB.
- olcRTC traffic is the exception: from 20 November 2026 it is charged at the network's olcRTC price, the exit receives 80% of that price, and an edge earns nothing from it, because olcRTC never passes the entry. That price is one for the whole network, set by ProofKit: a node has no olcRTC price of its own, and its Settings show what the exit receives.
- Traffic from your own account earns nothing.
Worked example
| Direct route, 100 GB | TON |
|---|---|
| Your price 0.01 TON/GB | 1.00 |
| User pays (+20%) | 1.20 |
| You receive (80% of 1.20) | 0.96 |
| Platform fee (20% of 1.20) | 0.24 |
Choosing a price
The marketplace lists each exit country with the lowest price in it, fee included, so add 20% to your own price before you compare. An exit node always has a price, at least 0.001 TON/GB. An entry node may be free: at 0, a route through it costs only what its exit costs.
ProofKit routes users to a node automatically only while its price is at or under the network's ceiling for automatic routing; a node priced above it is reached by the users who choose it. See Your Nodes.
Rules for changing it
- A rise applies only to routes added after it: routes already in users' subscriptions keep the price they locked.
- A drop also lowers the price of the routes already running on your node, once the lower price has stood for 3 hours. Every change of the price starts those 3 hours again.
- One change per 24 hours, up or down, and a rise of at most 3× in one step (0.002 → 0.006 is allowed, 0.002 → 0.01 is not).
- One exception: if you lowered a price by mistake, put it back up within 2 hours 50 minutes of the drop, to at most what it was. That needs no 24-hour wait and has no 3× limit. Put back all the way, the running routes never see the drop; put back only part of the way, they get the remaining lower price 3 hours after that change. A route added while the price was low keeps that price. The undo counts as a change, so the next one waits 24 hours.
- Prices go from 0.001 to 100 TON/GB. Only an entry node may also be set to 0.
Units
1 TON = 109 nano-TON. A price of 0.01 TON/GB is stored as 10000000 nano-TON per GB, and every charge and split is computed with whole nano-TON, so there is no floating-point rounding.