Last updated
If there are omissions or errors, corrections are welcome. Thank you very much!
1. Twitter sent by the BeL2 team@Be_Layer2@sash__mit,they will advance BitVM by passing ZKPs into EVMs, turning EVM ecosystems into Bitcoin sidechain processors, opening up a scalable world of incoming smart services. https://twitter.com/sash__mit/status/1769053594832245049
2. Weikeng Chen@weikengchen from L2Iterative @l2iterative contributed a PR for u32 mul to BitVM, It took 3705 bytes in Bitcoin script. Detail PR link: Add u32_mul by weikengchen · Pull Request #12 · BitVM/BitVM, The PR has been merged now. PR link:https://github.com/BitVM/BitVM/pull/12
1.@0x_orkunfrom Citrea@citrea_xyzposted on twitter https://twitter.com/0x_orkun/status/1768043273489179018?s=46&t=BXOpr41irHcUQp1fY-JnhQ，Described the approach to verify ZK proofs with OP:
a. Represented BitVM using binary circuits, enabling the output of BitVM programs to be 1 or 0 (true or false).
b. Encoded the ZK verifier into BitVM. If the output is 0, it indicates a false ZKP. The prover submits a ZKP, and the verifier initiates challenges to prove the proof is invalid. Ultimately, 40 transactions are required to determine the validity of the ZKP.
2. Citrea @citrea_xyz posted twitterhttps://twitter.com/citrea_xyz/status/1768276018077589591，Announced the open sourcing of itsGitHub - chainwayxyz/bitvm-zk-verifier: BitVM Groth16 Verifier Toolkit - WIP，based on Risc0 prover and BitVM-based proof verification circuits, achieving the challenge verification of Groth16 proofs.
The basic process is as follows:
Creating STARK proof from a RISC Zero guest program (written in Rust)
Wrapping the STARK proof into a Groth16 proof
Crafting its corresponding Groth16 verifier in C
Compiling the verifier to rv32i instruction set
Transpiling the verifier from rv32i to BitVM instruction set
Running the BitVM simulation (To be run on-chain once BitVM is ready)
@alexeiZamyatinfrom Bob@build_on_bobsaid their vision is to create the first hybrid rollup with multiple native bridges.https://twitter.com/alexeiZamyatin/status/1767327927979418068
