rayls.com valid

Rayls

Rayls: Bringing Finance Onchain. The EVM Layer 1 network connecting institutions to blockchain liquidity, with built in privacy and compliance. Institutions run their own private Rayls Sovereign chains and connect them to the permissionless Rayls Public Chain, with optional privacy from Rayls Enygma.

For agents: Rayls: EVM Layer 1 blockchain connecting institutions to onchain finance, with private Sovereign chains, a public chain and Enygma privacy. Docs cover architect

evm layer 1institutional blockchainrwa tokenizationrls tokenprivacy compliance

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T20:39:39.865Z. Cached copy · Source on rayls.com

# Rayls

> Rayls: Bringing Finance Onchain. The EVM Layer 1 network connecting institutions to blockchain liquidity, with built in privacy and compliance. Institutions run their own private Rayls Sovereign chains and connect them to the permissionless Rayls Public Chain, with optional privacy from Rayls Enygma.

Key facts:
- Products: Rayls Public Chain (permissionless EVM Layer 1), Rayls Sovereign (private EVM chain per institution), Rayls Enygma (optional privacy), Rayls Private Network (connects Sovereign chains).
- Rayls Public Chain: 15,000+ transactions per second (Axyl consensus, Reth execution client), hard sub-second deterministic finality with no chain reorganisations, gas paid in USDr (pegged 1:1 to the US dollar, backed by USDC), chain ID 72957, mainnet launched 30 April 2026.
- 100% EVM-compatible: standard Solidity tooling (Foundry, Hardhat, Remix, viem, MetaMask) works unchanged.
- $RLS is the staking token of the Rayls ecosystem: validators stake RLS and receive half of each epoch's fees; fees are swapped to RLS once per epoch and the other half is bridged to Ethereum and burned.
- Rayls Enygma uses zero-knowledge proofs with a read-only Auditor View for regulators; research published on the IACR ePrint archive (2025/1638, 2025/1639).
- Users include Banco Central do Brasil (Drex CBDC pilot: 16 institutions, 6 of 14 use cases delivered on Rayls), Núclea (Núclea Chain, in production since June 2024), Nimofast Global (up to $100bn of energy and commodities assets), XP (USDXP stablecoin) and Kinexys by J.P. Morgan (Project EPIC: one of five implementations, meeting all 5 confidentiality requirements). Featured in the G20/BIS TechSprint 2024 report.
- Parfin is the core contributor and developer of Rayls.

The full site content is available as one Markdown file: [llms-full.txt](https://llms.rayls.com/llms-full.txt)


## Start here
- [Rayls home](https://llms.rayls.com/index.md): Overview of the network, its three products, use cases and customers
- [Products overview](https://llms.rayls.com/products.md): How the Public Chain, Sovereign, Enygma and Private Network fit together, with a provider comparison vs Canton, Besu, zkSync and Avalanche

## Products
- [Rayls Public Chain](https://llms.rayls.com/products/public-chain.md): Permissionless EVM Layer 1: 15,000+ TPS (Axyl), sub-second deterministic finality, USDr gas pegged 1:1 to USD, chain ID 72957
- [Rayls Sovereign](https://llms.rayls.com/products/sovereign.md): Private, institutional-grade EVM blockchain each institution runs on-prem, integrated with core banking and connected to public and private networks
- [Rayls Enygma Sovereign](https://llms.rayls.com/products/enygma-sovereign.md): Private, auditable settlement between banks' Sovereign chains using zero-knowledge proofs, with a read-only regulator view key; comparison vs Canton, ZKsync Prividium and Zama
- [Rayls Enygma](https://llms.rayls.com/products/enygma.md): Privacy framework combining zero-knowledge proofs and homomorph
…

Related sites

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=rayls.com · GET /v1/domain/rayls.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for rayls.com:
1. POST https://agentwebmap.com/v1/sites/rayls.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://rayls.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/rayls.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/rayls.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.