Skip to content

Blockchain Core 0.17.2 / Overview

Blockchain Core overview

Provider-neutral wallet, network, proof, contract, and transaction policy for Cointacted integrations.

2 min read / Updated August 28, 2026

Blockchain Core

Blockchain Core is the free provider-neutral foundation for wallet-enabled Cointacted products. It defines the contracts that wallet providers and reviewed add-ons share; it does not bundle a wallet provider, private RPC credentials, or a transaction executor.

What Core owns

  • Network identities and public network metadata
  • Wallet-session state, connect and disconnect requests, and provider discovery
  • Signed-proof and Sign-In with Ethereum request contracts
  • Immutable transaction intents, previews, confirmations, and lifecycle facts
  • Trusted contract records with narrow read and write method allowlists
  • Typed callable schemas for reviewed contract methods
  • An optional, redacted transaction journal for signed-in users

Provider packages such as MetaMask own provider loading and wallet-specific behavior. Blockchain Tools owns advanced reads and guarded transaction sending. Core supplies policy and validation so those packages do not invent incompatible security models.

Free product boundary

Blockchain Core is always free. Installing it does not grant transaction authority and does not unlock a paid provider feature. A trusted contract record, callable schema, enabled network, or site capability is one required policy input—not user consent and not permission to send.

Fresh documents wait for an explicit visitor action before connecting an injected wallet. Public manifests contain safe network metadata only.

The optional transaction journal is disabled by default. Administrators may make it available, but each signed-in user must separately consent to the current policy. Journal entries are capped and expire automatically. They exclude wallet and recipient addresses, amounts, calldata, proofs, provider credentials, and RPC URLs.

Safe integration model

Reviewed consumers request the public Wallet Session facade rather than Core internals. Writes still require the exact chain, contract, method, capability, active wallet, simulation, immutable intent, explicit confirmation, idempotency check, and wallet prompt. Unknown or mismatched contracts fail closed.

Start here

Follow installation and trusted-contract setup, then use the administrator and privacy guide to configure networks, consent, schemas, and production safety checks.

Was this documentation helpful?Your response helps us improve this page.