Skip to main content

Rayls Public Chain Mainnet: The Privacy L1 Built for Banks Goes Live April 30

· 10 min read
Dora Noda
Dora Noda
Software Engineer

What if the chain you used cost exactly one dollar per transaction — every time, every block, regardless of whether ETH rallied 40% overnight or a memecoin pulled gas fees into the stratosphere? That question sounds mundane until you ask a bank CFO to sign off on deploying production settlement rails on top of a system where operating costs are set by the volatility of a third-party asset.

On April 30, 2026 at 3pm UTC, Rayls switches on its public chain mainnet — and the answer it offers to that question is the defining architectural choice of the launch. Rayls is a privacy-preserving Layer 1 built by Brazilian infrastructure company Parfin, backed by a Tether strategic investment, endorsed by the Central Bank of Brazil, and already running live workloads for Santander, Itaú, and JPMorgan's Kinexys division. It pays gas in USDr, its own USD-pegged native stablecoin. It burns half of all fee-derived RLS tokens. And it wraps every transaction in an encryption layer that combines zero-knowledge proofs, homomorphic encryption, and post-quantum cryptography — while preserving selective disclosure to authorized regulators.

This is not another general-purpose L1 chasing TVL. It is a surgical response to one specific question: what does a blockchain look like when the design brief is "a compliance officer at a tier-one bank will approve this"?

The Three Problems Rayls Was Built to Solve​

Most L1 launches in 2026 optimize for throughput, developer ergonomics, or fee compression. Rayls targets a different trio — a set of barriers that have kept regulated institutions out of permissionless chains despite six years of "institutional DeFi" marketing.

The volatility tax on gas. A corporate treasurer cannot forecast a $100M/year infrastructure line item if the underlying cost oscillates with a volatile native token. Holding ETH or SOL as "gas float" creates mark-to-market exposure that has to be hedged, reported, and justified to an audit committee. Circle's Arc chain addresses this by denominating gas in USDC. Tempo takes a similar path with fixed-fee payment lanes. Rayls goes further: USDr is chain-native, minted by the protocol, and burned as part of the fee cycle. Gas is literally priced in a unit of account the CFO already uses on the income statement.

The transparency problem. Public blockchains leak competitive information by design. When a bank's counterparties, transaction sizes, and liquidity positions are visible on a block explorer, trading desks get front-run, client relationships get exposed, and regulatory privacy obligations (GDPR, banking secrecy laws, MAS notices) can be violated by default. But fully private chains (classic Zcash-style) fail the opposite test — regulators cannot audit what they cannot see. Rayls Enygma threads this needle: encrypted transactions that remain verifiable, with an "auditor role" that can be assigned per-institution or per-regulator.

The counterparty-token exposure problem. On most L1s, paying gas means holding the native token, which means holding balance-sheet exposure to a speculative asset. For a bank settling tokenized deposits, the idea of the operational chain requiring them to custody RLS as a volatile counterparty is a non-starter. Rayls solves this in two layers: Privacy Node clients can pay fees in fiat, USDr, or RLS — the protocol handles conversion under the hood.

USDr: The Quiet Innovation​

The flashier elements of the Rayls architecture get most of the press — zero-knowledge proofs are photogenic, post-quantum cryptography makes headlines. But USDr may be the most consequential piece of the stack.

USDr is a USD-pegged stablecoin, native to the Rayls Public Chain, used as the canonical gas unit. When a user transacts, the fee is denominated in USDr. Behind the scenes, USDr is automatically converted into RLS through an on-chain DEX at specific trigger thresholds. Fifty percent of the resulting RLS is burned. The other fifty percent is routed to the Network Security Pool to reward validators.

This structure produces three effects simultaneously:

  1. Predictable fees for users. A transaction that costs $0.02 today costs $0.02 next quarter, regardless of RLS price action. Enterprise clients can budget infrastructure costs the way they budget cloud spend.
  2. Deflationary pressure on RLS. Every block of network activity permanently removes supply. With a fixed 10 billion total supply and no inflation, sustained usage compounds scarcity.
  3. Validator rewards in a stable reference unit. Validators earn RLS rewards funded by real transaction demand, not inflationary emissions that dilute existing holders.

During the early ramp-up phase — when fee generation may not yet cover validator payouts — the Rayls Foundation is supplementing rewards from its own treasury. This is unusual transparency: most chains quietly subsidize validators through inflation and hope nobody notices the dilution math.

Rayls Enygma: Privacy That Regulators Can Live With​

The privacy architecture is where Rayls gets genuinely interesting. Most "privacy chains" force a binary choice: full anonymity (which regulators reject) or full transparency (which institutions reject). Enygma refuses the binary.

Technically, Enygma combines:

  • Zero-knowledge proofs to validate transactions without revealing sender, recipient, or amount.
  • Fully homomorphic encryption (FHE) enabling computation on encrypted state.
  • Post-quantum authenticated key exchange for forward secrecy even against future quantum adversaries.
  • State root anchoring to Ethereum L1, providing censorship resistance and external verifiability for the chain's history without leaking transaction contents.

