[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  CRYPTO WELSH🍊,💊🔥 [@Hasdot313](/creator/twitter/Hasdot313) on x XXX followers Created: 2025-07-21 13:05:00 UTC Been geeking out over @build_on_bob architecture lately — and if you’re into zero-knowledge tech and dev tooling, this one’s for you. Let’s talk about one of the most powerful components under the hood: Rust zkVM, powered by RISC Zero. This is where @build_on_bob really starts to feel next-level 👇 @build_on_bob uses RISC Zero’s zero-knowledge virtual machine (zkVM) — which means developers can prove that code was executed correctly off-chain, and then verify that proof on-chain in a trustless way. Yes, that includes arbitrary Rust code — verifiable by Ethereum-compatible contracts. You can use the Bonsai ZK SDK to generate these proofs on your own machine. Then the proof gets verified on-chain by the RISC Zero verifier contract. No middlemen. No guesswork. Pure cryptographic assurance. Currently, this is live on: @build_on_bob Mainnet @build_on_bob Sepolia (Testnet) Now, one of the most exciting use cases is the ability to prove ownership of a Bitcoin Taproot address — without revealing your private key. Here’s how it works: You pass a Bitcoin private key into the zkVM. It derives the public key and creates a zk-proof. That proof is submitted to @build_on_bob (Sepolia). The private key never touches the chain. Only the proof does. It’s a super-secure and private way to connect your BTC identity to @build_on_bob. ⚠️ Important: Don’t use real private keys here! For testing, always generate a new, throwaway key. Even though zkVM doesn’t leak your key, it still receives it — and best practice is to never mess with keys tied to real funds. Also worth noting: this demo only works for pubkey-based Taproot addresses (not script-based), and only supports wallets built using ord and bitcoin-core. For devs who want to dive in: The guest logic for the proof runs in bonsai-prover/main.rs The actual proving logic for taproot ownership lives in taproot_prover/main.rs This is where the private key is used to derive a bech32m BTC address and an Ethereum-compatible verifier address. In production, you'd likely swap that logic out — the EVM address shouldn’t be derived from the same trusted environment for security reasons. But it’s a great demo of what’s possible. Overall, what @build_on_bob is doing with Rust zkVM is a game-changer for Bitcoin x DeFi. It brings serious privacy, verifiability, and trustlessness to a space that’s long needed more of it — and it’s giving devs a real toolkit to build powerful, secure apps on top of Bitcoin. If you're into zk, @build_on_bob is one of the few Bitcoin-first projects really doing it right.  XXX engagements  **Related Topics** [virtual](/topic/virtual) [hood](/topic/hood) [Post Link](https://x.com/Hasdot313/status/1947281657838407772)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
CRYPTO WELSH🍊,💊🔥 @Hasdot313 on x XXX followers
Created: 2025-07-21 13:05:00 UTC
Been geeking out over @build_on_bob architecture lately — and if you’re into zero-knowledge tech and dev tooling, this one’s for you.
Let’s talk about one of the most powerful components under the hood: Rust zkVM, powered by RISC Zero.
This is where @build_on_bob really starts to feel next-level 👇
@build_on_bob uses RISC Zero’s zero-knowledge virtual machine (zkVM) — which means developers can prove that code was executed correctly off-chain, and then verify that proof on-chain in a trustless way.
Yes, that includes arbitrary Rust code — verifiable by Ethereum-compatible contracts.
You can use the Bonsai ZK SDK to generate these proofs on your own machine. Then the proof gets verified on-chain by the RISC Zero verifier contract. No middlemen. No guesswork. Pure cryptographic assurance.
Currently, this is live on:
@build_on_bob Mainnet
@build_on_bob Sepolia (Testnet)
Now, one of the most exciting use cases is the ability to prove ownership of a Bitcoin Taproot address — without revealing your private key.
Here’s how it works:
You pass a Bitcoin private key into the zkVM.
It derives the public key and creates a zk-proof.
That proof is submitted to @build_on_bob (Sepolia).
The private key never touches the chain. Only the proof does.
It’s a super-secure and private way to connect your BTC identity to @build_on_bob.
⚠️ Important: Don’t use real private keys here! For testing, always generate a new, throwaway key. Even though zkVM doesn’t leak your key, it still receives it — and best practice is to never mess with keys tied to real funds.
Also worth noting: this demo only works for pubkey-based Taproot addresses (not script-based), and only supports wallets built using ord and bitcoin-core.
For devs who want to dive in:
The guest logic for the proof runs in bonsai-prover/main.rs
The actual proving logic for taproot ownership lives in taproot_prover/main.rs This is where the private key is used to derive a bech32m BTC address and an Ethereum-compatible verifier address.
In production, you'd likely swap that logic out — the EVM address shouldn’t be derived from the same trusted environment for security reasons. But it’s a great demo of what’s possible.
Overall, what @build_on_bob is doing with Rust zkVM is a game-changer for Bitcoin x DeFi.
It brings serious privacy, verifiability, and trustlessness to a space that’s long needed more of it — and it’s giving devs a real toolkit to build powerful, secure apps on top of Bitcoin.
If you're into zk, @build_on_bob is one of the few Bitcoin-first projects really doing it right.
XXX engagements
