At the Web3 Summit 2025, @gavofyork's PPT introduced the concept of ZkJAM. The JAM protocol can support various rollups protocols through service abstraction, including OP and ZK rollups, and enable native protocol interoperability. However, the ZkJAM in this meeting seems to be about zk-ifying Polkadot's PolkaVM (RISC-V VM). The following image compares the costs of the JAM protocol based on the proactive verification Elves algorithm (similar to fraud proof, but more proactive) and the JAM protocol based on ZK verification (no need to repeatedly execute transactions, only verify transaction proofs). In the next 12 months to several years, as ZK efficiency continues to improve, JAM may adopt ZK or a hybrid mode. Therefore, from another perspective, this explains why Risc0 has separated its brand, while the protocol uses the @boundless_xyz brand. ZKVM will become a broader infrastructure. Previously, @anoma's resource machine (similar to but different from EVM, which I will write about separately) was implemented using Risc0's RISC-V ZKVM. In the future, more projects may adopt this VM system, including potentially JAM.

I was inspired by this interview. See what the developers have to say. mp.weixin.qq.com/s/gPiNZY3xifw...… @polkaworld_org