rayls

我从预承诺阶段就开始质押 RLS,平时读官方博客,多半是想知道自己的仓位会不会受影响。8 月 30 日这篇讲量子的文章不一样,它通篇在教机构怎么做采购,跟我这种散户没什么直接关系。但我还是读完了,因为它开头立了一条挺硬的规矩,而这条规矩后来把我带回到文章自己身上。
那条规矩是这样的:一个”量子安全”的说法,如果不写清楚具体用了哪个标准化算法、在哪个参数级别,那它就不是一个主张,只是一个标签。
这句话我很认同。于是我做了一件文章本身鼓励做的事,把这条尺子转过来量它自己。
公告没写自己用的是哪一档
这篇文章的后半段给机构列了六个该问供应商的问题。第三个是:
系统在哪里用了 NIST 标准化的后量子算法,具体是哪些标准,在哪个参数级别?文章特意补了一句,ML-KEM 的 512 参数级别和 ML-KEM-1024 不是一回事。
而在前半段拆解 Enygma 支付流程的时候,第二个组件写的是:早期设计用 CSIDH 做审计方密钥交换,现在已替换为 ML-KEM。
到这里就没有下文了。参数级别没写。
我把这一处单独拎出来,不是要挑刺。恰恰相反,正因为这篇文章自己把参数级别列成了关键问题,并且举的例子就是 ML-KEM,这个空缺才值得一提。它显然知道这个区分重要,只是讲到自己时没有展开。
参数级别为什么不是细节
我去查了这个参数级别在现实里对应什么。
美国国安局的 CNSA 2.0 套件,明确指定 ML-KEM-1024 和 ML-DSA-87,取的是最强参数档。从 2027 年 1 月 1 日起,所有面向美国国家安全系统的新采购都必须支持 CNSA 2.0 算法,除非在采购文件里写明例外。
换句话说,一套用了 ML-KEM 但停在 512 或 768 档的系统,在那道闸门前和完全没用后量子算法的系统落在同一边。这不是安全强度上的细微差别,是能不能进采购流程的差别。
CNSA 2.0 后面还排着别的时间点。网络设备要在 2030 年前做到独占使用,再往后大部分设备的迁移目标定在 2033 年,最终的全面量子抗性对齐的是 NSM-10 那个 2035 年的目标。不过对供应商来说,真正先咬下来的是 2027 年那道,因为它卡的是采购环节,不是运行环节。
这篇文章的标题写的是”2027 年之前”,所以它显然知道这个时间点。它也在正文里准确写出了 CNSA 2.0 指定 ML-KEM-1024。它唯一没写的,是自己在哪一档。
五个已抗量子,再拆一层
文章的结论是七个组件里五个已经抗量子。这个说法本身没错,但它把两类性质不同的东西合并了。
看它自己给每个组件标的状态。组件一身份构造和组件二密钥交换,标的是 addressed,也就是”已处理”。这两处是 Rayls 主动改的:身份构造原本基于 Baby Jubjub 椭圆曲线,在 Enygma v2.5 之后换成了抗量子设计;密钥交换原本用 CSIDH,换成了 ML-KEM。
组件三、四、五标的是 no action required,“无需处理”。交易载荷的加密走的是 AES-GCM,其中 AES-256 在 Grover 算法下有效强度减半,剩下相当于 128 位的量子安全度,这个余量目前够用。私有标签那一项用 SHA-256,这个尺寸的哈希函数本来就不怕量子攻击。第三项是余额承诺,用的是 Pedersen 承诺,后面我会单独说它。
这三项不需要动,是因为这些算法从一开始就不怕量子计算机,任何人拿去用都一样。它们没有体现任何 Rayls 特有的工程投入。
所以按工作量算,属于 Rayls 主动完成的是七分之二,不是七分之五。
我不认为这是有意夸大。文章把每一项的状态都标得很清楚,肯读的人自己就能分出来。只是”五个已经抗量子”这个总结句会比拆解本身传播得更远,而它单独看起来像是完成了七成的活。
论文用的词,和公告不太一样
文章说,Rayls 的学术规格发表在 IACR 密码学电子档案上,机构可以据此独立验证这些声明。这句话是一份公开邀请,所以我去查了。
我查到的是编号 2025/1639 的那篇,标题是 Rayls: A Novel Design for CBDCs,作者是 Mario Yaksetig 和 Jiayu Xu。文章提到的 Rayls II,我没有找到对应的公开编号,这一点我没能核实。
论文里有两处值得注意。
第一,论文对 Groth16 的说法。它明确写了偏好 Groth16 的理由是验证方开销轻,也明确写了这个方案的局限。但论文点名的局限是需要可信设置,并说这个设置可以用多方方式完成来降低信任假设。也就是说,论文谈 Groth16 时讲的是信任假设问题,而 8 月 30 日这篇公告谈 Groth16 时讲的是量子问题。两处说的不是同一件事,公告说”论文明确承认了这一点”,至少在我查到的这篇里,承认的不是同一个”这一点”。
第二,论文形容自己的设计用的词是 quantum-private,量子隐私,具体解释是量子对手无法推断出网络中交易的付款人、收款人和金额。这是一个关于机密性的主张。
而公告全篇的框架是 quantum-resistant,抗量子。在密码学里,机密性和不可伪造性是两个分开的性质,一个系统可以做到前者而做不到后者。
这个区别落到组件五 Pedersen 承诺上就变得具体。Pedersen 承诺的标准性质是隐藏性无条件成立、绑定性只在计算上成立,而绑定性依赖的是离散对数难题,那正是量子计算机能解的那一类。公告说这两个性质在 Enygma 的使用场景下都保持量子安全,并标为无需处理。
我不知道这句话对不对。它说的是”在 Enygma 使用它的场景下”,而具体是什么场景,公告没有展开,我也没有能力从外部判断。我想说的只是,这是全篇七个组件里唯一一处结论与教科书性质表面上不一致的地方,而它恰好被标成了无需处理。按这篇文章自己提倡的精确标准,这一处值得展开说明。
还没定的部分
有两个组件公告自己就写明了没解决,这一点我认为处理得很坦率。
零知识证明用的 Groth16 基于配对密码学,目前没有可用于生产的后量子替代品。公告说这是全行业的缺口,不是 Rayls 独有的,所有用 SNARK 做隐私的链都在同一个位置上。这个说法我认为成立。它的应对是把证明系统设计成模块化可替换,等后量子零知识研究成熟后再换。
钱包密钥用的是标准 EVM 的 ECDSA,不抗量子。这是整个以太坊生态共同的约束,今天没有任何 EVM 兼容链拿出了可用于生产的后量子钱包密钥方案。
除此之外,我自己这边也有没查证到的:Rayls II 论文的公开编号,以及组件二 ML-KEM 的参数级别。这两项都不是我能从外部推断的,只能靠官方补充。
我的看法
这篇公告的核心论点我是赞同的:面对量子迁移,逐组件说清楚比一个”量子安全”标签有价值得多,而肯承认缺口的供应商比只会贴标签的更可信。
我这篇文章不是要反驳它,恰恰是接受了它的前提。一篇呼吁精确的文章,值得被精确地读,这本来就是它自己要求的待遇。
后面怎么判断,我盯的主要是一件事:ML-KEM 那个参数级别会不会被补上。
这是公告自己列的第三个问题,答案只要一行字。补了,说明那六个问题不只是拿来考别人的;不补,那”精确胜过标签”这句话在自己身上就没落地。这条我认为是最干净的观察指标,因为它成本极低,不存在”做不到”的解释空间。
另外两处我会顺带留意。Rayls II 的论文编号如果公开出来,公告里”可供独立验证”那句话才算真正成立。至于 Pedersen 承诺那一处的”使用场景”,如果哪天官方愿意展开讲,那会是这份组件清单里最值得读的一段。
顺带说一件跟公告无关但和这个话题有关的事。我核实时间线的时候发现,NIST 在 2024 年 8 月 13 日发布、8 月 14 日生效的是三份标准,FIPS 203、204、205。HQC 是 2025 年 3 月 11 日才选定的,而基于 FALCON 的 FIPS 206 到现在仍在制定中。网上有不少二手报道把 FIPS 206 也算进 2024 年那批里,这是错的。这篇公告在这一点上写得是准确的。
参考来源:Rayls 官方博客 The Quantum Clock is ticking: what financial institutions need to do before 2027,Selvaggia di Fazio,2026 年 8 月 30 日;NIST 后量子密码标准化项目页面,FIPS 203 / 204 / 205 于 2024 年 8 月 13 日发布,联邦公报载明 8 月 14 日生效,HQC 于 2025 年 3 月 11 日选定,FIPS 206 制定中;NSA CNSA 2.0 时间表,2027 年 1 月 1 日新采购闸门,指定 ML-KEM-1024 与 ML-DSA-87;IACR 密码学电子档案编号 2025/1639,Rayls: A Novel Design for CBDCs,Mario Yaksetig 与 Jiayu Xu。
#Rayls $RLS

