ESEspañol

Enterprise blockchain network · Hyperledger Fabric · Ethereum · Polygon

A galaxy of networks.

HyperGalax combines the best of both worlds: a private core on Hyperledger Fabric —the enterprise blockchain technology backed by IBM— where your data is seen only by those you choose, connected to Ethereum, Polygon and other public networks so anyone can verify what matters.

Design your networkStart the journey
  • 3.000transactions per second on average
  • FabricHyperledger core, with IBM as technology partner
  • 3 en 1private, public and hybrid in a single infrastructure

Before we begin

There is no single blockchain.

Bitcoin, Ethereum, a banking network or a hospital’s records all use the same idea —a shared ledger nobody can rewrite— but with very different rules about who joins, who writes and who validates. Choosing those rules well is the difference between a project that scales and one that never leaves the pilot. Come with us: we’re going to open a blockchain from the inside.

What a blockchain is

Four pieces, one network.

  1. 01

    The block

    A sealed bundle of transactions

    Each block bundles operations —a payment, a change of owner, a sensor reading— with a timestamp and a unique fingerprint (hash). If anyone changes a single comma, the fingerprint changes completely and everyone notices.

  2. 02

    The chain

    Each block points to the one before

    Each new block includes the fingerprint of the previous one. That forms a chain: to forge an old record you would have to redo every later block and also convince the rest of the network. In practice, it’s immutable.

  3. 03

    The network

    Thousands of identical copies

    The chain doesn’t live on a single server: every node on the network keeps a full copy and syncs it with the others. There is no single point of failure and no administrator who can quietly erase the history.

  4. 04

    Consensus

    They agree without intermediaries

    Before adding a block, nodes run a consensus protocol: proof of work (Bitcoin), proof of stake (Ethereum) or Byzantine fault tolerance and Raft in enterprise networks. The rules on who votes define what kind of network it is.

Network types

Public, private or hybrid.

Every blockchain shares the same underlying technology. What sets them apart are three questions: who can read the data?, who can write? and who validates the blocks? Depending on the answers, we get three families of networks with very different strengths, limits and uses.

  1. 01PublicPublic network · permissionless
  2. 02PrivatePrivate network · permissioned
  3. 03HybridHybrid network · private + public

01 / 03 · Public network · permissionless

Public

Open to the whole planet.

On a public blockchain anyone can download the chain, send transactions and, if they follow the protocol rules, take part in validation. There is no owner: the network belongs to those who use it.

Its security doesn’t rely on trusting anyone but on economics: attacking the network would mean controlling most of the computing power (proof of work) or the capital locked in staking (proof of stake), something extremely expensive on large networks. That’s why they’re ideal when strangers need to trust a record.

The price of that openness is total transparency: every transaction is visible to everyone, forever. Addresses are pseudonymous, not anonymous, and every transaction pays a fee (gas) that rises when the network is congested.

Who takes part

  • ReadAnyoneAnyone, with a block explorer
  • WriteAnyoneAnyone with a wallet and funds for gas
  • ValidateAnyoneAnyone who contributes computing power or staked capital

How it works

Consensus
Proof of work (mining) or proof of stake (staking)
Identity
Pseudonymous addresses derived from a private key
Cost
Per‑transaction fee in the network’s native coin
Governance
Open community of developers, validators and users

Strengths

  • Maximum decentralisation and censorship resistance
  • Verifiable by anyone, without asking permission
  • Global liquidity: exchanges, DeFi, wallets and stablecoins
  • No infrastructure of your own to maintain

Limits

  • All data is public forever
  • Variable, unpredictable fees
  • Limited throughput on the base layer
  • Complex fit with GDPR and confidentiality

