Configure which token operations are permanently recorded on Dash Platform for transparency, compliance, and auditability. All flags default to TRUE.
Quick Reference
What is History Tracking?
What it is: History tracking creates permanent, queryable records of specific token operations stored directly on the blockchain. Each tracked operation includes timestamps, amounts, participants, and contextual data.
Why it matters: History tracking enables transparency, regulatory compliance, dispute resolution, and analytics. It allows token holders, auditors, and applications to query past events and verify the complete lifecycle of tokens.
Default behavior: All six history tracking flags default to TRUE, meaning all operations are tracked unless you explicitly disable specific types. This ensures maximum transparency by default.
Trade-off: More tracking provides better transparency and auditability but consumes more blockchain storage and increases transaction costs. Less tracking reduces costs and enhances privacy but limits forensic capabilities.
Trackable Operations (6 Flags)
1. Transfer History (keepsTransferHistory): Record when tokens move between addresses, including sender, receiver, amount, and timestamp. Supports encrypted notes for confidential transfer metadata (shared/private).
2. Freezing History (keepsFreezingHistory): Record when token balances are frozen or unfrozen, essential for compliance and security auditing.
3. Minting History (keepsMintingHistory): Record when new tokens are created, documenting supply expansion events with recipient and quantity details.
4. Burning History (keepsBurningHistory): Record when tokens are permanently destroyed, tracking supply reduction and the burning address.
5. Direct Pricing History (keepsDirectPricingHistory): Record when direct purchase pricing is modified, maintaining a historical price record for valuation analysis and marketplace transparency.
6. Direct Purchase History (keepsDirectPurchaseHistory): Record marketplace purchases where tokens are acquired directly from the contract owner (not peer-to-peer transfers).
Notes and Metadata
Transfer notes: The transfer operation supports encrypted notes up to 2048 characters. These can be shared (encrypted for both sender and receiver) or private (sender-only).
Character limit: All notes fields across token transitions have a maximum length of 2048 characters. This limit applies system-wide to maintain storage efficiency.
Encryption capability: Notes use identity-based encryption, enabling confidential metadata exchange while maintaining privacy for sensitive transaction details.
Implementation Considerations
Storage costs: Each tracked operation consumes blockchain storage. High-volume tokens should carefully select which operations to track to manage costs. Transfer tracking typically has the highest cost due to transaction frequency.
Privacy implications: History tracking makes operations permanently visible (though notes can be encrypted). Consider whether full transparency aligns with your token's privacy requirements.
Query performance: Tracked events are indexed and searchable, enabling efficient historical queries for wallets, explorers, and analytics tools.
Immutability: Once deployed, history tracking settings typically cannot be disabled (though they may be governable depending on your change control configuration). Choose carefully based on long-term requirements.
Token actions: Dash Platform supports 11 transition types (Burn, Mint, Transfer, Freeze, Unfreeze, Destroy Frozen Funds, Claim, Emergency Action, Config Update, Set Purchase Price, Purchase). History tracking determines which transitions are recorded.