When blockchain projects talk about enterprise adoption, they typically focus on how “our technology is more advanced.” This time, the article Rayls put out is different. It spends the better part of the piece talking about customer complaints, and the complaints are fairly blunt. After reading it, I felt that what’s truly worth saying isn’t the list of products, but the fact that it admits something the industry is generally reluctant to acknowledge.
First, there’s something unusual about this release itself.
On August 25, Rayls launched Sovereign—a private blockchain intended for financial institutions. But according to official statements, its underlying platform has been running in production environments since June 2024, with more than 30 financial institutions already onboard and using it. Sovereign is a thoroughly rebuilt version of the earlier product called Rayls Privacy Node; the rewrite was thorough enough that they changed the name.

I usually just glance at regulatory news and move on, because most of it has little to do with ordinary holders. But after reading these UK rules, I changed my mind, because there’s a rather unobvious mechanism that will genuinely affect which chain institutions choose in the future.
First, lay out the timeline clearly, because that determines how urgent it is.
On February 4, 2026, the UK Parliament passed the relevant regulations. On June 30, the FCA published the core details of the制度, with a total of five policy documents. The authorized gateway opened on September 30, while the complete scope of regulated activities will not fully take effect until October 25, 2027.

In the previous post, I talked about the staking being opened up itself. But in the backend, the most frequently asked question from many brothers was actually the same sentence: exactly how do you do it? So this time, I went through the whole process again from start to finish, and wrote down every step and every spot that’s easy to get stuck. Just follow it.
Here’s the link to the previous post: 质押开放给所有人了,但有几件事最好先知道
First, let’s make it clear who this article is for. If you’ve never come across Rayls at all— and even aren’t very familiar with terms like wallets or bridging— then this is written for you. For every piece of technical terminology, I’ll briefly explain it along the way.

