Skip to content

Vrfier

Prove that a deployed Soroban contract is exactly what its source code says it is — reproducibly, and open to anyone.
$vrfier verify CC4U…7Q2 —source ./contracts

Why Vrfier

Trust the bytecode, not the promise

Anyone can deploy a Soroban contract and claim it does what their GitHub repo says. Vrfier closes that gap: it reproducibly rebuilds the source, compares the resulting WASM hash to what’s live on Stellar, and publishes a verdict everyone can independently re-check.

⛓️

Reproducible builds

Pinned toolchains and deterministic compilation mean the same source always yields the same bytecode — no “works on my machine.”

🔍

On-chain matching

The rebuilt WASM hash is compared directly against the contract’s installed code on the Stellar ledger.

🌐

Open & re-checkable

Every verification records the inputs needed to reproduce it. Don’t trust Vrfier — re-run it yourself.

Built for developers

A single CLI command, CI-friendly output, and a registry your users can browse before they sign a transaction.

How it works

From source to verified in three steps

Submit

Point Vrfier at a contract address and the source repository plus the commit that produced it.

Rebuild

Vrfier compiles the source in a pinned, reproducible environment and hashes the resulting WASM.

Match & publish

The hash is compared to the on-chain code. A match earns a verified badge anyone can audit.

Ship contracts people can trust

Add source verification to your Soroban project in minutes and give your users on-chain proof of what they’re interacting with.

Read the Quick Start →