Hey @zkBridge team - read your newest paper on zk bridging and would love to learn more, if someone from your team is open to chatting.
A small update from our team:
We’ve now completed a circuit capable of transitioning from one beacon chain header root hash to another:
The cost of processing one update is now down to 330K (getting quite closer to the theoretical minimum of around 250K for verifying a single Groth16 ZK proof). There are only two remaining Solidity computations that can still be moved to the circuit to arrive at the final fully optimized version.
A complete header-to-header transition is also what we needed for creating recursive proofs, so our next primary goal would be developing the one-shot syncing solution.
We have now completed a recursive version of our circuit which can be used by any Ethereum client to implement one-shot syncing capabilities similar to the ones available in the Mina protocol (please see our analysis regarding the limitations of this approach):
In the coming months, we’ll be porting our proof verification contracts to many other blockchains and we’ll be aiming to implement a recursive circuit verifying aggregated signatures from the entire validator set, instead of just the sync committee, which should significantly increase the crypto-economic security of the bridge.
Trying to restore this post, which was unfortunately flagged by the system.
Our light client is now being used in production to secure the Gnosis omnibridge from Ethereum → Gnosis: https://twitter.com/SuccinctLabs/status/1676714807276470272!
An updated address to receive the Phase 2 of the grant is here: 0x1c95dfADB4984267eEccF0Db04399Ee10573e4cB.