Blockchain Core 0.17.2 / Policy
Trusted contracts
Register reviewed chain and contract identities with narrow method allowlists.
Add a site-owned record
Open Blockchain → Trusted Contracts. Record the exact CAIP-2 chain, canonical address, HTTPS provenance, capability, risk, and narrow read or write method signatures. Verify every value against an independent authoritative source before approval.
Administrator approval means the site accepts the record; it is not independent contract verification. Removing a record changes local policy only and performs no on-chain action.
Installed-code records
Reviewed extensions may contribute records through ctbc_web3_trusted_contracts_v1. These records are read-only in WordPress and must be changed in the owning package. Treat any new contributor as security-sensitive installed code.
Validation boundary
Consumers validate a registry ID with ctbc_validate_trusted_contract_v1() or CointactedWeb3.contracts.validate(). Validation confirms policy identity; it does not call an RPC endpoint, simulate a transaction, obtain user consent, or authorize execution.
Writes still require the exact method allowlist, capability, adapter, simulation, immutable intent, explicit confirmation, idempotency protection, active-wallet checks, and wallet prompt.