Crucially, Enygma supports a "God View" compliance model. Institutions, dApps, or operators can designate an auditor role — a regulator, an internal compliance team, or an external authority — with selective visibility into encrypted transaction data. A central bank overseeing a CBDC pilot can inspect flows without the entire network going public. A compliance officer can answer a subpoena without exposing client counterparties.

This is the architecture Brazil's Central Bank selected for the Drex CBDC pilot. It is the privacy layer JPMorgan's Project EPIC evaluated for fund tokenization. It is the design point that distinguishes Rayls from pure-transparency competitors like Base or Arbitrum and pure-anonymity competitors like Aztec or Railgun.

The Competitive Landscape​

Rayls is not launching into an empty field. The regulated confidential finance category has become the most contested zone in L1 design over the past eighteen months.

Canton Network is the incumbent. Built by Digital Asset and now processing over $4 trillion monthly in on-chain U.S. Treasury repo financing through Broadridge's DLR platform, Canton is the first mover and has landed Bank of America and Circle as live participants. Its architecture is permissioned-by-default with sub-net privacy, which maps cleanly onto how TradFi thinks about counterparty relationships.

Aztec Network is the ZK-purist alternative. As a privacy-preserving rollup on Ethereum, Aztec inherits Ethereum's security and developer ecosystem but sacrifices the gas-predictability and governance controls that matter to regulated players. Aztec is where crypto-native privacy builders go; Rayls is where banks go.

Circle's Arc launched in early 2026 with USDC-denominated gas and a quantum-resistant roadmap. Arc and Rayls overlap meaningfully — both bet on stablecoin gas, both target institutions, both plan post-quantum upgrades. The differentiator is the privacy primitive: Arc's near-term privacy roadmap targets balance confidentiality; Rayls ships native transaction-level privacy from day one.

Tempo Network takes a narrower stance — purpose-built for payments with fixed fees and sub-second finality — but lacks the privacy layer for confidential settlement.

What Rayls brings to this field is a specific combination no competitor has fully assembled: stablecoin gas + native transaction privacy + selective disclosure + EVM compatibility + an existing institutional client base already running live pilots.

Why the LatAm Origin Matters​

It is tempting to read Rayls as just another L1 and slot it into a ranked list. That misses the most important context: Rayls is not a crypto-native project that backed into institutional use cases. It is an institutional infrastructure company (Parfin) that built a chain because its existing bank clients needed one.

Parfin has been providing digital asset custody and tokenization infrastructure across Latin American banks for years. Santander and Itaú — two of the largest banks in Latin America by assets — were Parfin clients before RLS was a token. The Central Bank of Brazil selected Parfin for Drex because Parfin was already the operational backbone for Brazilian financial institutions experimenting with tokenized assets.

Latin America recorded nearly $1.5 trillion in crypto transaction volume in the past year, with institutional activity as a major driver. The GENIUS Act in the United States, MiCA in Europe, and Brazil's progressive stablecoin framework have created a regulatory convergence where compliant blockchain infrastructure is no longer a defensive necessity but a commercial opportunity. Tether's strategic investment in Parfin in late 2025 was a direct bet on exactly this thesis.

When Rayls launches on April 30, it does not have to bootstrap a user base. It has to activate an existing institutional pipeline that has been waiting for the public chain side of the two-chain architecture to go live.

What to Watch After Mainnet​

The first six months of Rayls public chain operation will test three specific hypotheses that have defined the institutional privacy category:

Does stablecoin gas actually reduce institutional friction? If Rayls sees measurable adoption from banks that have sat out transparent chains, the architectural thesis is validated. If institutions still hesitate, it suggests the barriers were always regulatory more than technical.

Does the deflationary model work at institutional transaction volumes? Bank settlement flows are larger but fewer than retail DeFi volumes. Whether the burn rate compounds meaningfully depends on whether fee-paying transaction volume materializes at the projected scale.

Does selective disclosure satisfy regulators? The Drex pilot is the proving ground. If Brazil's central bank is satisfied with Enygma's auditor model, that credential becomes exportable to every other central bank running CBDC pilots — and the list is long.

The broader question — whether regulated confidential finance captures the TradFi migration that transparent chains have partially addressed but not closed — is the largest single bet in L1 design right now. April 30 is when the most institutionally credentialed contender in that category starts accumulating on-chain evidence.

BlockEden.xyz provides enterprise-grade RPC and API infrastructure for builders deploying across EVM-compatible chains. As privacy-preserving L1s like Rayls and confidential finance stacks like Canton mature, developers need reliable, compliant node infrastructure to bridge the regulated and permissionless sides of the ecosystem. Explore our API marketplace to build on foundations designed to last.

Sources​

Share on Twitter