I started staking from the batch of pre-commitments in June, so I’ve gone through this whole process already. This time it’s open to everyone. A lot of people around me have been asking how to operate it and what to watch out for, so I’m just going to lay everything out clearly in one go.
First, let’s talk about the change itself.
Rayls uses delegated proof-of-stake: validators run nodes, produce blocks, and help secure the public chain. Regular holders don’t need to run nodes themselves—they can delegate their RLS to a validator and share part of the staking rewards.
This mechanism went live in June, but at the time it was only available to wallets that participated in the pre-commitment plan and the liquidity seed activities. Those participants locked their tokens before the mainnet launch, and the official team offered a three-month 55% boosted annualized return. They even sent 1 USDr to each qualifying wallet so they wouldn’t even have to worry about having gas.

I’ve been going through the Rayls docs, and one thing I initially found confusing was the difference between a Privacy Node, Private Network, and Public Chain.
After looking at how they connect, it became much easier to understand.
They each have a different role.
1. Privacy Node: the institution’s own blockchain
A Rayls Privacy Node is an EVM-compatible chain operated by a single institution.
What happens inside the institution stays inside its own environment.
It can issue tokens, manage balances, run smart contracts and handle its internal activity there.
One detail I found important: a Privacy Node is not a validator.
The docs describe it more like the institution’s own onchain environment, where its data, keys and workflows are controlled by the institution itself.
That makes sense for banks because they need control over sensitive financial information.
2. Private Network: where institutions interact
The next part is the Rayls Private Network.
This is a permissioned blockchain network where multiple institutions can connect through their Privacy Nodes.
So instead of every institution keeping its own isolated blockchain, they can interact with other approved participants while keeping transactions private.
Rayls uses a Private Network Hub to coordinate these interactions.
This is where Enygma becomes interesting.
Enygma is Rayls’ privacy protocol for confidential transactions. The docs show how it can be used for private token transfers and Delivery-versus-Payment, where two assets can be exchanged while keeping sensitive transaction information protected.
There is also an auditor role, so privacy doesn't simply mean that nobody can ever inspect anything.
That balance between confidentiality and authorised visibility is one of the things I found interesting while going through the docs.
3. Public Chain: the open side
Then there is the Rayls Public Chain.
This is an EVM-compatible Layer 1 designed to connect the institutional side with the open blockchain ecosystem.
This is where public applications, assets and DeFi can operate.
The current docs also mention over 10,000 TPS and sub-second deterministic finality through Rayls' Axyl consensus.
So the Public Chain isn't simply another place to store assets.
It is the open side of the architecture.
The simple way I understand it now
Think about an institution issuing a tokenised asset.
Privacy Node
The institution creates and manages the asset in its own environment.
↓
Private Network
The institution can interact with other approved institutions privately.
↓
Public Chain
The asset can reach the open blockchain ecosystem and public liquidity when appropriate.
Of course, the actual flow depends on the use case. The important part is that Rayls doesn't force every activity into the same environment.
Each environment has a specific job.
And this is where Rayls Enygma fits
This was probably the most interesting part for me.
Blockchain usually gives you transparency by default, but financial institutions often need the opposite for sensitive transactions.
Enygma is designed to provide confidential transactions while keeping them verifiable and auditable.
For example, Rayls documents describe confidential transfers where the sender, recipient and amount can be hidden from public view, while authorised auditors can still access the necessary information.
It also supports private DvP flows for tokenised assets.
So the goal isn't simply:
"make everything private."
It is more about giving different participants different levels of visibility depending on what they are authorised to see.
What I took away from exploring Rayls
Before going through the docs, I mostly thought of Rayls as another blockchain project focused on institutions.
After looking at the architecture, I see the idea differently.
The Privacy Node gives an institution its own controlled onchain environment.
The Private Network lets approved institutions interact.
The Public Chain connects that institutional infrastructure to the open blockchain world.
And Enygma provides the privacy layer for sensitive activity.
That separation is probably the part of Rayls I found most interesting.
Instead of asking institutions to choose between private infrastructure and public blockchain access, Rayls is building a way for the two sides to work together.
That was the part that clicked for me after actually going through the docs.
@Rayls #Rayls