Real examples

  • 2009Digital money

    Bitcoin

    The first blockchain. Thousands of miners compete to solve a mathematical puzzle every ten minutes; the winner adds the block. Deliberately slow, but the most secure and battle‑tested network in the world.

    Consensus
    Proof of work
    Block
    ≈ 10 min
    Throughput
    ≈ 7 TPS

  • 2015World computer

    Ethereum

    It introduced smart contracts: programs that run on the chain. Since September 2022 it runs on proof of stake, which cut its energy use by around 99.9%. It underpins most of DeFi, stablecoins and tokens.

    Consensus
    Proof of stake
    Block
    12 s
    Finality
    ≈ 13 min

  • 2020EVM‑compatible network

    Polygon PoS

    Compatible with Ethereum —same contracts, same wallets— but with blocks every few seconds and fees of a cent or less. Widely used by brands for NFTs, loyalty and payments.

    Consensus
    Proof of stake
    Block
    ≈ 2 s
    Cost
    A cent or less

  • 2020High performance

    Solana

    Bets on speed in a single layer: it combines proof of stake with a cryptographic clock (Proof of History) to order transactions in slots of around 400 ms.

    Consensus
    PoS + PoH
    Slot
    ≈ 400 ms
    Throughput
    Thousands of TPS
Use it when

You need anyone to be able to verify or use your assets without asking you: tokens traded on open markets, public certificates, global payments or decentralised applications.

02 / 03 · Private network · permissioned

Private

Only those with a key get in.

A private or permissioned blockchain keeps immutability and traceability, but every participant is identified and authorised. It is governed by a company or a consortium that decides who reads, who writes and who validates.

Because validators are known, there’s no need for mining or staking: fault‑tolerant (Raft) or Byzantine‑fault‑tolerant (BFT) protocols reach agreement in milliseconds, with immediate finality —a confirmed block is never reverted— and no per‑transaction fees.

When the network is shared by several companies that compete with each other —banks, insurers, shipping lines— it’s called a consortium network. Each one runs its own nodes and nobody controls the shared ledger alone, yet sensitive data stays out of public reach.

Who takes part

  • ReadAuthorised onlyOnly permitted members, even per channel or field
  • WriteAuthorised onlyUsers and applications with a digital certificate
  • ValidateLimited groupNodes appointed by the company or consortium

How it works

Consensus
Raft, BFT, IBFT 2.0 / QBFT or notaries
Identity
X.509 certificates issued by a network authority
Cost
No gas: only node infrastructure
Governance
Policies agreed by members and enforced in code

Strengths

  • Real confidentiality and GDPR fit
  • Thousands of transactions per second, immediate finality
  • Predictable costs, no per‑transaction fees
  • Identity and legal accountability of every participant

Limits

  • Less decentralised: you have to trust the members
  • Third parties can’t verify it on their own
  • No direct access to open‑market liquidity
  • Requires running and governing the infrastructure

Real examples

  • 2017Enterprise framework

    Hyperledger Fabric

    It was born from code contributed by IBM and is now a Linux Foundation project. Its modular architecture separates contract execution from block ordering, and supports channels and private data collections. It is the core of HyperGalax.

    Consensus
    Raft · BFT
    Contracts
    Go · Node.js · Java
    Finality
    Immediate

  • 2018Food supply chain

    IBM Food Trust

    A Hyperledger Fabric network for food traceability. In a widely cited test, Walmart cut the time to trace the origin of a batch of mangoes from about seven days to 2.2 seconds.

    Built on
    Hyperledger Fabric
    Before
    ≈ 7 days
    After
    2,2 s

  • 2016Regulated finance

    R3 Corda

    Designed by a banking consortium: transactions are shared only between the parties involved and a notary prevents double spending. SDX, the Swiss SIX Group’s digital asset exchange, runs on it, for example.

    Consensus
    Notaries
    Data
    Only between parties
    Sector
    Banking and markets

  • 2017Spanish consortium

    Alastria

    A consortium of Spanish companies, universities and institutions that runs Ethereum‑compatible permissioned networks (Quorum and Hyperledger Besu) and promotes self‑sovereign digital identity.

    Technology
    Quorum · Besu
    Consensus
    IBFT · QBFT
    Type
    Consortium
Use it when

You handle confidential data —customers, health, contracts, prices— and need to share it with partners with high throughput, predictable costs and regulatory compliance.

03 / 03 · Hybrid network · private + public

Hybrid

What’s private stays inside. The proof goes out.

A hybrid network combines a private environment, where sensitive data is processed, with one or more public networks, where whatever must be verifiable by all or circulate freely is published. It is the HyperGalax model.

