Quick Start
This guide walks through verifying a deployed Soroban contract against its source.
Prerequisites
Section titled “Prerequisites”- A deployed contract address on a Stellar network (testnet or mainnet).
- The source repository and the exact commit the contract was built from.
- The Rust toolchain and
wasm32v1-nonetarget used for the original build.
1. Install the CLI
Section titled “1. Install the CLI”# placeholder — installation method TBDcargo install vrfier-cli2. Verify a contract
Section titled “2. Verify a contract”Point Vrfier at the on-chain contract and your local source tree:
vrfier verify CC4U…7Q2 \ --source ./my-contract \ --network testnetVrfier will:
- Resolve the contract’s installed WASM hash from the ledger.
- Rebuild the source in a pinned, reproducible environment.
- Compare the hashes and print the verdict.
✔ Rebuilt WASM hash: 9f2c…a1b4✔ On-chain WASM hash: 9f2c…a1b4✔ VERIFIED — source matches deployed bytecode3. Publish the result
Section titled “3. Publish the result”Submit the verification so others can find it in the public registry:
vrfier publish CC4U…7Q2 --source-url https://github.com/you/my-contractUsing Vrfier in CI
Section titled “Using Vrfier in CI”Add a verification step to your pipeline so every release proves its bytecode:
- name: Verify contract source run: vrfier verify "$CONTRACT_ID" --source . --network mainnetNext steps
Section titled “Next steps”- Learn what happens under the hood in How Verification Works.