Network
Coverage can be asked for, and funded.
A map built only from where contributors happen to be has holes in it. A bounty pays to fill a specific one.
How a bounty runs
Request, measure, verify, pay.
-
01
Request
A buyer funds a campaign: a place, a network, a metric, a count, a window.
-
02
Measure
Devices that match the campaign pick it up. Matching is on network class and region, never on identity.
-
03
Verify
Submissions pass the same gates as everything else. A bounty does not buy a shortcut through verification.
-
04
Pay
The pool splits across the contributors whose readings were verified. Unfilled campaigns refund.
Example campaigns
The shape of a bounty.
These are worked examples of the format, not open campaigns.
-
Example
Manchester, Vodafone 5G
Latency and packet loss across the city at peak hours, on one operator and one network class.
-
Example
Lagos, fixed broadband
Throughput and stability on fixed lines, where independent measurement is thinnest and most needed.
-
Example
Frankfurt, route to one cloud region
Latency and jitter from consumer connections to a single cloud region, measured from outside that provider.
Sample dataNo bounty is open, no pool is funded, and no campaign has been paid. These examples exist so the format can be reviewed.
Rules
What a bounty cannot do.
- A bounty cannot ask for a result. It funds measurement of a place and a metric, and the answer is whatever the devices report.
- A bounty cannot lower the verification bar. Readings submitted against a campaign pass the same gates as any other reading.
- A bounty cannot target an individual. Campaigns are scoped to a region and a network class, never to a device or a household.
- A bounty that does not reach its target does not pay out a partial dataset. It refunds, and the readings still count toward the public map.
Fund the coverage you need
Campaigns open once the measurement network does.