A bug means that even though the validators didn't sign off on some header, we say that we approve an inner circuit. What you can do in your light client is if for the same block number there are two block headers that both passed all these checks. That's a sort of assertion we can add inside our light client and we can change some flag from like... So you don't support forking them? What if there is actually a long fork that then reconciles itself in the six block finality period? There is some sort of... You are making some choice there that might be slightly different than the each stock fork choice rule. Although yeah, I'm sure it exists.
In this week’s episode, Anna and Tarun speak with Succinct Labs. Guests Uma Roy and John Guibas discuss their interest in ZK, their work with 0xparc and the goals of Succinct Labs - that is to provide proof of consensus through SNARK-based light clients. Acting similar to IBC, but in the Ethereum context, we discuss the challenge of building ZK-based light clients on Ethereum, their first implementation linking Gnosis Chain to Ethereum, and how they imagine interacting with the larger blockchain space.
Here are some additional links for this episode:
Today's episode is sponsored by Aztec. Aztec Network is building the first privacy-enabled zkRollup on Ethereum.
The team is proud to announce Noir, the world's first universal ZK language. Noir makes it safe and intuitive to write privacy-preserving ZK circuits.
Aztec is now hiring engineers and cryptographers to build the execution layer supporting Noir's private smart contracts.
Join the team making private Ethereum a reality. You can learn more by visiting aztec.network/careers.
If you like what we do: