Stellar Validators Vote November 23 On Bell Upgrade
Bell, Stellar's Protocol 30 package, goes to a mainnet vote at 17:00 UTC on November 23. It carries muxed contract addresses, a post-quantum signature check for smart contracts and millisecond ledger timestamps, and holders don't have to lift a finger.
The vote is one afternoon. The homework sits with wallets and exchanges.
Stellar validators vote on November 23 at 17:00 UTC on Bell, the Protocol 30 upgrade that adds post-quantum signature checks. If the vote passes, the upgrade activates on mainnet the same day, and the network's validators have already cleared the same package on testnet.
Three changes ride on the single vote. CAP-84 creates muxed contract addresses, a new address type that starts with W and lets a contract account carry a customer identifier the way bank sub-accounts do. CAP-88 moves ledger timestamps to millisecond precision, a change that matters for contracts that price time in fractions of a second.
CAP-87 is the headline item. It lets Soroban smart contracts verify ML-DSA signatures, the post-quantum standard the National Institute of Standards and Technology published as FIPS 204. The check lives inside contracts, so applications can start screening post-quantum credentials without a second network vote, while the network's own transaction signatures stay on Ed25519.
The runway was short and public. The Stellar Development Foundation introduced Bell on October 20, Stellar Core v30.0.0 shipped on October 16 with the upgrade code inside, and the testnet vote passed on November 3. Validators who run the network have had the software in hand for five weeks.
For businesses
Amazon Business is Amazon’s purchasing store for companies, with business accounts and quantity ordering.Register with Amazon BusinessHolders sit this one out. XLM balances don't move, no claim window opens, and no action is required from anyone who simply holds the asset. The work lands on wallets, exchanges, custodians and indexers, which have to update their SDKs and XDR definitions so their systems read the new address type and the finer timestamps correctly.
Protocol votes on Stellar rarely fail at this stage, and the testnet result points the same way. The live question isn't the count on November 23. It's how fast the services built on top of the network ship their updates once W addresses and millisecond timestamps exist on mainnet, because a feature the wallets can't read is a feature users can't use.
Sources
The conversation.
Loading comments…
A little more perspective.
Reading is free. Verified members can comment and reply for $2 a month.