Consortium governance model
Who may join, who approves new members, how chaincode or contract upgrades are agreed, and what happens when a member leaves, written as a document the members sign off.
Service · Blockchain
Commission us to design and stand up a permissioned network that a group of identified organisations can run together. We cover membership and identity, data privacy between members, the business logic on the ledger and how each party operates its nodes.
Fabric and Besu both considered
Governance written before code
Per-member node runbooks
Deliverables
Who may join, who approves new members, how chaincode or contract upgrades are agreed, and what happens when a member leaves, written as a document the members sign off.
Organisations, peers or validators, ordering or consensus nodes, and channels or privacy groups, sized for fault tolerance and mapped to which member runs what.
Certificate authorities per organisation for Fabric, or node permissioning and account allowlists for Besu, with documented issuance and revocation.
Chaincode in Go or TypeScript for Fabric, or Solidity contracts on Besu, with endorsement or validation rules that reflect how members actually approve transactions.
Services that connect each member’s existing ERP, document or reporting systems to the network, so staff keep working in tools they know.
Early decisions
Fabric suits channel-based privacy and flexible endorsement between organisations; Besu suits teams that want Ethereum tooling, Solidity and a possible path to public networks.
Separate channels, private data collections with hashes on the shared ledger, or Besu privacy groups, each with different implications for who sees what and how disputes are evidenced.
Raft ordering for Fabric or QBFT for Besu, sized so the network survives the loss of the nodes you expect to fail or misbehave.
Every member runs its own nodes, one operator hosts on behalf of all, or a mix. This decides how decentralised the network really is.
Which organisations must sign before a transaction counts, balanced so one absent member cannot halt business but one rogue member cannot act alone.
Engagement
We meet representatives from each organisation to agree the shared process, the data each party contributes, what must stay confidential and who arbitrates disputes.
Topology, privacy design, identity scheme and governance rules are written up and reviewed by every member’s technical and compliance contacts.
Chaincode or contracts, adapters and monitoring are built on a multi-organisation staging network that mirrors the production layout, including certificate rotation.
Members bring nodes online one at a time with a runbook, while we verify endorsement, privacy boundaries and recovery before the first real transaction.
Fit
Organisations that do not fully trust each other need one agreed record of shipments, claims, certificates or settlements.
Commercial terms or personal records rule out a public chain, yet a shared, tamper-evident history is still required.
Every member can be identified, contracted with and removed, so open participation offers nothing useful.
Alternatives
If anyone should be able to verify or transact without permission, a public chain or rollup is the right base.
Open registerWhere a single company is trusted by all parties, an integration platform with audit logging is simpler than a consortium.
Open registerIf partners only need to send each other records reliably, well-designed APIs are cheaper to build and govern.
Open registerTechnology rarely sinks a consortium network. Disagreement does: over who pays for nodes, who can add members, and how an upgrade is approved when one party is slow to respond. We write these rules down with the members before building, because retrofitting them into endorsement policies is painful.
Hyperledger Fabric was designed for enterprise consortia, with channels, pluggable endorsement and chaincode in general-purpose languages. Besu is an Ethereum client that can run permissioned networks, which suits teams that already know Solidity or want compatibility with public Ethereum tooling.
Neither is universally better; the choice follows the privacy model and the skills each member already has.
Putting data in a channel limits it to that channel’s members, but administrators of those peers can still read it. Private data collections narrow it further. We map each data type to the narrowest audience that still lets the process work, and document that mapping for each member’s compliance team.
A network where one vendor operates every node is decentralised only on paper. We aim for members to run their own peers or validators, with monitoring, certificate renewal and backup procedures they can follow without us.
FAQ
It is closer to a shared database where no single member holds the admin password. The value comes from members validating each other’s writes. If one party could run it for everyone, a database with audit logs is often enough.
Besu makes that path easier because it uses Ethereum tooling. Fabric can anchor hashes to a public chain through an integration. Either way, plan for it up front rather than retrofitting.
The members do, according to the governance document agreed at the start. We hand over runbooks and can stay on to support operations, but we do not become a hidden central operator.
Through channels, private data collections or privacy groups, depending on the platform. Only authorised members hold the data itself; others may see a hash proving it existed at a given time.
Related services
Fabric and Besu nodes usually run in containers, and members need repeatable deployments across their own clusters.
Open registerMost consortium data originates in members’ ERP systems, so adapters on that side decide whether the network gets used.
Open registerCertificate authorities, node access and key storage need hardening reviews in each member’s environment.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.