- Data completeness
- 67%
- Confidence
- 69%
- Sources
- 4
- Last reviewed
- 7 Jun 2025
The take
What to know
Chronicle is a veteran oracle provider originating from MakerDAO that delivers gas-efficient, verifiable data feeds to the Tempo ecosystem. It is currently available for integration on Tempo's testnet environment with a transparent whitelisting model for developers.
Best for
- +DeFi protocols requiring low-cost on-chain price feeds
- +Stablecoin and RWA collateral verification
- +Institutional payment and settlement applications
Watch out
- Feed access is whitelist-gated and requires implementing the SelfKisser pattern or manual approval
- Mainnet production feed availability should be confirmed directly with Chronicle Labs
The record
Key facts
- Origins
- Established in 2017 as the original oracle for MakerDAO to support the SAI stablecoin· 60%
- Core Technology
- Scribe protocol utilizing Schnorr signature aggregation for gas efficiency· 96%
- Integration Status
- Publicly integrated and documented for Tempo Testnet Moderato· 60%
- Access Model
- Whitelist-protected data feeds; testnet users can self-whitelist via the 'SelfKisser' contract· 60%
The timeline
History
2017
MakerDAO Origins
Developed as the first oracle on Ethereum to facilitate SAI, the predecessor to the DAI stablecoin.
2023-09
Independent Spin-out
Chronicle Protocol opened access beyond the MakerDAO ecosystem to all Web3 builders as an independent entity.
2026
Tempo Integration
Listed as an ecosystem infrastructure partner for Tempo, providing documented support for Testnet Moderato.
Questions
FAQ
- What is Chronicle's primary function on Tempo?
- Chronicle acts as an infrastructure partner providing verifiable price feeds for tokenized assets and stablecoins to support on-chain financial markets.
- How does Chronicle maintain low costs for users?
- It uses the Scribe protocol and Schnorr signatures to aggregate validator signatures, reducing gas costs for on-chain verification.
- Can any developer read Chronicle feeds immediately?
- No. Feeds are read-protected by a whitelist; however, developers can use a 'SelfKisser' contract to whitelist themselves on the Tempo testnet.