Blockchain Core 0.17.2 / Developers
Blockchain Core integration contract
Integrate with Core’s public facades without depending on provider internals.
Reviewed frontend integrations enqueue the Wallet Session runtime through ctbc_web3_wallet_session_enqueue_runtime and use CointactedWalletSessionV1. Do not call private session internals or assume MetaMask is the only provider.
Use canonical ecosystem and CAIP-2 identifiers throughout. Validate trusted contracts and callable schemas by stable ID. Treat browser wallet state as volatile and recheck account and chain immediately before every sensitive operation.
Core supplies networks, session state, proofs, policy identities, immutable transaction facts, and the optional journal. Provider packages own provider discovery and wallet prompts. Blockchain Tools owns advanced reads, simulation coordination, guarded sends, and lifecycle monitoring.
An integration must fail closed when a facade, provider, chain, contract, method, capability, or user confirmation is missing. It must not place private RPC credentials, raw signatures, calldata, or secrets in public manifests, HTML, logs, analytics, or support payloads.