--- title: Private blockchains url: "https://www.unknowngravity.com/en/servicios/blockchain-privadas" site: Unknown Gravity published: "2025-01-17T15:54:19+00:00" modified: "2026-07-15T10:51:34+00:00" language: en-US description: A customized, secure and efficient solution for companies looking to take advantage of blockchain technology while maintaining total control. section: "Home > Private blockchains" --- # Private blockchains > A private blockchain is a distributed ledger network whose access and validation are restricted to authorised participants, unlike public networks. It is used when confidentiality or data control require it. Unknown Gravity deploys private and permissioned networks for companies and institutions. FULL CONTROL OVER YOUR DATA IMMEDIATE FINALITY, NO FEES GOVERNANCE AND PERMISSIONS BY DESIGN [Book a meeting](/en/meeting) A private blockchain is a distributed ledger network whose access and validation are restricted to authorised participants, unlike public networks. It is used when confidentiality or data control require it. Unknown Gravity deploys private and permissioned networks for companies and institutions. **We design and run permissioned blockchain networks for consortia: identified participants, per-record permissions, and governance settled before the first node goes up. If your case does not need one, we say so.** ## 01 / What is a private blockchain and how does it work? A private, or permissioned, blockchain is a network where every participant is identified. Nodes are run by known organizations, and a committee decides who joins, who validates and what each member reads. Consensus moves from probabilistic to deterministic: a transaction is final as soon as a quorum signs it. There is no native token for fees, and confidentiality is handled inside the protocol, through channels or private collections. In exchange, trust no longer comes from crypto-economics: it rests on the governance of the consortium. ## 02 / When it makes sense, and when an audited database is enough A permissioned network pays off when several conditions hold at once: - **Several independent organizations** write to the same record, and none of them accepts another one owning the server. - **The record must be non-repudiable**: every entry is signed, and nobody rewrites it later without leaving a trace. - **Sensitive data is involved** that only some parties should see, with permissions per document or per field. - **Reconciliation costs real money**: files, emails and separate ERP systems are cross-checked to reach the same figure. It does not pay off when one organization owns both the data and the truth. With no third party to verify, a database with an immutable audit log, signed events and WORM retention is cheaper to run. ## 03 / Use cases where a consortium adds something - **Multi-company supply chain**: manufacturer, carrier, customs and distributor record milestones on the same batch, each with its own visibility. We build it as a [product traceability system](/en/servicios/sistema-trazabilidad-de-productos) over their ERP systems. - **Financial operations between entities**: trade confirmations, collateral or promissory notes where each party keeps its own book and reconciles by hand. - **Healthcare and multi-center trials**: only the integrity proof and the consent go on chain. The GDPR right to erasure and an immutable record do not sit together; that is settled in the design. - **Verifiable credentials** between members, with revocation that works: covered in [digital identity management](/en/servicios/blockchain-para-gestion-de-identidades-digitales). ## 04 / Architecture, identity and permissions: Hyperledger, Besu and Quorum - **Hyperledger Fabric**: X.509 identities and MSPs, channels and private data collections, per-chaincode endorsement. A fit when confidentiality between subgroups rules and no token is wanted. - **Besu and GoQuorum**: full EVM, QBFT/IBFT consensus and privacy groups. A fit when Solidity tooling is already in house. - **Public network with contract-level permissions**: sometimes no network of your own is needed, just access lists and encrypted off-chain data. Permissions are designed in three layers: who connects, who writes to each contract, and who reads each record. HSM-backed key custody and its rotation belong there from day one. Anchoring the state hash to a public chain gives proof of existence without exposing content. If you issue tokens that leave the consortium the framework changes: MiCA governs crypto-assets and utility tokens; where the instrument is a transferable security, securities markets legislation rules instead (LMVSI, MiFID II), with **ERIR** (the entity responsible for registering and recording securities represented by distributed ledger technology, Arts. 7 and 8 of Law 6/2023) as the DLT registry figure. First read in the [MiCA/MiFID classifier](/en/clasificador-mica-mifid). ## 05 / Governance, deliverables and operations The usual reason a consortium never leaves the pilot stage is not technical: nobody wrote the rules. Before any node goes up we settle who admits and removes members, how an upgrade is approved, and what happens to the history if a partner leaves. Deliverables on a typical engagement: - Architecture and data model, justifying what goes on chain and what stays off it. - Governance agreement plus a role and permission matrix. - Infrastructure as code for nodes, certificate authority and ordering service. - Chaincode or contracts with test suites and a security audit before production. - Observability and runbooks: onboarding and offboarding members, certificate rotation, backup and recovery. Once live it has to be run: patches, expiring certificates, new members, versioned contract changes. If you would rather not build that team in house, we cover it as [blockchain as a service](/en/servicios/blockchain-como-servicio-baas). We have delivered 75+ projects with 0 hacks in production. FAQ ## Frequently asked questions **How is a private blockchain different from a public one?** It comes down to who validates and who reads. On a public network anyone can run a node and the whole state is visible. On a private one the validators are identified organizations and confidentiality is built in, but trust shifts to governance: if they agree, they can change the rules. **Is a private blockchain scalable?** It performs better than a public network because the validator set is small and known, but the bottleneck is rarely consensus: it is the data model, the signing policies and queries over the history. We run a load test with your own transactions before fixing the architecture. **Which industries can benefit from a private blockchain?** It is common in banking, insurance, healthcare, energy, logistics and the public sector, but the industry is not what decides: the structure is. Several independent entities sharing a process, and a record none of them should be able to rewrite alone. This page is informative. It is not legal, tax or investment advice, and it does not replace a case-by-case review. The rules cited change: check the current version on [BOE](https://www.boe.es) and [EUR-Lex](https://eur-lex.europa.eu). RELATED SERVICES [Blockchain consulting for companies](/en/servicios/consultoria-blockchain) [Tokenomics](/en/servicios/tokenomics) [Whitepapers](/en/servicios/whitepapers) [Blockchain protocol development](/en/servicios/desarrollo-de-protocolos-blockchain) [All blockchain services](/en/servicios)