What are Zero Knowledge proofs? Magi EVM integration

in #magi • 15 hours ago

image.png

Magi EVM

The Ethereum bridge is Magi's next big release. It brings ETH and USDC onto Hive's L2, right next to BTC and HBD, and lets you swap between all of them.

The part we are proudest of is how Magi knows an Ethereum deposit is real. It doesn't ask anyone. It checks a proof.

That proof is a zero-knowledge proof. This post explains what that is in plain words, how Magi uses it (straight from our code), why so few bridges are built this way, and how it keeps costs down.


What is a zero-knowledge proof?

A zero-knowledge proof is a tiny receipt that proves a big piece of work was done correctly. Making the receipt is hard. Checking it takes a moment. And nobody can make a valid receipt for work that was done wrong.

The "zero-knowledge" part means the receipt doesn't have to reveal the work behind it. That is useful for privacy, but it is not why Magi uses it. Ethereum is public anyway. Magi uses ZK proofs because they are short, cheap to check, and "impossible" to forge.


How Magi uses it

Magi splits the bridge into two jobs: ZK proofs to know what happened on Ethereum, and TSS to hold the coins. Everything below is in our public code:
sp1-helios-magi(the prover),
zk-header-verifier(the on-chain checker) and
account-mapping(the Ethereum bridge contract).

Coming in: a deposit

  1. Ethereum is proven. A program called SP1 Helios follows Ethereum like a light wallet does: it checks the committee's signatures and that the block is final. It runs inside SP1, Succinct's zero-knowledge virtual machine, so every run comes out with a proof. The proof is a few hundred bytes.
  2. Every Magi node checks the proof. Anyone can send the proof to Magi's verifier contract. Each node checks it with the same math, and that check is already built into the Magi node software. The contract also makes sure the proof is for the real Ethereum chain, picks up exactly where the last accepted proof left off, and only moves forward. Then it stores the proven Ethereum block.
  3. Your deposit is proven too. When you send ETH or USDC to the Magi vault, the bridge contract checks a short chain of hashes showing that your transaction, and its "success" receipt, are inside a proven block. It reads your address from your own Ethereum signature. Then it credits you.

Going out: a withdrawal

  1. The witnesses sign together. Magi's elected witnesses sign the Ethereum withdrawal with threshold signatures (TSS). No single witness ever holds the vault key. This is the same system that already holds Magi's Bitcoin on mainnet.
  2. The vault moves with the committee. When the witness set changes, the vault rotates to a new key held by the new committee, the same way the Bitcoin vault did in its first live rotation on Nov 14.

No proof, no money

The bridge contract only accepts Ethereum blocks from the ZK verifier. If no proof is there, the bridge simply waits. It never falls back to trusting someone.

Even the data source is untrusted. The prover reads Ethereum from an ordinary public endpoint, and the proof checks the committee's signatures itself. A lying endpoint cannot produce a valid proof.


Why it matters

Every bridge has to answer one question: "did this really happen on the other chain?" In most bridges the answer is a person, a company or a small group of signers saying "yes, trust us." That is exactly the spot attackers go for.

With ZK proofs the answer is math. Here is what that gets you:

  • Anyone can be the watchdog. Because Magi can read Ethereum's real state, anyone can prove that the Ethereum vault sent a transaction Magi never signed. Anyone can also prove the vault's balance on Ethereum, and if it ever holds less than users are owed, withdrawals stop until the books match again. Neither check needs permission, and neither can be paused.
  • Witnesses stay light. A witness doesn't need its own Ethereum node to trust a deposit. It checks a proof. Keeping the hardware bar low means more people can run a witness, and more witnesses means a stronger, more decentralized committee.

Pushing the boundaries of crypto technology

Bridges, TSS and ZK proofs each exist on their own, but live networks that put all three together are hard to find. Most projects pick one side.|

The TSS networks hold native coins, but every node has to watch every chain itself, and the cost grows with each chain added.

Magi does both on one network: native BTC and native ETH in TSS vaults, with ZK proofs telling the vault what really happened on Ethereum. And it does it on Hive, with 3-second blocks and no gas fees for users on the L1.


How ZK cuts costs

The expensive part of following Ethereum is done once, by one prover, instead of by every witness. Everyone else just checks the receipt.

Every witness runs EthereumEvery witness checks a proof
What each witness needsTwo Ethereum clients, a 4 TB NVMe SSD, 16 to 32 GB of RAM, 25+ Mbit/s (ethereum.org)The Magi node it already runs
Heavy workRepeated on all 16 witnessesDone once per proof
When the bridge is quietNodes keep running and costingNothing is proven, nothing is paid
Adding another chainAnother full node on every witnessAnother proof, same witnesses

On top of that, the code is careful about when it pays:

  • Proofs on demand. The prover is built to work only when the bridge is waiting on something, like a new deposit or a withdrawal. An idle bridge costs nothing.
  • One proof for many users. When a request comes in, the prover waits up to 10 minutes so a single proof covers everything that arrives in that window. That caps it at 144 proofs a day for now.
  • A price cap on every proof. Each request says the most we will pay. One Ethereum update is about 53 to 72 million proving units, so at our cap a proof costs at most about 0.02 PROVE.

Succinct Network: who makes the proofs, for now

Making a proof takes serious computing power. For now, Magi buys its proofs from the Succinct Prover Network, a marketplace for ZK proofs that went live on Ethereum mainnet on August 5, 2025, together with its PROVE token (The Block). The network says it already serves more than 35 protocols, including Polygon, Mantle, Celestia and Lido.

Here is how a Magi proof gets made:

  1. Magi asks. Our prover operator sends a request: "prove this Ethereum update with this exact program, and here is the most we will pay." It pays in PROVE.
  2. Provers compete. Proving teams around the world, who stake PROVE to take part, bid in an auction Succinct calls proof contests. The lowest price wins (Succinct docs).
  3. The proof comes back, usually in 25 to 85 seconds, and the operator sends it to Magi.
  4. Magi checks it. Every node verifies it. A wrong proof is simply refused.

Our side adds its own guard rails: a 10-minute deadline per request, a saved request so a restart never pays twice, a daily proof budget and a low-balance alarm.

Why "for now"

Succinct gives us speed and uptime. It gives none of the security. A proof from Succinct is checked exactly like a proof from anyone else, and anyone is allowed to submit one. The program being proven is open source, the verifier pins its exact fingerprint, any change to it waits out a timelock of about 14 days, and our CI checks that the published program matches a reproducible build.

That means Magi can later run its own provers, or use another proving network, without changing anything users have to trust.


Hive at the front

Hive has always been fast and free to use. With Magi it already holds native Bitcoin in a vault that rotates with its witnesses. With the Ethereum bridge it reads Ethereum through zero-knowledge proofs, and holds ETH and USDC the same way.

Native custody, threshold signatures and ZK verification, all in one network, is something very few projects in crypto can show. This one runs on Hive.

The rule behind both of Magi's bridges is simple: prove what happened, then sign together. No messengers, no "trust us."


Posted via Lumen

Sort:  

You are doing great work with such a small team!

What's the best way to interact with Magi currently? the Magi.eco is still saying "This deployment is temporarily paused"