Install Blockchain Core

1. Install the current cointacted-blockchain-core.zip package in WordPress.
2. Confirm the required integrations below are available.
3. Activate Cointacted Blockchain Core.
4. Review the plugin's WordPress administration surfaces and health notices before enabling it for users.

Trusted contract extensions

Core 0.9.0 accepts trusted contract records only from installed code through the ctbc_web3_trusted_contracts_v1 filter. Registration does not grant execution authority. Confirm that every contributing extension is trusted and that its records use canonical CAIP-2 chains, exact addresses, narrow method allowlists, HTTPS provenance, and an approved or verified status.

Administrators can also open Blockchain > Trusted Contracts to approve a site-owned record. Use one canonical method signature per line and verify the chain, address, provenance, and risk before saving. Records contributed by installed code are read-only in this screen and must be changed in their owning package. Removing an administrator record does not call the contract or modify any on-chain state.

Consumers must validate registry IDs with ctbc_validate_trusted_contract_v1() or CointactedWeb3.contracts.validate() before using a record. Validation is a policy decision only: it does not call a provider, simulate a transaction, or authorize execution. Writes still require the separate transaction simulation, confirmation, idempotency, and adapter-owned wallet flow.

Core 0.17.0 allows Trusted Callable Schemas to describe either an allowed read method or an allowed write method. For a guarded write integration, first place the exact signature in the trusted contract's write allowlist, then approve a callable schema with ordered name:type inputs and outputs. The callable ID is the only contract identity a Builder component should persist. Approving the schema does not enable sending and does not bypass the separate Blockchain Tools setting, simulation, visitor confirmation, active-wallet checks, or wallet prompt.

Optional transaction journal

The redacted transaction journal is off by default. To permit cross-session receipt resumption for signed-in users, open Blockchain > Wallet & Privacy, review the disclosed fields and retention policy, enable Save a redacted transaction journal, and save changes. This grants site availability only; each signed-in user must separately consent before new records are written. Disabling the setting stops reads and writes but does not prevent a user from revoking consent or erasing existing records. Records otherwise expire after seven days; administrators can clear them immediately.

Requirements

No terminal addon is required for the shared runtime to load.

Reviewed frontend integrations can request the Wallet Session facade introduced in Core 0.16.0. A compatible provider package must also be active; Core does not bundle provider adapters or provider credentials. Confirm that the consumer loads the facade through ctbc_web3_wallet_session_enqueue_runtime and uses CointactedWalletSessionV1 instead of calling Core session internals.

Updates should be installed from a verified package while preserving the plugin slug cointacted-blockchain-core.

Return to the product overview.