The key mechanism is anchoring: every so many blocks, the private network computes a single fingerprint (Merkle root) that summarises thousands of operations and writes it to Ethereum or Polygon. The data never leaves, yet anyone can check it hasn’t been altered. A single public transaction protects millions of private records.

The other bridge runs the other way: an asset recorded on the private network —an invoice, a bond, a batch of goods— can be represented as a token on a public network to be sold, pledged or used in DeFi, while the regulated information stays protected inside.

Who takes part

  • ReadLimited groupData: authorised only · Proofs: anyone
  • WriteLimited groupIdentified members; public tokens, anyone
  • ValidateAnyonePrivate nodes + the anchoring public network

How it works

Core
Permissioned network (Hyperledger Fabric in HyperGalax)
Anchoring
Merkle roots published on Ethereum or Polygon
Bridge
Minting and burning of tokens on public networks
Oracles
Signed external data feeding the contracts

Strengths

  • Confidentiality and throughput of a private network
  • Public, independent verification of integrity
  • Access to liquidity, wallets and open markets
  • Minimal public cost: one anchor protects thousands of operations

Limits

  • More complex architecture to design
  • Bridges require extreme auditing and security
  • You must decide carefully what is published and what isn’t

Real examples

  • SedeFabric + Ethereum / Polygon

    HyperGalax

    Our private core on Hyperledger Fabric processes an average of 3,000 transactions per second and periodically anchors its proofs on public networks, from which it can also issue tokens.

    Core
    Hyperledger Fabric
    Anchoring
    Ethereum · Polygon
    Average
    3.000 TPS

  • 2022Banking + DeFi

    Project Guardian

    An initiative of the Monetary Authority of Singapore. In its first pilot, JP Morgan, DBS and SBI executed trades in tokenized currencies and bonds on a permissioned DeFi protocol deployed on the public Polygon network: verified identity in an open world.

    Led by
    MAS
    Public network
    Polygon
    Model
    Permissioned DeFi

  • 2018European infrastructure

    EBSI

    The European Blockchain Services Infrastructure, run by the European Commission and Member States. Only authorised public nodes write, but anyone can verify diplomas or credentials: a “public permissioned” model.

    Writes
    Authorised nodes
    Verifies
    Anyone
    Use
    Credentials

  • 2019Trade finance

    XDC Network

    It defines itself as a hybrid blockchain for trade finance: it combines an Ethereum‑compatible public network with private subnets for each deal’s documents.

    Consensus
    XDPoS
    Compatibility
    EVM
    Sector
    Trade finance
Use it when

You need enterprise privacy and throughput, but also want regulators, customers or investors to verify integrity on their own, or your assets to reach open markets.

Comparison

Seven networks, side by side.

Figures are indicative: they depend on configuration, load and each protocol upgrade. What matters is the order of magnitude and, above all, who controls each piece.

NetworkTypeWho validatesConsensusBlockThroughputFinalityPrivacyCost per operation
BitcoinPublicAny minerProof of work≈ 10 min≈ 7 TPSProbabilistic (≈ 1 h)Transparent, pseudonymousVariable, market‑driven
EthereumPublicValidators with 32 ETHProof of stake12 sTens of TPS (L1)≈ 13 minTransparent, pseudonymousVariable (gas)
Polygon PoSPublicValidators staking POLProof of stake≈ 2 sHundreds of TPSSecondsTransparent, pseudonymousA cent or less
Hyperledger FabricPrivate / consortiumAuthorised organisationsRaft · BFTConfigurableThousands of TPSImmediateChannels and private dataNo gas
R3 CordaPrivateAppointed notariesNotary (Raft / BFT)No blocksHundreds to thousandsImmediateOnly the parties involvedNo gas
Permissioned BesuConsortiumAuthorised validatorsQBFT · IBFT 2.0ConfigurableHundreds of TPSImmediatePer‑node and per‑account permissionsOptional gas
HyperGalaxHybridAuthorised members + anchoring public networkRaft · BFT + anchoring on Ethereum / PolygonConfigurable3,000 TPS on averageImmediate + public proofData inside, only fingerprints leaveNo gas inside; batched anchoring

