Stellar’s Bell upgrade this week has been spun by a bunch of accounts as “XLM is now quantum-resistant.” I checked the original text from the SDF itself, and that claim is at least half an exaggeration.
First, the facts: the Protocol 30 mainnet vote is scheduled for 11/23 at 17:00 UTC, which is 1:00 a.m. on Tuesday, November 24, Beijing time. It only takes effect if validators vote to approve it. There are three changes in total: CAP-84 adds 64-bit IDs to contract addresses, creating a new address format that starts with W; CAP-87 lets Soroban contracts verify ML-DSA signatures; and CAP-88 changes ledger time to millisecond precision.
The key point—one many people left out—is this line in CAP-87: transaction signatures on the network will still use Ed25519 for now. Native quantum-resistant signatures for classic accounts will have to wait for a future protocol upgrade. In plain English, the XLM in your G-address will still use elliptic-curve signatures even after the vote passes. If quantum computing really arrives, those funds will still be exposed. This upgrade merely lays a foundation for contract accounts, allowing people to write a contract wallet that “requires a quantum-resistant signature to spend funds.” The SDF’s own wording is that the next step depends on adoption, and the entire industry is still researching how that adoption might happen.
Why put this in Core instead of having contracts do the verification themselves? Because ML-DSA is computationally heavy. According to NIST FIPS 204, even the smallest ML-DSA-44 signature is 2,420 bytes, while an Ed25519 signature is only 64 bytes—that’s over 30 times larger. Signature verification also costs a lot more. So even if wallets get built, every authorization from a quantum-resistant account will involve more data and higher costs than it does today. Security doesn’t come free.
The change with real business implications is actually the one getting the least hype: CAP-84. Exchanges and fiat on/off-ramps currently use muxed accounts (starting with M) to collect funds from all their customers in a single account. Smart contract accounts didn’t have this feature, which effectively meant one contract per customer—a model that simply doesn’t scale. With W-addresses, custodians may finally be able to move customer funds into contract accounts. Note that it’s only a possibility: exchanges would have to be willing to change their deposit systems, so this won’t turn into on-chain demand in the short term.
As for the price, Binance’s XLMUSDT pair has fallen from an opening price of 0.1733 on October 24 to around 0.1275 now, down 26% in a month. Pitching a developer-focused upgrade as a catalyst for a price rally is like mistaking a roadmap for buying pressure. The vote passing is good news, but it has very little to do with whether your few XLM will go up next week.
#XLM #Stellar
First, the facts: the Protocol 30 mainnet vote is scheduled for 11/23 at 17:00 UTC, which is 1:00 a.m. on Tuesday, November 24, Beijing time. It only takes effect if validators vote to approve it. There are three changes in total: CAP-84 adds 64-bit IDs to contract addresses, creating a new address format that starts with W; CAP-87 lets Soroban contracts verify ML-DSA signatures; and CAP-88 changes ledger time to millisecond precision.
The key point—one many people left out—is this line in CAP-87: transaction signatures on the network will still use Ed25519 for now. Native quantum-resistant signatures for classic accounts will have to wait for a future protocol upgrade. In plain English, the XLM in your G-address will still use elliptic-curve signatures even after the vote passes. If quantum computing really arrives, those funds will still be exposed. This upgrade merely lays a foundation for contract accounts, allowing people to write a contract wallet that “requires a quantum-resistant signature to spend funds.” The SDF’s own wording is that the next step depends on adoption, and the entire industry is still researching how that adoption might happen.
Why put this in Core instead of having contracts do the verification themselves? Because ML-DSA is computationally heavy. According to NIST FIPS 204, even the smallest ML-DSA-44 signature is 2,420 bytes, while an Ed25519 signature is only 64 bytes—that’s over 30 times larger. Signature verification also costs a lot more. So even if wallets get built, every authorization from a quantum-resistant account will involve more data and higher costs than it does today. Security doesn’t come free.
The change with real business implications is actually the one getting the least hype: CAP-84. Exchanges and fiat on/off-ramps currently use muxed accounts (starting with M) to collect funds from all their customers in a single account. Smart contract accounts didn’t have this feature, which effectively meant one contract per customer—a model that simply doesn’t scale. With W-addresses, custodians may finally be able to move customer funds into contract accounts. Note that it’s only a possibility: exchanges would have to be willing to change their deposit systems, so this won’t turn into on-chain demand in the short term.
As for the price, Binance’s XLMUSDT pair has fallen from an opening price of 0.1733 on October 24 to around 0.1275 now, down 26% in a month. Pitching a developer-focused upgrade as a catalyst for a price rally is like mistaking a roadmap for buying pressure. The vote passing is good news, but it has very little to do with whether your few XLM will go up next week.
#XLM #Stellar