MultiChain is an open-source platform for creating private, permissioned blockchains, derived from Bitcoin Core and maintained by Coin Sciences. It gives you a working chain with granular permissions, native asset issuance and key-value "streams" in minutes, configured rather than programmed. That simplicity is its main advantage and its main limit: it is excellent for shared registries and asset ledgers among known parties, and the wrong tool if you need expressive smart contracts.
Clearing up the name
"Multichain" means three different things, and search results mix them up:
- MultiChain the platform, the subject of this guide.
- Multi-chain applications, meaning dApps deployed across several public chains. For that topic, see the guides to multichain NFT platforms and multichain launchpads, and the article on interoperability and layer 2s.
- Multichain the bridge (formerly Anyswap), a cross-chain bridge that collapsed in 2023 after unexplained outflows of user funds and the detention of its CEO. It is unrelated to the MultiChain platform and is a reminder of the risks of bridges controlled by a few keys.
How MultiChain works
A MultiChain network starts from a parameters file created with multichain-util create. You set the block time, maximum block size, whether the chain is open or permissioned, native currency settings and mining rules, then start the first node with multichaind. Other nodes connect once they are granted permission. Everything is controlled through a Bitcoin-style JSON-RPC API or the multichain-cli tool.
Permissions
Permissions are granted per address and include connect, send, receive, issue, create (streams), mine, activate and admin. Admin changes can require consensus among multiple administrators, so no single party can take over the network.
Consensus: mining diversity
Rather than proof of work, permitted miners take turns in a round-robin scheme. The mining diversity parameter limits how many consecutive blocks one miner may produce, so a single node cannot monopolize the chain. It is a pragmatic model for consortiums but provides less fault tolerance than BFT protocols such as QBFT or Fabric's BFT ordering.
Native assets
Assets are issued with a single command, tracked at the protocol level in the UTXO model, and can be transferred, exchanged atomically, and reissued if allowed. You get multi-asset ledgers without writing token contracts.
Streams
Streams are append-only collections of items with keys and publishers, usable as a key-value store, time series or document log. Nodes can subscribe to only the streams they care about and index them for queries. Many MultiChain deployments use streams far more than assets, for audit trails, document notarization and shared reference data.
Smart filters
Since version 2.0, transaction filters and stream filters let you write JavaScript rules that every node runs to accept or reject transactions or stream items. They enforce business rules such as "transfers of this asset require a second signature" or "stream items must match this JSON schema," but they are validation rules, not a general smart-contract environment.
MultiChain compared with other private ledgers
| Platform | Programming model | Strength | Weakness |
|---|---|---|---|
| MultiChain | Configuration, assets, streams, JavaScript filters | Very fast to stand up; simple to operate | Limited logic; smaller ecosystem |
| Hyperledger Fabric | Chaincode in Go, Java or TypeScript | Fine-grained privacy and endorsement | Operationally complex |
| Besu or Quorum (private EVM) | Solidity contracts | Huge tooling and talent pool | Privacy needs extra design |
For deeper comparisons see Hyperledger development and private blockchain development.
Building a MultiChain solution
- Model the data as assets, streams or both, and decide who publishes and who reads each stream.
- Set chain parameters and the permission scheme, including multi-admin consensus for governance.
- Write filters for business rules and test them against edge cases.
- Build an application layer that talks to nodes over JSON-RPC, keeps keys in a wallet or HSM, and indexes data for your UI.
- Deploy nodes across participating organizations, with monitoring and backups.
A focused registry or notarization system can reach a working pilot in weeks with one or two engineers, since the chain itself needs little code. The time goes into the application, integrations and agreeing governance between participants.
Risks to weigh
MultiChain's development pace has slowed compared with its early years, and its community is small. Before committing, review the project's recent release history and support options, and design your application so the ledger could be replaced. As with any private chain, also ask whether a shared database with signed audit logs would meet the need at lower cost.
Frequently asked questions
Is MultiChain free?
The community edition is open source. A commercial edition with additional features and support has also been offered; check current licensing terms directly with the maintainer.
Can MultiChain run Solidity smart contracts?
No. It offers assets, streams and JavaScript filters. If you need Solidity, use a private EVM network such as Besu.
Is MultiChain related to the Multichain bridge?
No. They are unrelated projects that happen to share a name.