Getting Started
Herodotus Builders Guide
This page will show you how to use Herodotus step by step. You'll learn what you can do with Herodotus and the Herodotus API. Our API allows you to generate storage proofs. If you want to know more about storage proofs, check out this article.
Are you interested in accessing historical data from one chain and using it in another? Would you like to retrieve the balance of a specific account on one chain and utilize it on another chain?
With the help of storage proofs, you can achieve this without the need for an external bridge. Storage proofs allow you to access data across different chains and even retrieve information from older blocks.
Currently, the Herodotus API supports the following environments. For more details on available API methods, refer to this page.
On-chain Data available:
- GOERLI → STARKNET_GOERLI
- GOERLI → ZK_SYNC_ERA
Features:
- HEADER_ACCESS
- blockNumber
- blockHash
- parentHash
- timestamp
- proposer
- stateRoot
- transactionsRoot
- receiptsRoot
- ACCOUNT_ACCESS
- nonce
- balance
- codeHash
- storageHash
To learn more about what you can do with Herodotus, check out the examples we've provided using real-world projects like StarkSight and MAID, which demonstrate how to use storage proofs to achieve specific use cases.
How to get started building on storage proofs and using the Herodotus API
The Herodotus API allows applications to access storage proofs from different chains. Developers can interact with on-chain data and send different types of access.
Will be different by each API access point
[1] Design: Determine the data you want to read and how to use it.
Will be different by each network
[2] Request: Create an API request body based on the requirements you want to test.
[3] Access: You can call the FactRegistry contract directly or call the API task to get the result and use it.
Last modified 3mo ago