Rules

United States only for now. The endpoint catalog is being seeded state by state. Other countries will follow once the data is in place.

1. Pick your endpoints. Identify the city halls or state capitols you're riding between, and create a route — segment (A → B) or chain (A → B → A, A → B → C, etc.). The first finisher of a route locks in its endpoint zones; subsequent attempts are measured against those same zones.
2. Free route. Pick whatever path you want between the endpoints. There's no required route — only the start, the waypoints (in order, for chains), and the finish are checked.
3. Ride it as fast as you can — but obey traffic laws and ride safely. No leaderboard time is worth getting hurt or putting others at risk. Stop signs are still stop signs. The clock keeps running through any stops you make on route, so plan ahead.
4. Upload your .fit file. The system verifies the GPS track passed through the endpoint zones in order, then records an attempt on every leaderboard the ride satisfies — including any chain routes that include your segments.

How timing works

Gun start, finish-line stop. The clock starts at the last GPS sample inside the start endpoint's zone — the moment your track exits — and stops at the first GPS sample inside the finish endpoint's zone. Time spent inside the start or finish zones doesn't count, so a rider just passing on the road outside doesn't trigger anything, and lingering at the endpoints can't game the clock.

Stops between the endpoints — traffic lights, water breaks, photos — keep the clock running. For chain routes (A → B → C, A → B → A), the intermediate endpoints are checkpoints: your track must enter each in order, but only the start and finish zones bound the timing.

Verification

Activities are verified from the .fit file. Indoor rides without GPS are rejected. Re-uploading the same file is a no-op — duplicates dedup by SHA-256.