Most projects talk about a burn mechanism—about how much we will burn. I’m more curious about the upstream part: where did those burned tokens originally come from? Rayls’s design answers this in a way that surprised me—it starts with a fiat payment.
First, the conclusion. The starting point of the entire chain isn’t in the world of encryption; it’s a fiat payment issued by an institution in its own country.
When an institution conducts business on Rayls through privacy nodes, it generates fees. The key design is that they can settle directly in fiat, or choose to use USDr or RLS.

When I look at lockup announcements, they usually only care about one thing: whether this commitment can be verified. Most projects’ “team lockup” ultimately comes down to a single sentence—you either choose to believe it or you don’t. This time is a bit different, so I checked on-chain.
First, let’s state the facts clearly. Parfin is the core technology provider behind Rayls. It is responsible for developing privacy nodes, the private network, the Enygma privacy framework, and the Rayls mainnet. As compensation for its work prior to the TGE, it received 1,070,493,535 RLS tokens—about 11% of the initial total supply of 10 billion.
This batch of tokens was previously held by an institutional custodian on Ethereum. The reason is straightforward: at the time of the TGE, the Rayls chain hadn’t gone live yet, so the tokens could only be held in custody. Now that the mainnet is available, this batch has been migrated to the Rayls chain and locked in a smart contract that can be publicly verified. At the same time, the unlock date has been pushed back from December 2026 to December 2027.

