Core Trust & Verification Standards
These standards form the backbone of the decentralized App Store and the software supply chain.ICRC-118: WASM Management
The Shelf. This standard manages application namespaces (
CanisterType)
and their versioned WASM histories. It’s the underlying storage layer for
all application code.ICRC-120: Canister Orchestration
The Canister Manager. This standard handles the deployment and
orchestration of canisters. Crucially, it ensures that only WASM that has
been verified by the protocol can be deployed.
ICRC-126: Verification & Auditing
The Immutable Logbook. This standard provides the immutable ledger for
verification requests and attestations. Verifiers file cryptographic
attestations after performing reproducible builds, creating a permanent
on-chain audit trail. Key Features: - Attestation filing: Verifiers
submit build verification results with metadata - Audit type system:
Supports multiple verification types (build_reproducibility_v1,
security_audit, etc.) - Consensus tracking: Records multiple independent
verifications per WASM - Authorization: Integrates with ICRC-127 bounty
system to authorize attestations - Immutable history: All attestations
stored permanently on-chain via ICRC-3
ICRC-127: Bounty System
The Economic Engine. This standard powers the decentralized bounty
system that incentivizes both automated build verification and human
security audits. Key Features: - Bounty creation: Developers fund
verification work with USDC rewards - Staking mechanism: Verifiers stake
collateral (0.30 USDC) to reserve bounties - Slashing protection: Stakes
are burned if verifiers abandon work (1-hour timeout) - Automated
payouts: Smart contracts transfer rewards upon successful verification -
Multiple verifiers: Each bounty can be claimed by one verifier, enabling
parallel verification - Divergence reporting: Verifiers earn rewards
even for failed builds (honest reporting) - Consensus-based
finalization: Majority of verifiers must agree for WASM approval
Token & Identity Standards
These standards provide the foundation for payments, credentials, and on-chain proof of quality.ICRC-1 & ICRC-2: Fungible Tokens
The Bank. These standards are the foundation of the Direct Payments
pillar. ICRC-1 is used for all token transfers, while ICRC-2 powers the
user-controlled allowance system.
Auditor Credentials (Custom)
The Identity Layer. While not a formal ICRC standard, this is a critical
component. It issues non-transferable, credential-like tokens to vetted
auditors, ensuring that only qualified experts can perform specific types of
audits.
How They Work Together
The standards form an integrated workflow:- ICRC-118 (WASM Registry): Developer registers a new WASM version with Git commit hash and expected hash
- ICRC-127 (Bounty System): Developer creates verification bounties (~$2.25 per version) to incentivize verifiers
- Verifier Network: Automated bots detect pending verifications and reserve bounties by staking USDC
- Reproducible Builds: Verifiers rebuild WASM from source in deterministic Docker environments
- ICRC-126 (Attestations): Verifiers file cryptographic attestations with build results and metadata
- Consensus: System requires 5 of 9 independent verifiers to agree on the same WASM hash
- ICRC-127 (Rewards): Successful verifiers claim bounties and receive USDC + returned stake
- ICRC-120 (Deployment): Once verified, the WASM can be deployed to mainnet via canister orchestration

