Who sees what: privacy and oversight

Enygma hides amounts, and who receives each payment, from the other members of a Rayls Private Network. It is designed for supervised networks, so one party can see every transfer: the Private Network operator, the network's supervisor. The operator is usually a central bank, another financial market infrastructure (FMI) provider such as a clearing house, or the parent of a banking group (see Governance). Its view has two limits:

  • It can read but can't spend. The operator holds each participant's view key, not its spend key, so it can't sign or move anyone's funds.
  • It sees only what crosses the Hub. Activity inside a member's own Rayls Sovereign chain, such as payments between two clients of the same institution, never reaches the Private Network Hub and stays outside the operator's view.

Some actions, such as minting, are visible on the Hub, the Hyperledger Besu chain at the centre of the network, to its validators and members. This page sets out what each party can see and do.

What each party can see

PartyCan seeCan't see
Hub validators and members of the network. The Hub is the network's own chain, not a public one.Which participants (up to six) were in each Enygma transaction; the commitments, nullifiers and encrypted messages; the token and the time; the amount and the participant of every mint and burnTransfer amounts, balances, which of the other participants received value, and the wallet that sent the funds
A participant in a transactionEverything above, plus its own decrypted message: what it received, or that it received nothingThe other participants' messages and balances
The receiving institutionThe transfer it received, as it mints the tokens on its own chainOther transfers it wasn't part of
The operator of a Rayls Sovereign chain (usually the institution itself)All client balances and payments on its own chain, which are ordinary ERC-20 records thereOther institutions' chains
The Private Network operator, the network's supervisorEvery Enygma transfer in the network, decrypted: sender, receiver and amount. See The operator's view.Spend keys: it can read transfers but can't sign them. Activity inside a member's own chain that never crosses the Hub.

The anonymity set and small networks

Each Enygma transaction names k participants, where k is the number of participants in the network, capped at six. Participants who aren't part of the payment receive a commitment to zero.

The anonymity set hides the receivers. The sender's wallet is masked too: on a chain where transactions pay gas, a relayer submits each transaction, so the wallet that sends the funds doesn't appear on the Hub. On a chain without gas, a transaction can be submitted from a fresh, single-use (ephemeral) wallet.

How much the anonymity set hides about the receivers depends on the size of the network:

Participants in the networkWhat the anonymity set hides
2Nothing between the two: each knows the other is its only possible counterparty. Amounts stay hidden.
3Limited. A participant that is in a transaction and receives nothing knows that the payment was between the other two.
4 to 6Every participant is in every transaction. A participant that receives nothing learns only that value may have moved between some of the others.
More than 6Each transaction includes six participants. Observers learn only that value may have moved between some of them.

Zero-value validation transactions, which the relayer sends to finalise each transfer, mean that a transaction doesn't always carry value. That weakens what an observer can infer from any single transaction.

The operator's view

When an institution registers in the network (see Adding new participants), its key service encrypts the institution's view private key to the Private Network operator, as part of the registration. Registration can't complete without this step. With those keys, the operator's governance services decrypt every Enygma transaction on the Hub (and every other message that crosses it: see Auditing), and the Private Network Auditor Explorer shows each transfer's addresses, chains and amounts.

In practice:

  • Audit access is network-wide. The operator, and anyone the network's rules allow to use its tools, such as a regulator, sees every transfer in the network.
  • There are no scoped view keys. You can't give an auditor a key limited to one account, one time window or one transaction.
  • A view key can't move funds. Spending needs the institution's separate spend key, which stays in its own key service. With view keys only, the operator can read but not spend.

Who can change what

ActionWhoWhereNotes
Freeze a token for a participantThe Private Network operator, or a compliance officer it appointsHub token registryA frozen participant can't send the token through Enygma or use it in DvP. See Freezing tokens.
Mint and burn supplyThe token's issuerIssuer's chain, then HubThe amount and the participant are public on the Hub.
Burn a holder's balance on a chainOwner of the token contract on that chainThat Rayls Sovereign chainburn(from, value) doesn't need the holder's approval.
Approve a token for the networkPrivate Network operatorHubSee Approving new tokens.
Approve contracts for program stepsAnyone can propose one; the Private Network operator approves or revokes itHub template registryStandard Rayls templates are pre-approved. Only approved contract code and functions can run on arrival.
Spend a participant's balanceOnly that participant, with its spend keyThrough its own relayerNeither the operator nor the issuer can spend it.

Designing for these properties

  • If participants must not learn each other's activity, plan for at least four participants in the network.
  • Treat the Private Network operator as able to see all Enygma activity, and choose the operator accordingly. See Governance and Private Network roles. In a central bank digital currency (CBDC) network, for example, that is usually the central bank.
  • Payments between clients of the same institution never reach the Hub. They are as private as that institution's own chain.

Did this page help you?