Private payments. Safe and compliant.

Rayls Enygma is a privacy protocol for EVM chains. It hides who paid whom and how much, while an auditor can still read every payment. It comes in two editions: Enygma Sovereign, in production between banks, and Enygma Public, whose testnet pilot runs on the Rayls Public Chain Testnet. Enygma Sovereign connects banks’ own Rayls Sovereign chains: each transfer hides its receiver among up to six banks, and the network operator, usually the central bank, can read every transfer. Enygma Public is for anyone on a public chain: payments sit in one shared shielded pool, and a relayer submits each one, so the sender’s address isn’t in the transaction.

In Enygma Public, the public sees that a payment happened, but not who paid whom or how much. Your username and address are public in the registry, and moving tokens into or out of the shielded pool is public. The person you pay sees what they received. The auditor sees everything, including invites; on this testnet, that is the Rayls Foundation. It can read payments, but it can’t freeze or move funds. In Enygma Sovereign, other banks and the public can’t see amounts or which bank was paid, and the network operator, usually the central bank, can read every transfer.

Enygma Public is quantum-private: payment data is encrypted with AES-256-GCM under keys agreed through ML-KEM, NIST’s post-quantum standard, so recorded history stays private even from a future quantum computer. Its zero-knowledge proofs and transaction signatures aren’t post-quantum, so it isn’t quantum-secure. Enygma Sovereign also uses ML-KEM, for the view keys that let the network operator read transfers.

From their public documentation, Tornado Cash moves fixed amounts and only breaks the link between a deposit and a withdrawal. Railgun hides payments inside its pool, but, as far as we can tell, an auditor only sees them if you share a viewing key. Enygma Public gives an auditor access by design, encrypts payments with post-quantum ML-KEM, and pays gas in shielded $RLS, so an invited account never needs public funding.

Yes, you can bring an existing EVM wallet such as MetaMask. But its address has a public history, so you risk linking your public profile to your shielded activity. A passkey starts you on a new address with no history, needs no seed phrase, and only works on the Enygma site.

Your spending key never leaves your device, and the wallet makes each proof in your browser. A relayer submits the finished transaction. The amount and recipient in it are encrypted, so the relayer can’t read them. Like any website, it sees your IP address. The wallet counts page views with Google Analytics, page names only, and you can turn that off in How it works. That’s the Enygma Public wallet. In Enygma Sovereign, each bank’s keys stay in its own key service, and it sends through its own relayer.

Your Enygma Public keys come from your passkey. A passkey synced through iCloud Keychain, Google Password Manager or a password manager comes back on a new device. If you lose one that isn’t synced, you lose access to that account and its shielded balance, and nobody can recover it. Enygma Sovereign doesn’t use passkeys: each bank’s keys stay in its own key service.

Enygma Public isn’t: its pilot runs on the Rayls Public Chain Testnet, with test tokens only. Enygma Sovereign already runs in production with banks, on their own Rayls Sovereign chains.