Legend has it that building with STARK proofs gets a lot easier when the proving workflow is handled by an API… 🫣
Link ↓
Herodotus 🛰
495 posts
Herodotus 🛰
@HerodotusDev
We build trust minimized solutions for the sovereign future. ZK-powered verifiable data and coprocessing for Ethereum and beyond 🛰
- Herodotus 🛰 reposted
Oracles tell you what happened onchain. Storage Proofs prove it. Snapshot X verifies L1 voting power cryptographically with Storage Proofs. No trusted third party. Just math. More below ↓
- Herodotus 🛰 reposted
You think your DeFi portfolio is highly diversified? Cute. Look under the hood. 10 different protocols often share the exact same oracle, same bridge, and same upgradeable proxy risks. One exploit at the base layer and your "diversified" stack goes to zero. We mapped the entire
00:00 - Herodotus 🛰 reposted
Been thinking a lot lately about how vaults in DeFi need to be reinvented. The best curated vaults today (Morpho and friends) are still running on a social contract. The curator promises to behave. That promise keeps cracking. ZK and storage proofs has finally matured enough to - Herodotus 🛰 reposted🧵 Last week's feedback on the @HerodotusDev RiskLayer beta was genuinely great, so we shipped a batch of features that were sitting behind the "is anyone going to use this?" gate. Here's what's new 👇
- Risklayer (early beta) - an experiment leveraging frontier LLMs for automated DeFi risk intelligence & scoring. Deep protocol analysis (contracts, oracles, governance, dependencies, leverage & more) in minutes. Early access live. Feedback welcome:We've been building ZK infra at @HerodotusDev for 4 years. storage proofs, cross-chain verification, trust-minimized everything. the Aave exploit broke my brain a little, not because it was sophisticated because the signs were right there and nobody had a way to catch themrisklayer.onlineRisklayer BetaExperimental DeFi risk intelligence. Outputs may break or be inaccurate; feedback is welcome.
- Compliance without fragmentation. This is what Herodotus Sentinel is for
00:00 - How do you prove a massive computation without a massive machine? Break it into chunks, prove them in parallel, stitch them back together. We wrote up how we're doing this inside @StarkWareLtd's S-two prover: medium.com/@herodotusdev/…
- Any chain. Any block. Any storage slot. Verified with zero-knowledge proofs. That's Herodotus.
- Replying to @HerodotusDevNotes: → Current focus is S-two Cairo; other AIRs can be added over time → Audit pending, use at your own risk → Contributions welcome! Repo:
- Replying to @HerodotusDevComing soon: → Direct integration into Atlantic for seamless EVM settlement → More benchmarks, including GPU-accelerated proving
- Replying to @HerodotusDevHow it works: 1.Prove your Cairo program with S-two 2. Wrap the STARK proof into Groth16 using this repo 3. Verify with Groth16 solidity verifier onchain
