Stellar (XLM) now supports RISC Zero zero-knowledge proof verification on-chain via Groth16, enabling complex off-chain computations with on-chain validation. (Stellar (XLM) now supports RISC Zero zero-knowledge proof verification on-chain via Groth16, enabling complex off-chain computations with on-chain validation. (

Stellar (XLM) Enables RISC Zero zkVM Proof Verification in Smart Contracts

2026/02/12 14:24
3 min read

Stellar (XLM) Enables RISC Zero zkVM Proof Verification in Smart Contracts

James Ding Feb 12, 2026 06:24

Stellar (XLM) now supports RISC Zero zero-knowledge proof verification on-chain via Groth16, enabling complex off-chain computations with on-chain validation.

Stellar (XLM) Enables RISC Zero zkVM Proof Verification in Smart Contracts

Stellar (XLM) has rolled out support for verifying RISC Zero zkVM execution directly within its smart contracts, a technical upgrade that significantly expands what developers can build on the network. The integration uses Groth16 proof verification and became possible after bn254 cryptographic functions launched on Stellar Futurenet on January 22nd, 2026.

The practical implication? Developers can now run computationally intensive operations off-chain—processing megabytes of data if needed—and then verify the results on Stellar with a single transaction. That's a capability the network simply didn't have before.

How It Actually Works

RISC Zero's zkVM creates a verifiable execution environment. Think of it as running code in a secure black box that produces cryptographic proof the computation happened correctly. The Stellar smart contract doesn't need to re-run the entire computation—it just checks the proof.

Nethermind built the verifier contract that makes this possible. The workflow breaks down into three components: a "guest" program running inside the zkVM, a "host" application generating proofs locally, and the on-chain verifier contract that validates everything.

When a proof verifies successfully, the contract returns a simple unit type. No fancy confirmation message—just cryptographic certainty that the off-chain computation was legitimate.

Technical Requirements and Current Limitations

Right now, this only works on Stellar Futurenet. The bn254 functions required for Groth16 verification haven't hit Testnet or Mainnet yet, which limits immediate production use. Developers need a Unix environment (Windows users can run WSL), Rust installed, and the Stellar CLI.

The proof generation process takes a couple minutes on standard hardware. Once generated, you get three hex values—the seal, image ID, and journal SHA-256 hash—which get passed to the on-chain verifier.

What This Unlocks for Builders

Zero-knowledge proofs have been the hot infrastructure play across crypto for years, but implementation has concentrated heavily on Ethereum and its L2s. Stellar's relatively low transaction costs could make it attractive for ZK applications where Ethereum gas fees become prohibitive.

Use cases that were previously impossible on Stellar—complex financial calculations, privacy-preserving credential verification, or any logic requiring heavy computation—now become feasible. The constraint shifts from on-chain compute limits to proof generation time.

For XLM holders watching protocol development, this represents genuine technical expansion rather than marketing fluff. Whether it translates to meaningful adoption depends entirely on what developers actually build with it. The infrastructure is there; now it needs applications.

Image source: Shutterstock
  • stellar
  • xlm
  • risc zero
  • zero-knowledge proofs
  • smart contracts
Market Opportunity
Stellar Logo
Stellar Price(XLM)
$0.1563
$0.1563$0.1563
-2.73%
USD
Stellar (XLM) Live Price Chart
Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.