Overview

Connecting to Rayls Private Subnets enables private transactions between Privacy Ledgers. These decentralized, permissioned EVM networks allow financial institutions to securely manage digital assets, payments, and transactions.

Rayls Subnets provide privacy, scalability, interoperability, and decentralization, giving institutions full control over their data while enabling seamless value exchange. The architecture supports high transaction throughput and real-time settlement, meeting financial standards​​​.

For more details on Private Subnets, please refer to this page.

Pre-requisites

Here are the pre-requisites for a Privacy Ledger to be connected with a Private Subnet:

1. Deployment of Components: All components in your Privacy Ledger package must be fully deployed, and operational. Ensure that the necessary databases are set up with adequate resources.
2. Private Subnet Registration: Registering your Privacy Ledger with a Private Subnet is a simple straight forward process of information exchange and coordination with the Subnet Operator to ensure that your Privacy Ledger is recognized and allowed to participate in the network.
3. Testing and Validation: Once connected, it’s important to validate the setup by conducting test transactions to ensure that everything is functioning as expected.

Private Subnet Onboarding Process:

The process of connecting a Privacy Ledger to a Private Subnet is an off-chain process managed by the Subnet Operator of each subnet. This ensures that each Subnet Operator institution can customize their onboarding and connecting workflows according to their specific needs and regulatory requirements.

Connecting a Privacy Ledger to a Private Subnet is establishing a communication channel between the Relayer component of the Privacy Ledger and the Commit Chain of the Private Subnet. This channel enables secure and private cross-chain transactions.

Read more details about creating a cross-chain transaction in the Sending A Teleport page.

Key Components:

• Privacy Ledgers: Private permissioned EVM blockchains that support high transaction volumes with full privacy and compliance.
• Relayers: Enables the cross-chain communication and transaction processing of a Privacy Ledger in a Private Subent.
• Commit Chain: An EVM-compatible blockchain that orchestrates and validates transactions between participant Privacy Ledgers of a Private Subnet.

Step-by-Step

1. Off-chain Coordination between Privacy Ledger and Private Subnet: Coordinate off-chain with Private Subnet Operator about connecting your Privacy Ledger. Information such as Privacy Ledger chainID and Private Subnet commit chain details will be exchanged.
2. Registration and Approval by Subnet Operator: Once information exchange is completed, the Subnet Operator goes through its registration and approval.
3. Establishing connection with Private Subnet: Once your Privacy Ledger is approved by the Subnet Operator, is time to initiate the communication channel with the Private Subnet by deploying the Relayer component.
4. Testing connection: Once the Relayer component is operational, it’s time for testing it. It is recommend exchanging Arbitrary Messages with subnet participants to ensure connection. Use the block explorer to visualize and confirm the cross chain messages sent/received.

Additional Resources

• Read more about private subnets in the Private Subnet Basics docs.
• Contact support if assistance is needed.