To be honest, the first time I saw these three abbreviations put together, I thought they were three different answers to the same question: faster, safer—pick one and you’re done. Later I realized that ranking them side by side is like asking, “Which is best—a hammer, a screwdriver, or a wrench?” The answer depends on whether you have a nail, a screw, or a bolt.
The issues they each solve are actually three problems that have been conflated.
The first problem is: I want to prove that something is true, but the data needed for the proof is sensitive, and I don't want to show it to you. A bank wants to tell regulators that a transaction is legal, authorization is correct, and there are no duplicates—yet it doesn't want to put the amounts and the payer/payee details on the ledgers. This kind of proof that is true but doesn't reveal the underlying data is ZK’s home turf. Its charm lies in guaranteeing the conclusion comes from mathematics, not from “I promise you, I won’t let you see.” Regulators or auditors who receive the verification key can check the result, but they can’t touch the underlying data. The cost is also real: it’s good at proving properties of data, but not good at letting multiple parties compute together when no one has complete data, and it’s far more compute-intensive than plaintext.

Brothers, I’ve been lurking in the Rayls community for a long time. I know everyone is very dissatisfied with the team—so am I. But the team is really doing work and has been putting in effort. It’s just that the Rayls team is taking a compliance-first route. Brothers, don’t give up—leave it to time. I believe the Rayls team will ultimately deliver the exam papers that satisfy us. Let me share some good news with you brothers—it's about the recent Rayls team integrating with an RPC. This is a very important thing!!
A quick overview at a glance
What is RPC
You can think of RPC as a dedicated hotline between an application and the blockchain.

In the crypto circle, you can see “some traditional finance giant is moving into blockchain” every week. I mostly swipe past headlines like this, because in most cases they end up in an innovation lab, issue a press release, and then there’s no follow-up. There’s a very simple way to judge whether something is true: for an ordinary customer, in their own app, can they directly click in and use it?
XP Inc. This time it met the standard.
First, get a clear picture of the company, because its scale determines how much weight this carries. XP is a Brazil-based investment platform listed on Nasdaq, ticker symbol XP. I checked its investor relations page for Q1 2026 data: customer assets are on the order of R$152.9 billion reais—more precisely, R$1.529 trillion; there are more than 18,000 financial advisors; and over the past twelve months, total revenue is R$19.8 billion reais, with pre-tax profit of R$5.8 billion reais.

In my previous article about XP, I kept wondering about one thing: once an institutional stablecoin like USDXP is issued, how exactly does it participate in real cross-border settlement? This piece is my attempt to fill in that gap, and it also helped me finally understand a term for the first time: “stablecoin sandwich.”
First, let’s explain this term. It’s actually very visual. A single cross-border payment: the two ends are your local currency, with a layer of public stablecoin in the middle. The payer converts their local currency into a USD stablecoin; the stablecoin completes the cross-border settlement on-chain; then the payee converts it back into their own local currency. Doesn’t it look like two slices of bread with that middle layer in between? That’s the phrase the industry started using to describe stablecoin-based cross-border settlement.

