Infrastructure
Contract Source Verification Service
Problem Statement
Soroban contracts are deployed as opaque WASM blobs. Without a source verification registry, users and auditors cannot confirm that the deployed bytecode matches any published source code, undermining trust in the ecosystem.
Technical Requirements
Deterministic Build: Reproducible WASM compilation pipeline (e.g., via Docker) so source-to-bytecode matching is verifiable. Registry API: Public API and UI to submit, verify, and query contract source code by contract ID. Explorer Integration: Hook into the Soroban-First Block Explorer (Q1 RFP) to surface verification badges.