historical-balances
API reference for the DALP historical-balances token feature, attached automatically by most instrument templates without operator input.
The historical-balances token feature records a balance checkpoint for every holder at every block where their balance changes. It attaches without operator input on almost every instrument template.
For the operator how-to, see Historical balances how-to. For the architecture model, see Historical balances architecture.
Configuration
No featureConfigs entry required. The feature is self-contained and attaches when the selected template lists it in requiredFeatures.
Reading snapshot data
Use the token holders-and-transfers endpoints to read balance history.
| Endpoint | Returns |
|---|---|
GET /api/v2/token/{address}/holders | Current holder list and balances. |
GET /api/v2/token/{address}/holders/{holder}/history | Balance checkpoints for a holder. |
GET /api/v2/token/{address}/balance-at-block?block={n} | Balances for the asset at a specific block. |
See Token holders and transfers for the full contract.
Related
- Voting power — uses historical-balances for snapshot weights.
- Feature constraints
Token features API
Reference index for the eleven DALP token features and the dapi endpoints that configure and operate them during asset creation and servicing.
voting-power
API reference for the DALP voting-power token feature, which exposes delegation and snapshot-based governance weights paired with historical-balances.