Rayls

• Name: Rayls
• URL: https://www.rayls.com/
• Category: banking blockchain infrastructure / permissioned EVM / tokenized-finance interoperability stack / CBDC and RWA infrastructure
• Summary: Rayls is an institutional blockchain stack designed to connect private bank-operated ledgers with a public EVM chain. Its primary materials frame the system less like a single protocol token play and more like a regulated tokenized-finance control plane: a Rayls Public Chain for open composability, Rayls Privacy Nodes for institution-run private ledgers, and a Private Network / protocol layer for confidential inter-institution transfers, messaging, and delivery-versus-payment workflows. That makes it most useful to catalog as banking and tokenized-finance infrastructure rather than as a generic L1.
• What it does:
  • Operates the Rayls Public Chain, a permissionless EVM chain intended to connect banks, fintechs, RWAs, and DeFi liquidity
  • Lets financial institutions run Rayls Privacy Nodes: private EVM-based ledgers for token issuance, internal operations, governance controls, and confidential transfers
  • Connects privacy nodes through a Private Network Hub, relayer, endpoint contracts, and SDK tooling for cross-chain messaging and asset movement
  • Supports tokenized-deposit, CBDC, cross-border-payment, DvP, and tokenized-asset workflows where institutions need privacy plus interoperability
  • Publishes fairly operational docs covering protocol design, node roles, infrastructure sizing, monitoring, disaster recovery, and privacy-node deployment
• Key claims:
  • The homepage says Rayls is building “the blockchain for banks” and is designed to bring “$100 trillion liquidity and 6 billion bank customers onchain” through a scalable private-and-public blockchain system
  • The docs describe Rayls as a combined architecture of Rayls Public Chain plus Rayls Privacy Nodes that can connect into a Rayls Private Network, with explicit goals around privacy, scalability, interoperability, governance, and auditability
  • Rayls says its Privacy Node is a scalable single-node EVM ledger integrated with MongoDB and based on a modified Geth execution client, which is a useful clue that the operational architecture is more specific than the homepage alone suggests
  • The protocol docs emphasize confidential inter-institution token and message transfer, endpoint contracts, relayers, and a Private Network Hub rather than only generic chain marketing
  • Rayls also highlights publicly shared academic work, including an IEEE Security & Privacy poster on a CBDC design using its Enygma technology, suggesting a research-heavy posture even though no single canonical protocol whitepaper is obvious from the current public surface
• Whitepaper: No single canonical standalone protocol whitepaper or litepaper was found in the current public materials reviewed during this pass. The strongest primary sources were the official site, docs index, llms.txt, architecture / protocol pages, privacy-node docs, and Rayls’ published academic-material pages; see ../whitepapers/rayls-primary-sources-2026-04-27.md.
• Sources:
  • https://www.rayls.com/
  • https://docs.rayls.com/
  • https://docs.rayls.com/llms.txt
  • https://docs.rayls.com/docs/a-warm-introduction-to-rayls
  • https://docs.rayls.com/docs/rayls-protocol
  • https://docs.rayls.com/docs/a-warm-introduction-rayls-privacy-node
  • https://docs.rayls.com/docs/rayls-infrastructure
  • https://docs.rayls.com/docs/published-academic-material
  • https://docs.rayls.com/docs/cbdc-poster

Internal linkages

• Company boundary: parfin is the developer and institution-facing operating shell around Rayls.

• Keep the split explicit: Rayls is the public/private-chain product surface; Parfin is the custody, CaaS, implementation, and bank-relationship layer that packages it.

• Last reviewed: 2026-08-06 UTC