Appearance
What happens to a ride
text
file -> checks -> climb matching -> results and CAL -> weekly settlementChecks
The file is validated before any result is produced. Rides that are too short, lack timestamps or elevation, or are not cycling activities produce no climb results.
Climb matching
Each climb has a start, a route, and a finish fixed from the road map before any ride. Your ride produces a result on a climb when it crosses the start, follows the route, and crosses the finish in that order. The ride supplies a time and a place; it does not alter the climb.
Sustained climbing on a hill that is not yet a defined climb is recorded as a nomination. Repeated nominations of the same hill place it under review. A nomination alone creates no climb, vault, or DUNG.
Determinism
A valid file processed under the same rules always produces the same result. This is the property that allows a result to move a leaderboard or count CAL.
States
| State | Meaning |
|---|---|
| Pending | Processing, or awaiting chain confirmation |
| Delayed | Confirmation is slower than usual; no data is lost |
| Review | The ride requires inspection before it counts (see below) |
Numbers on a ride are final only when it has left these states.
Review
A ride enters review when Boulder Roller cannot count it without a person looking. The usual causes:
- The recording's stamp did not match the processed file, or arrived incomplete.
- Power data covered too little of the ride to count CAL, or the effort could only be estimated from heart rate or the route.
- The ride was completed more than 30 days before upload, or its clock is wrong, such as a finish time in the future.
- The same activity was uploaded twice.
The ride shows Review where CAL would be on the web, or Under review on iOS. Results that depend on the review wait for it. You do not need to do anything: Boulder Roller reviews the ride, and it then either counts or is marked not counted with the reason shown. If a ride stays in review, contact support with the ride date (Contact).
Every result has a transaction behind it. The ride page links to it on Solana Explorer; BoulderScan decodes the surrounding protocol state.