Building for Private Subnets

Writing applications for the Rayls Subnets is similar to any other EVM chain, however there are several important distinctions that we will walk through in the following subsections.

In addition to the technical reference in this guide, keep in mind that since Subnets are permissioned, you will need to have permission from a Subnet operator before you can deploy any smart contract into a Subnet.

Rayls Private Subnet Components

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

Component	Description
Rayls Privacy Node	An EVM chain ledger in the Rayls Privacy Node integrated with a highly scalable enterprise database. and A private relay tool , part of the Rayls Node, that passes encrypted messages between a Rayls node and a Subnet Hub
Subnet Hub	An EVM-compatible permissioned chain that orchestrates transfers between Rayls Nodes.
Rayls Custody	A HSM-based custody tool to securely generate, store and utilize cryptographic keys.
Rayls Protocol	A fully-private transfer protocol and developer-friendly SDK to connect Rayls Nodes via the Private Subnet's Hub.
Rayls Governor	A suite of developer-friendly governance tools for use within a Private Subnet.
Rayls Auditor	A suite of auditing tools to check and validate transactions within a Private Subnet.