FAQ

What is a Storage Proof?

A storage proof defined by Herodotus merges inclusion proofs, which confirm data's presence, and proofs of computation, which validate the execution of a multi-step workflow to attest the validity of one or multiple elements in a large dataset such as the whole Ethereum blockchain or a rollup.

What type of data does Herodotus provide?

Herodotus currently provides strictly on-chain blockchain data. If the data exists inside a blockchain archive node, it can be proven with storage proofs.

Why is the company called Herodotus?

The name "Herodotus" is inspired by the ancient Greek historian of the same name, often dubbed the "Father of History." Just as Herodotus dedicated himself to recording and preserving historical events, our company enables unlocking and accessing historical on-chain data.

While the name underscores the importance of historical data access, our solutions, like storage proofs, also enable data access for current data.

Does Herodotus support L1 to L1 data access?

No, not at this time.

What are the differences between Storage Proofs and Oracles?

• Latency: Oracles are asynchronous, leading to longer delays when accessing flat data compared to storage proofs.

• Cost: While many oracles are cheaper because no computation proof is needed, the lower security is a trade-off. Storage proofs have higher costs but offer greater security.

• Security: The data feed's maximum security from oracles is capped at the oracle's own security level. In contrast, storage proofs match the chain's security. Additionally, oracles are susceptible to manipulation attacks due to their usage of off-chain attestations.

What are the differences between Storage Proofs and Keepers?

• Latency: Both storage proofs and keepers operate at similar latencies.

• Cost: Interacting with the chain through keepers involves sending transactions, making keepers more expensive than using storage proofs.

• Security: Both keepers and storage proofs have a security level equivalent to the blockchain itself since keepers can't manipulate on-chain events.

When is it recommended to use storage proofs?

Storage proofs are best suited for applications that prioritize high security and require access to on-chain data.