PublicPrivateHybrid

Inside HyperGalax

The architecture, layer by layer.

  1. 01

    Identity

    Every node, user and app has a name

    Each organisation on the network has its own certificate authority (Fabric CA) and membership service provider (MSP). Nothing runs without a valid X.509 certificate, and Idemix anonymous credentials let you prove an attribute —being of age, being a customer— without revealing who you are.

  2. 02

    Channels

    Networks within the network

    Channels are subnetworks with their own ledger: one customer’s suppliers can’t see another’s. Within a channel, private data collections keep sensitive information only on authorised nodes and leave just its fingerprint on the chain. That’s how GDPR is met without giving up traceability.

  3. 03

    Ordering

    Execute, order, validate

    Fabric flips the classic order: first nodes simulate the transaction in parallel, then the ordering service places it in a block —with Raft, crash‑tolerant, or BFT, tolerant to malicious nodes— and finally every node validates it. The result: high throughput and immediate finality, with no forks.

  4. 04

    Chaincode

    Contracts with signing policies

    Smart contracts (chaincode) are written in Go, Node.js or Java, languages your team already knows. Each contract has an endorsement policy: for instance, a transaction is only valid if two of the three organisations involved sign it. Business logic becomes rules nobody can skip.

  5. 05

    Public anchoring

    The galaxy connects to the universe

    The HyperGalax bridge batches blocks, computes their Merkle root and publishes it on Ethereum or Polygon. From then on, anyone can check your network’s integrity without seeing a single record. The same bridge mints tokens on public networks when an asset needs to circulate outside.

HyperGalax is a permissioned network on Hyperledger Fabric, the technology IBM championed and contributed to the Linux Foundation, with IBM as Sede Blockchain’s technology partner. Travel through its five layers.

Public networks we work with

One private core, many public orbits.

HyperGalax doesn’t lock you into one network. Its private core orbits alongside the main public networks, and for each project we choose the one that best balances security, cost and reach.

  1. 01Maximum security

    Ethereum

    The public network securing the most value and the token standard. We use it for high‑value anchoring, security tokens (ERC‑3643) and assets meant for institutional investors.

    • Anchoring
    • ERC‑20
    • ERC‑3643
    • ERC‑721

  2. 02Low cost, high frequency

    Polygon

    Ethereum‑compatible with minimal fees. Ideal for frequent anchoring, certificates, product NFTs, loyalty and small payments.

    • Frequent anchoring
    • ERC‑1155
    • Certificates
    • Payments

  3. 03Wherever your users are

    EVM networks

    Any network compatible with the Ethereum Virtual Machine —Arbitrum, Optimism, Base, Avalanche C‑Chain or BNB Chain— with the same contracts and tools, depending on where your market is.

    • Arbitrum
    • Optimism
    • Base
    • Avalanche

  4. 04Risk‑free

    Test networks

    Every integration is first validated on test networks such as Sepolia or Amoy, with dummy data and zero cost, so going live holds no surprises.

    • Sepolia
    • Amoy
    • Audit
    • CI/CD

30‑second diagnosis

Which network does your project need?

Answer four questions and the galaxy reconfigures into the recommended architecture. Then send us the result and we’ll study it with you.

01 Is your data confidential?

Customer, health, contract or pricing data, trade secrets…

02 Who should validate transactions?

Who runs the nodes that confirm each block.

03 Must third parties verify without asking you?

Regulators, end customers, auditors, investors or the public.

04 Must your assets circulate on open markets?

Wallets, exchanges, DeFi or sale to investors worldwide.

Answer all four questions to see the recommendation. 0 / 4

General guidance. The final architecture is decided after analysing your case, your systems and your sector regulations.

For every sector

Where each network shines.

