Building for Private Networks

Writing applications for the Rayls Private Networks is similar to writing them for any other EVM chain, although there are several important distinctions that the following subsections work through.

Alongside the technical reference in this guide, it is worth remembering that Private Networks are permissioned, so permission from a Private Network Operator is required before any smart contract can be deployed into a Private Network.

Rayls Private Network Components

A Rayls Private Network is comprised of protocols, chains, tools, and SDKs.

Component	Description
Rayls Sovereign	An EVM chain ledger held by the institution and integrated with a highly scalable enterprise database, together with a private relay tool that passes encrypted messages between a Rayls Node and a Private Network Hub
Private Network Hub	An EVM-compatible permissioned chain that orchestrates transfers between Rayls Nodes.
Rayls Custody	An HSM-based custody tool to securely generate, store and use cryptographic keys.
Rayls Protocol	A fully private transfer protocol and developer-friendly SDK that connects Rayls Nodes through the Private Network Hub.
Rayls Operator	A suite of developer-friendly governance tools for use within a Private Network.
Rayls Auditor	A suite of auditing tools to check and validate transactions within a Private Network.