To be honest, when it comes to partnership news, I usually just glance at it and swipe past. Nine out of ten are only re-hanging logos with each other. But I stopped and read this one through because it touches the most boring—and also the most expensive—part of cross-border payments.
Cross-border remittances are slow, and many people think it’s because the “network is slow.” The real reason is much more boring: it isn’t that the money is “sent” over; it’s been “sitting there” already. When a bank wants to pay to a particular country, it usually has to open an account with a local bank in advance and pre-deposit a large amount of money there—a piece of jargon called a nostro account. Every payment corridor around the world has to keep a slice of funds, like depositing a stack of cash at each friend’s house in case you pass by one day and need it. The money stays idle on the books, and exchange-rate fluctuations are borne by the account balance itself. After a cross-border payment runs its course, it often takes several days.

Rayls is a project I’ve followed for a long time. Recently, it launched a community project called The Rail, and the gameplay is somewhat different from the usual "points-grinding activities." It doesn’t reward spamming; it recognizes people who consistently put in real effort. In short, let me explain how it works! Family, if you also think it’s great, come join and fill out the form to get on board.
https://tally.so/r/dWgdrA
1. What is The Rail
The Rail is Rayls’s community ambassador program. Its purpose is to recognize meaningful contributions and turn them into identity, permissions, and rewards. The official positioning is: "a community built on real contributions, not a points-grinding game," described as "a small family room where everyone genuinely cares about one another." The operating logic is: you contribute → earn points → level up your role → get recognized.

Rayls is up 79.00% to $0.00702 in 24h, dramatically outperforming a flat broader market, primarily driven by a speculative surge in a low-liquidity asset.
Primary reason: Extreme volume spike and low liquidity, with trading volume surging over 603% to $38.96M, amplifying buy-side pressure.
Secondary reasons: No clear secondary driver was visible in the provided data; the move appears isolated from broader market trends.
Near-term market outlook: If RLS holds above $0.0050, a test of the $0.0080 area is possible; a break below $0.0050 risks a sharp retracement toward $0.0035, with sustainability hinging on whether high volume persists.
Deep Dive
1. Speculative Pump in Low-Liquidity Asset
Overview: The price surge was accompanied by a 603% explosion in 24h trading volume to $38.96M. The turnover ratio (volume/market cap) is 3.70, indicating extremely thin liquidity where relatively small trades can cause large price swings. This pattern is characteristic of a low-float asset experiencing a speculative pump.
What it means: The move is driven by concentrated buying pressure in an illiquid market, not by fundamental developments or broad market beta.
Watch for: A sustained decline in volume, which often precedes a reversal in such pumps.
2. No Clear Secondary Driver
Overview: No specific news, partnership, or ecosystem catalyst for Rayls was present in the provided data. The total crypto market cap was nearly flat (+0.59%), and Bitcoin dominance was unchanged, showing RLS moved independently of macro trends.
What it means: The rally lacks an identifiable fundamental catalyst, increasing the risk of a volatile correction if speculative interest fades.
3. Near-term Market Outlook
Overview: With no specific upcoming events in context, focus shifts to key levels and volume. The immediate support is the $0.0050 zone. Holding above it could see a push toward $0.0080. However, the extreme 79% gain on thin liquidity makes the asset vulnerable; a break below $0.0050 could trigger a swift drop toward the $0.0035 level.
What it means: The outlook is highly volatile and contingent on whether the extraordinary volume sustains or evaporates.
Watch for: Volume sustaining above $20M for continued momentum, or dropping below $10M as a warning of buyer exhaustion.
Conclusion
Market Outlook: Highly Speculative & Volatile The surge is a classic low-liquidity pump, detached from fundamentals or market trends, making it prone to sharp reversals. Key watch: Can RLS maintain trading volume above $20M to support prices, or will a volume collapse trigger a rapid mean reversion.
#Rayls $RLS