Banking, insurance, health, logistics, energy or public administration: each sector strikes a different balance between privacy and transparency. Here’s how we solve it.

  1. 01

    Banking and finance

    Inter‑bank settlement on a private network, tokenized bonds and deposits on public networks, and compliance records the supervisor can verify.

    Network · Hybrid
  2. 02

    Supply chain

    Traceability of every batch from origin, with channels per supplier so nobody sees a competitor’s prices.

    Network · Private
  3. 03

    Health

    Medical records and consents visible only to authorised professionals, with a tamper‑proof log of every access.

    Network · Private
  4. 04

    Insurance

    Parametric policies that pay out automatically when an oracle confirms the event, and assessments shared between insurers and reinsurers.

    Network · Hybrid
  5. 05

    Public administration

    Tenders, registries and degrees with protected data and public seals any citizen can verify.

    Network · Hybrid
  6. 06

    Energy

    Renewable origin certificates and peer‑to‑peer energy trading, with public traceability of every green kilowatt.

    Network · Hybrid
  7. 07

    Human resources

    Instantly verifiable credentials, training and contracts, without exposing employees’ personal data.

    Network · Private
  8. 08

    Entertainment and brands

    Tickets, collectibles and loyalty programmes on low‑cost public networks to reach millions of users.

    Network · Public

Technology

Engineered by Sede Blockchain.

HyperGalax is a product of Sede Blockchain, the Barcelona company that has worked with smart contracts since 2015 and has IBM as its technology partner. We design, deploy and run the entire network, or hand it over for you to operate.

01Core
Hyperledger Fabric with Raft or BFT ordering
02Contracts
Chaincode in Go, Node.js or Java; Solidity on public networks
03Deployment
Kubernetes on your cloud, ours or your own servers
04Keys
HSM and IBM Hyper Protect technology for custody
05Integration
REST and gRPC APIs, events and ERP connectors
06Bridge
Merkle anchoring and token minting on EVM networks
07Observability
Private block explorer, metrics and alerts

FAQ

What people ask us.

What’s the difference between a public and a private blockchain?

On a public one anyone can read, write and validate, and security is guaranteed by the protocol’s economics. On a private one only identified, authorised members take part and decide who sees each record. Public maximises openness; private maximises confidentiality and throughput.

Is a private blockchain still a blockchain?

Yes. It keeps blocks chained by cryptographic fingerprints, copies distributed across several nodes and a consensus protocol. What changes is who can take part. A recorded entry can’t be altered without the other members detecting it.

What exactly is a hybrid network?

A network that processes data in a private environment and uses a public network for whatever must be verifiable or tradable: it publishes fingerprints (anchoring) or mints tokens. You get the privacy and speed of private with the trust and reach of public.

What role does IBM play in HyperGalax?

IBM is Sede Blockchain’s technology partner. The HyperGalax core is Hyperledger Fabric, the enterprise blockchain framework IBM championed and contributed as open source to the Linux Foundation, and we use IBM Hyper Protect technology for key custody. HyperGalax is a Sede Blockchain product.

Does my data end up on Ethereum or Polygon?

No. Anchoring only sends out a cryptographic fingerprint summarising thousands of operations. The data can’t be reconstructed from it, but it proves nothing has been modified. Information is only published openly if you decide to mint a public token.

How does a blockchain fit with GDPR?

In HyperGalax personal data is kept in private collections outside the shared ledger, with only its fingerprint on the chain. If a data subject exercises their right to erasure, the data is deleted and the fingerprint no longer points to anything, without breaking the chain.

How much does each transaction cost?

There is no gas inside the private network: the cost is node infrastructure, fixed and predictable. On public networks you only pay for anchors, which are batched so a single transaction protects thousands of operations, plus token minting if you need it.

Can I start private and open up later?

Yes, it’s the most common path. HyperGalax starts private and public anchoring or the token bridge are switched on when the project needs them, without migrating data or changing existing contracts.

Who runs the nodes?

You choose: we run them as a managed service, you deploy them on your own cloud or servers, or each consortium member runs its own. The network works the same in every case.

How long does it take to launch a network?

A working proof of concept is usually ready in a few weeks. A production network with integrations, channels and anchoring depends on the number of organisations and systems, and we plan it with you from day one.

Let’s start

Let’s design your network.

Tell us what you want to connect and who should take part. We’ll reply within 48 business hours with a first architecture proposal: network type, organisations, public networks and next steps.

  • Free first architecture proposal
  • Confidential from the first message
  • Tech and legal team in a single point of contact