Monitoring cross-chain transactions

The Private Network operator monitors a Rayls Private Network from the Private Network Hub. Everything that moves between Rayls Sovereign chains (Privacy Nodes in the code) passes through the Hub, encrypted. The operator's governance services read it, decrypt it and keep a searchable record. Activity that stays inside one Rayls Sovereign chain never reaches the Hub, so the operator can't see it.

The monitoring services

The operator runs three services from rayls-sovereign-pnh-governance, which share a PostgreSQL database, and a web interface on top:

In the local stack started with ./rayls init --full, the API is at http://localhost:9100 and the Auditor Explorer at http://localhost:8181.

The services find the Hub contracts through the Hub's DeploymentProxyRegistryV1 (PNH_DEPLOYMENT_PROXY_REGISTRY). They decrypt with the operator's view secret key (PNH_RAYLS_VIEW_SECRET_KEY).

What the listener decrypts

Every participant's view private key is encrypted to the operator when the participant registers (see Adding new participants). The listener uses the operator's key to recover each participant's view key, then the shared secrets between participants. With those it decrypts:

• the batches of messages each chain sends through the Hub: arbitrary messages, including their payloads;
• Enygma transfers: sender, receiver, amount;
• the terms of delivery-versus-payment (DvP) swaps.

It reloads the keys whenever a participant registers or updates its keys on the Hub. For what this means for Enygma users, see Who sees what.

What gets recorded

Each cross-chain transaction is recorded with a protocol and a message type:

The message type is, for example, custom, enygma, dvp_erc721 or dvp_erc1155. Enygma mints and burns, which are public on the Hub, are recorded with the message type enygma.

The listener also records:

• token registrations, status changes, and mints and burns that issuers report to the Hub;
• token freezes and unfreezes;
• participant registrations and changes of status or role;
• the block headers each chain's private relayer submits to the Hub (Proofs contract).

Querying the governance API

Audit endpoints

For example, every Enygma transfer that chain 200002 sent after 1 October:

curl "http://<governance-api>/audit/transactions?sourceChainId=200002&messageType=enygma&initiatedAfter=2026-10-01"

{
  "data": [
    {
      "type": "ENYGMA",
      "id": "0x5b1e…",
      "idType": "batch_id",
      "createdAt": "2026-10-03 14:22:05 +0000 UTC",
      "sourceChainId": "200002",
      "sourceAddress": "0x…"
    }
  ],
  "total": 1,
  "limit": 10,
  "page": 1
}

The list gives each entry's id and idType. Use them to fetch the details: message_id with /audit/transactions/{messageId}, batch_id with the batch endpoints, shared_id with /audit/transactions/dvp/swap/{sharedId}, and transaction_id with /audit/transactions/dvp/{transactionId}.

Balance and status endpoints

These need a login. POST /private-network/login with {"username": "…", "password": "…"} sets an Authorization cookie valid for 30 days; POST /private-network/signup creates the account.

The net positions come from the Hub traffic only: the issuer's mints and burns, and the decrypted transfers between chains. They are not read from the Rayls Sovereign chains.

🚧

Restrict access to the API

The API doesn't authenticate the /audit endpoints or /flagged, and anyone who can reach it can create an account with /private-network/signup. Its data includes decrypted transfers. Expose it, and the Auditor Explorer, only on a network the operator controls.

What to watch

The services don't send alerts. Poll the API, or watch the flagger's logs, which record each flag as a warning.