Why a Rayls Private Network?
A Rayls Private Network is multiple Rayls Sovereign chains connected together via a central Hyperledger Besu chain, the Private Network Hub.
It is a permissioned network for institutions that need to exchange tokenised value with each other privately, under rules that one accountable operator sets and enforces.
Who it's for
- Financial market infrastructure (FMI) providers, such as central banks, clearing houses and exchanges, that want to run a wholesale network for their members.
- Central banks exploring a wholesale central bank digital currency (CBDC). See CBDCs on Rayls Private Networks.
- Banking groups that want separate chains for subsidiaries, business lines or jurisdictions, with controlled flows between them.
- Groups of institutions that settle tokenised assets against tokenised cash between approved counterparties.
What makes it different
- Each institution has its own chain. Every participant runs its own Rayls Sovereign chain (Privacy Node in the code), a full EVM (Ethereum Virtual Machine) chain. Its client accounts, internal payments and contracts stay there, separate from every other member's.
- A shared Hub that holds the rules. The Private Network Hub records who the participants are, which tokens may move and which contracts transfers may call, and copies those rules to every chain.
- Private payments between institutions. With Rayls Enygma, amounts and receivers are hidden from the other members, and the Hub checks each payment with a zero-knowledge proof.
- Private DvP. Enygma tokens can be exchanged for tokenised assets in one settlement on the Hub. See DvP on Rayls Private Networks.
- Oversight built in. The operator can decrypt all cross-chain traffic and flag anomalies as they happen. See Auditing.
- Standard tooling. All the chains are EVM chains, so Solidity contracts and existing Ethereum tools work.
What the operator does
The Private Network operator:
- runs the Private Network Hub, the governance services and the Auditor Explorer;
- admits institutions, sets their roles and authorises their relayers;
- approves the tokens that may move between chains, and the contract templates that transfers may call;
- freezes participants, or a token for chosen participants;
- reads and monitors all cross-chain activity.
See Governance and Private Network roles.
Before you decide
- The operator sees everything that crosses the Hub. Each participant's view key is encrypted to the operator when it joins. Choose an operator that all participants accept in that position. See Who sees what.
- Senders are visible. The Hub shows which participant sent each transaction. Enygma hides receivers among up to six participants, so a network with fewer than four participants hides less. See The anonymity set and small networks.
- You design the Hub's deployment. The code doesn't fix the Hub's consensus or how many nodes run it. See Private Network design options.
Next steps
Updated 1 day ago
Did this page help you?