Transit Fabric releases

Testnet rewards: proposed rules

Proposed, open for feedback until Tuesday 17 November 2026, 12:00 UTC. The rules become final then, and we publish the final version here with a list of what changed. If substantive feedback arrives late, we may extend the deadline and say so here.

How to give feedback:

Point at the section you're commenting on. Numbers marked proposed value are the ones we most want views on.

Proposed rules, version 2. This page will be the only place that says what testnet work may earn. Other pages link here and don't restate it.

In short

What an allocation is

The pool

How we currently intend to size any discretionary reward; not a promise or entitlement.

Track Share of the pool Rewards
Nodes 50% Sites that stay up, declare honestly and are peered, weighted toward the networks and environments the testnet lacks
Findings 30% Valid findings, by the tiers in the bounty page
Solvers 10% Route tables that beat the reference solver
Docs and onboarding 10% Merged fixes, and first onboarding reports from a new environment

A track's unspent share moves to the node track.

Who can earn

Node points

How we currently intend to size any discretionary reward; not a promise or entitlement.

Points are counted per site each week (140 windows), then summed per claimant. A site is a group of one claimant's nodes whose probed endpoints share an IPv4 /24. Every input comes from what validators already commit each window.

Base: 10 points per site a week

A site holds base for the week when all four of these hold:

Diversity: up to 6 points per site

D = 6 / n_asn

Environment: one bonus per site, the highest that applies

Environment Points
OpenWrt router on the supported image 15
Node on a home or mobile line behind NAT 8
Another platform we list as wanted (for example an ARM board or a new OpenWrt target) 5
Datacenter VM 0

Roles: added to the site

Role Points a week Condition
Open peer 4 Peered with nodes of at least 2 other claimants during their first 14 days
Fast upgrade 3 On a new release within 24 hours of its announcement

A data-server role comes with phase F. Solvers have their own track.

Fleet: per claimant

Fleet Points
One hotkey binding 3 or more sites in at least 2 ASNs, all holding base 10 a week
The first working binding of more than 7 nodes under one hotkey 30, once

Duplication

A week, worked through

Site or claimant Base Diversity Environment Roles Fleet Total
VM, 5 sites at its provider 10 1.2 0 11.2
VM, the only site in its ASN, open peer 10 6 0 4 20
OpenWrt router at home, alone in its ASN 10 6 15 31
Fleet of 3 VMs in 3 ASNs (1, 2 and 6 sites each) 30 6 + 3 + 1 0 10 50

Capacity above the base floor appears nowhere. A home router earns almost 3 times a VM at a crowded provider.

How points become alpha

How we currently intend to size any discretionary reward; not a promise or entitlement.

claimant's alpha = track pool × claimant's points / all points in that track

Solvers, findings, docs

How we currently intend to size any discretionary reward; not a promise or entitlement.

Fairness rules

Ledger and appeals

Payout schedule

How we currently intend to size any discretionary reward; not a promise or entitlement. Every part is a discretionary reward (see What an allocation is).

Changes