Chain Core

Enterprise blockchain software for production deployment

Powering Blockchain Networks

Chain Core is the software implementation of the Chain Protocol. It is designed to run in enterprise IT environments. Chain Core enables institutions to initiate, operate, or connect to a blockchain network.

What is Chain Core?

Chain Core is more than a blockchain node – it is an enterprise-grade distributed system that powers secure, scalable, and highly available blockchain networks.

Communication Layer

The HTTP+JSON API powers applications and enables easy integrations. RPC servers connect hosts within a Chain Core and Chain Cores within a network. Load balancers route inbound service-layer requests.

Services Layer

Robust, scalable services that index blockchain data, participate in consensus, validate transactions, and execute smart contracts.

Storage Layer

Horizontally scalable, highly available database cluster that houses blockchain and account data.

Learn more about deploying Chain Core in your organization


Chain Core can be configured to enable any type of network participation. These features are accessed using Chain Core’s API and SDK.

Issue Assets

The Asset Issuer governs the definition of asset types, issuance and retirement of assets in circulation, and supports the tracking of issuance data for insights. An asset is any type asset with quantifiable and transferable value.

  • Asset Issuer is used for creating assets.
  • Users may also query the existing asset types and their circulations and other details.
  • Before adding the block to the blockchain, the Generator obtains signatures on the block from the PBN’s configured Signers.
  • Only transactions signed using proper private keys constitute valid issuances.
Store Assets

The Account Manager consists of accounts, which are repositories for units of any asset type and their identifying information, and offers extensive data indexing to view activity and balances.

  • Using the Chain SDK, a user can connect to the Manager to create payment and other transactions and to query balances and other information about accounts.
  • Different account-management nodes on a single network house different collections of accounts.
  • To maintain confidentiality and security of transactions, every account has its own public/private keypair that is not computationally feasible to reverse.
  • Account holders redeem funds with a digital signature made from the receiver’s private key, known only to the account holder.
Create Transactions

The Account Manager service allows institutions to transfer assets from one account to another account. These transfers can happen within a single Chain Core or across Cores in a blockchain network. Transfers may also be made into and out of “smart contracts.”

  • Transfer assets between accounts
  • Transfer assets across the blockchain network
  • Transfer assets into and out of smart contracts
  • Query and interact with smart contracts
  • Validate and execute smart contracts
Block Creation & Consensus

The block generator is responsible for collecting proposed transactions from all network participants. It rejects invalid and conflicting transactions and publishes new blocks for the blockchain.

  • Transactions created via Asset Issuers and Account Managers are submitted to the Generator for inclusion in the next block.
  • The Generator validates these transactions against the current blockchain and periodically bundles the latest batch of valid transactions into a new block
  • All Cores independently validate blocks and individual transactions within each block, and verifies that the required Signers have added their signatures.
  • The appearance of a transaction in a block serves as confirmation of that transaction.
Operate & connect Netorks

The Block Signer validates and signs blocks received from the Block Generator so they may be added to the blockchain.

  • Each block in the blockchain must be digitally signed by one or more block signers.
  • Block signer independently corroborates the validity and correctness of the transactions in the block.
  • A Chain PBN must have at least one Signer, although additional Signers can be configured and required for a transaction to be validated and added to the blockchain.
  • The block generator requests signatures from all configured block signers as part of the block-publishing process.

Deploying Chain Core

Chain Core deploys to on-premise and cloud data centers. Deployment engineers are available to initiate and support production blockchain networks. Pre-deployment prototyping is available in the Chain Sandbox.

  • Integration Engineering

    A team of experts who bridge financial services and high tech is available to help you transition to a blockchain infrastructure.

  • SLAs

    Contractual commitments to uptime for mission-critical blockchain networks, backed by engineering and operations experts.

  • 24/7 On Call Support

    Engineers are standing by to troubleshoot and resolve performance, availability, and other issues you might encounter.

Designed for Developers


Multi-language support

SDKs are available in many programming languages (Java, Node.js, Ruby) for building blockchain applications.


Access raw blockchain data for unlimited extensibility. Export blocks in real time to data warehousing solutions.

HSM integration

Supports private key generation and storage, and digital signatures on authorized transactions.

Developer Center


Multi-language reference documentation for the Sandbox APIs and SDKs

Tutorials & Sample Code

Learning resources and code snippets to help you build blockchain applications

Implementation Guides

Standards and best practices for developing blockchain applications across various industries

Ready to start building with blockchain?

Get in touch to schedule a Chain Core demo.

[email protected]