ZKM

We also support: 1. Proof network with multiple high-level languages support, Golang, Rust and C/CPP @ProjectZKM 2. Agent harness platform @ClawUpAI 3. More if you need, like privacy protocol

The world knows ZKM 🌎

We had been on this for 2 months. * Upgradeable proof system for BitVM2 * Formal verification of zkVM circuits it looks slow, BUT our BitVM3 (BitVM2-GC internally) was already adapted and run on Devnet now. Security is always the first.

bitvm2-node 0.4 is live. This release: • adapts to Ziren zkVM v1.2.5 • improves how non-standard challenge/disprove transactions get mined • refactors key derivation and committee-key handling • adds better operator reliability and monitoring Meanwhile, the GOAT BitVM2 testnet has already seen: • 4.34 tBTC bridged in • 254 bridge-in txs • 251 bridge-out txs Try trust-minimized Bitcoin bridging for yourself: docs.goat.network/users/goat-bit…

* Formal verification of the entire MIPS zkVM circuits, including Linux ABIs', with Picus @VeridiseInc * Large step toward Geth/Keeper real-time proving * Upgradeable wrapping proof for GOAT BitVM2/3 Cann't wait the next version our proof system shortly * 100-bit JBR security (@Ethereum soundcalc) * >2x proving speedup

Our team ships relentlessly and it doesn't go unnoticed. Every release makes the infrastructure underneath GOAT Network stronger. This is the kind of low-level work that most people never see but that world class technology depends on. @sd_eigen and team - you keep raising the bar.💪

For @GOATNetwork (and any other Bitcoin L2 that opts to build on Ziren) this release means the proving system can keep evolving without breaking verification downstream. That's been one of the hardest infrastructure problems to get right, and this upgrade solves it. But the bigger picture: v1.2.5 makes it possible to realize realtime proving for Geth, @Ethereum's most widely used execution client. That's an industry-wide unlock. @sd_eigen and his team continue to ship at a level that doesn't get the attention it deserves. Serious, foundational work 👏

Ziren is the zkVM that powers cryptographic proof across the GOAT Network stack. This release keeps the Groth16 verification key stable across upgrades, which means the GOAT BitVM2 architecture can upgrade its proving system without disrupting verification. That's a big infrastructure problem solved. Proving systems need to evolve, but verifiers can't break every time they do. Ziren v1.2.5 makes that possible.

1/ Ever wondered how Ziren proves unmodified Geth — Ethereum’s most popular client — without touching the Go compiler? It comes down to full Linux ABI compatibility in the MIPS-based zkVM. 2/ Ziren runs standard MIPS binaries compiled against the Linux userspace ABI. The guest issues real SYSCALL instructions exactly as on native MIPS32 ELF. The zkVM intercepts them and emulates a minimal Linux kernel — memory management, I/O, and process lifecycle — sufficient for Go’s runtime. No source changes. No compiler patches. 3/ Syscalls are routed across shards for efficient proving: • Core shard decodes via SyscallInstrsChip • Precompile shard executes via SysLinuxChip (81-column AIR) • GlobalChip verifies arguments/results with half-word packed lookups 4/ Key syscalls supported for Geth/Keeper: • SYS_MMAP / SYS_MMAP2 and SYS_BRK (heap & page management) • SYS_CLONE (simulated PID for threading) • SYS_EXIT_GROUP, SYS_READ, SYS_WRITE, SYS_FCNTL • Signals + others treated as NOPs (v0=0, a3=0) All proven with strict byte-level AIR constraints (collision-resistant half-word packing + structural page alignment) for memory safety and determinism. 5/ This Linux ABI layer lets Ziren prove Geth/Keeper end-to-end — unmodified. Full details: docs.zkm.io/mips-vm/linux-…

My Telegram account with the handle @daceconomy got hacked last week and I lost control of it. Please don't respond to any message from that account. DM me here if you want to contact me.

20/ If this line of work succeeds, the implication is not just “Ziren can prove Go”. It is that zkVM design choices can materially affect which execution clients remain viable in @Ethereum’s next architecture. And that makes infrastructure choices much more consequential than benchmark charts alone suggest. zkm.io/?nocache

19/ The main takeaway: A lot of zk proving work has focused on building new proving-friendly clients. @sd_eigen's talk was different. It asked whether Ethereum’s existing dominant client can be brought into the ZK future without abandoning client diversity. That is a more important question than it may first appear.

At @EthCC, ZKM CTO Stephen Duan presented something that, to our knowledge, nobody else has done yet: proving Geth, @Ethereum’s dominant execution client, inside a zkVM. Here are the key takeaways from @sd_eigen’s talk "Prove Geth With Ziren" 🧵