Ride Records
A ride record connects a rider, an activity, and a result under known rules.
It explains:
- why a climb counted
- why a ride earned CAL
- why a role changed
- why a later reward was owed
The public record stores the outcome, not the raw ride file.
Inputs
Boulder Roller can use:
- GPS points
- timestamps
- elevation and distance
- activity type
- effort signals such as power, heart rate, TSS, or speed
- parser and attestation version
Public State
Public protocol state focuses on compact facts:
- climb completions
- Leaderboard state
- Local Legend state
- staking positions
- settlement outputs
- claims
Raw ride files, precise private traces, and heavy verification inputs are off-chain inputs rather than public protocol state.
BoulderScan
The app summarizes what happened. BoulderScan is for transactions, account state, Vault data, settlement outputs, and decoded protocol details.