Ride Processing
This is the path from activity file to ride result.
Ride file
-> validation
-> climb detection
-> result review
-> CAL at ride time
-> DUNG later through settlement1. Activity Data
Boulder Roller can process FIT files, GPX files, and rides from connected sources such as Strava or Garmin.
Useful inputs include:
- GPS points
- timestamps
- elevation
- activity type
- power or heart-rate data when available
2. Validation
The system checks whether the activity is usable before accepting a result.
If the data is too flat, noisy, short, or ambiguous, the ride may produce no counted climbs.
3. Climb Detection
The detector looks for sustained uphill efforts and tries to match them to known Climbs.
The same valid ride should produce the same result when interpreted with the same parser version. Consistency matters when a result affects rewards, records, or settlement.
4. Result Review
The app can show:
- matched climbs
- your time on each climb
- ride-level CAL
- Leaderboard movement
- Local Legend or other role changes
- new climb candidates
- pending or completed processing states
BoulderScan is available for transactions, account state, Vault state, and settlement detail.
5. Reward Timing
CAL is awarded from eligible counted ride effort.
DUNG is distributed later through eligible climb roles, Vault rewards, and settlement.
Reward Paths
| Path | Uses |
|---|---|
| Leaderboard / Record Royalty | All-time top 10 climb results |
| Local Legend | Recent eligible participation |
| Staking | CAL deposited into a Climb's Vault |
| Protocol and liquidity buckets | Operations and liquidity support |