Chronicle’s VAO dashboard is the first transparency layer for oracles and tokenized RWAs, giving institutions, builders, and policymakers easy-to-access visibility into how asset data is sourced, verified, and monitored onchain.
Chronicle Oracles have launched on Avalanche. Developers can access 140+ resilient, robust data models for crypto and tokenized assets.
Wade Prospere
Wade Prospere·
As you look at the cover image above, you see a pleasing element of ‘Scroll Inception’- a scroll within a scroll, illustrated by Chronicle’s Scribe, the next-generation Oracle that unlocks huge scalability, cost-efficiency, and transparency benefits for developers on Ethereum Mainnet and L2s.
With Scroll’s bytecode-level compatibility, integrating Chronicle, the first Oracle network on Ethereum, is a breeze for Scroll builders. Similarly, if you’re already leveraging Chainlink, a simple contract address swap to Chronicle's equivalent price feed Oracle is all it takes to get started.
63+ real-time data feeds, including cryptocurrency prices, yield rates, and RWAs, are primed and ready for developers working on the latest innovations in DeFi, Real-World Assets, and beyond. Builders can now access the same Oracle network that has secured MakerDAO since 2017, leveraging unmatched security and Lindy.
Choose from a range of asset pairs, including WBTC/USD, WSTETH/USD, and DAI/USD, and take advantage of the unique benefits of Chronicle’s Oracles - full transparency over where the Oracle reported data was sourced, who reported/signed it, and how the final reported value was calculated. We are proud to be the first Oracle network to move away from the opaque ‘black box’ design that all others employ.
With transparency comes trust minimization. These are values both we at Chronicle and the team at Scroll can fully align on. When bolstered with verifiability, developers have no questions about any element of the Oracle reported data—more on that below in the TL;DR on Scribe.
If you’re interested in bolstering your protocol, DeFi Dapp, or anything else with a custom Oracle designed by Chronicle, or would like to integrate any of our existing real-time price feeds, please reach out to us directly in Discord or via email to gm@chroniclelabs.org
The TL;DR on Scribe
Choosing an Oracle to secure your protocol and its TVL is the most important consideration of them all. With that in mind, we’ve prepared a short rundown of the questions every Oracle user should have definitive, verifiable answers to and how Scribe stacks up:
Where does the data come from?
Chronicle Scribe displays every data source in real-time and historically via The Chronicle, our on-chain dashboard. Pick an Oracle, choose a time and date on the graph, and hit the drop-down arrow on any validator to see which exchanges they queried for the price data.
wstETH/USD Oracle sources & values
Oracle providers that use low volume and low liquidity exchanges or liquidity pools for data sources are the reason behind most DeFi protocol attacks. Every Oracle protocol should provide complete data source transparency to their users, and in a cryptographically verifiable way - not just words and images. Don’t trust, verify.
An example of the cryptographic signature verification feature from the dashboard
How many validators or signers does the protocol have?
At Chronicle, we refer to these protocol actors as validators. By other providers, they are sometimes referred to as signers or Oracles. Essentially, these are the actors that operate the nodes on the protocol that attest (or sign) to the integrity of the reported data (such as the price of BTC/USD at a specific time).
This is how to establish truth in an Oracle network. Enough of these nodes must report back with the requested data to develop a consensus. However, if a bad actor can gain control of the majority of these nodes, they can manipulate the reported data. Therefore, the more validators or nodes an Oracle protocol has and the more distributed (or decentralized) they are, the more secure it is from being hacked.
Using The Chronicle, anyone can see who Chronicle Protocol’s validators are, which cryptocurrency pairs or Oracles they are sourcing data for, and when their reported data was last updated.
Scribe is the first Oracle design to pioneer the use of Schnorr signatures. This allows Chronicle Protocol to scale to an unlimited number of validators. No other Oracle protocol can achieve this as they all use an implementation of ECDSA that has a linear relationship between the number of validators and the cost of operating the Oracle.
Oracle networks constructed in this way must keep validator or signer numbers low to maintain a lower operating cost, sacrificing better security and decentralization.
A real-time view of the protocol validators from The Chronicle dashboard
Who are the protocol validators or signers
Knowing the identity of the validators is just as important as the total number. This is because an actor running a node can report any data they please. For example, they could have the node report that BTC is worth $10,000 when the market value is $40,000, creating an attack vector and draining the DeFi protocol the Oracle ‘secures.’
Therefore, decentralized and distributed nodes should be at the top of your Oracle provider shopping list unless you want your Oracle provider to have the power to drain your project. Right now, more than one Oracle provider runs all or the majority of its protocol’s nodes themselves, securing millions of dollars of TVL. Nothing stops them from draining your project if they get compromised. This is the risk of using a centralized Oracle.
At Chronicle, all of our validators are distributed and identifiable, and many are operated by well-known brands with a good reputation and track record—projects such as MakerDAO, Infura, Gnosis, Gitcoin, Etherscan, and DeFi Saver. Our goal is to create a validator community of some of the most used protocols in the space, creating a positive feedback loop of increasing security and decentralization.
A selection of Chronicle Protocol’s validators
What does it cost to operate the Oracles?
Oracles are very gas-hungry. For example, every time the BTC/USD Oracle (or Feed) updates to the latest price, this has a gas cost as it is required to post the result on-chain. Regardless of L1 or L2, the more updates, the more cost, and the Oracle provider shoulders that cost. Therefore, many Oracle providers look to update the data less frequently. This creates stale data and opens up opportunities for arbitrage, with both the Dapp and the user of the Dapp losing out.
With Scribe, we have tackled the underlying engineering problem behind the high cost of operating Oracles. The result is an Oracle that costs up to 6x less than Chainlink to update and 3.5x less than Pyth (on L1 and L2). This was achieved using Schnorr signatures - to read more about that, check out this research report by Token Terminal.
About Chronicle Protocol
Chronicle Protocol is a novel Oracle solution that has exclusively secured over $10B in assets for MakerDAO and its ecosystem since 2017. With a history of innovation, including the invention of the first Oracle on Ethereum, Chronicle Protocol continues to redefine Oracle networks. A blockchain-agnostic protocol, Chronicle overcomes the current limitations of transferring data on-chain by developing the first truly scalable, cost-efficient, decentralized, and verifiable Oracles, rewriting the rulebook on data transparency and accessibility.
