Step-by-Step Guide to Proving Canister Code Authenticity On-Chain
True decentralization requires that any independent third party can verify that running canister code exactly matches open-source repository releases without relying on developer assertions.
ICPay maintains reproducible build environments allowing anyone to verify live canister module hashes.
───────────────
Core Technical Architecture & Mechanisms
───────────────
1. Deterministic Containerized Builds
Build scripts compile Motoko source code in isolated environments, producing identical WebAssembly bytecode with matching cryptographic hashes.
2. Live Canister Status Queries
Querying canister_status on canister 6vbhm-nqaaa-aaaan-q6muq-cai returns the active module_hash directly from IC subnet consensus.
3. Continuous Hash History
The Transparency Explorer tracks every historical release hash alongside corresponding Git commit hashes.