Stellar Protocol 30 Bell Upgrade: Nov 23 Mainnet Vote and What XLM Users Should Expect
Stellar validators vote on the Protocol 30 Bell upgrade on 23 November at 17:00 UTC. XLM holders need no migration, but wallets, exchanges and node operators must upgrade first.
Crypto Support & Research Desk
Quick answer: Stellar validators are scheduled to vote on the Protocol 30 "Bell" mainnet upgrade on 23 November 2026 at 17:00 UTC. XLM holders do not need to migrate anything and existing addresses stay valid. Bell adds muxed contract "W" addresses, post-quantum ML-DSA verification for smart contracts, and millisecond ledger close times, so wallets, exchanges and node operators must upgrade software first.
What is Stellar Protocol 30 "Bell"?
The Stellar Development Foundation (SDF) announced Protocol 30, code-named Bell, on 20 October 2026 and published an upgrade guide the same day (last updated 23 October). The protocol upgrades page lists a testnet vote on 3 November 2026 at 17:00 UTC and a mainnet vote on 23 November 2026 at 17:00 UTC, both "subject to change."
Bell went live on testnet after the 3 November vote, which SDF announced on 4 November, as reported by crypto.news. Mainnet activation depends on validators: each validator sets the target protocol version and time, and the network only moves to the new version once enough voting weight agrees.
The three changes in Bell
CAP-84: muxed contract "W" addresses
Stellar already has "M" addresses, which are muxed accounts: a normal account plus an ID, commonly used by exchanges to route deposits. CAP-84 brings the same idea to smart contracts with a new W address prefix. A W address combines a contract ID with a 64-bit customer ID, so a single contract can serve many customers.
When funds are sent to a W address, they go to the underlying contract, and the customer ID is recorded in the transfer or mint event field to_muxed_id. The guide warns that a contract function declared with a plain Address type will reject W addresses, and that apps must add W handling to validation, display, storage and routing. The SDK provides only the parser.
CAP-87: post-quantum verification for smart contracts
CAP-87 adds ML-DSA post-quantum signature verification inside Soroban, Stellar's smart-contract platform. This is for smart-account and contract authorization only. Network transaction signatures remain Ed25519, and a native quantum-safe signer for classic accounts is planned for a later protocol. Bell does not make every Stellar account quantum-safe.
CAP-88: millisecond ledger close times
CAP-88 changes the ledger header format so close times can be expressed with millisecond precision. The closeTime field still reports whole seconds, but old decoders and SDKs will fail to parse Protocol 30 ledgers. CAP-88 does not shorten block times by itself; Protocol 28, which went live on 16 September 2026, had already reduced ledger close times from about 5.7 seconds to 5 seconds, according to crypto.news.
Who needs to do what
XLM holders
You do not need to do anything with your XLM. There is no migration, no new token and no balance change, and existing addresses remain valid. Existing Soroban contracts keep working without changes.
Wallet users
Update your wallet app or hardware-wallet companion app when an update is offered. Older wallet software built on outdated SDKs may fail to read new ledgers after activation, which could show up as a frozen balance or failed history load even though your funds are safe.
Exchanges, custodians and ramps
The guide says exchanges and custodians must upgrade their SDKs and infrastructure and should add support for withdrawals to muxed contract addresses. Wallets, ramps and issuers must upgrade SDKs and add W address handling. Stellar Core v30.0.0 went stable on 16 October 2026, and Core, Horizon, RPC and Galexie v30.0.0 are required for infrastructure operators.
Developers
SDF calls the SDK upgrade mandatory before 23 November because of the ledger header change. Versions listed in the guide include JS SDK v17.3.0 (the 16.4.0 line decodes Protocol 30 ledgers but does not handle W addresses), Go SDK v0.8.0, and Rust Soroban SDK 30.0.0-rc.1, with a stable release due before the mainnet vote.
Will XLM deposits and withdrawals pause?
No official source we reviewed mentions planned downtime or deposit pauses, and we found no exchange suspension notices for XLM tied to 23 November at the time of writing. Exchanges sometimes pause a network briefly during upgrades anyway, so treat a short pause as possible, not confirmed. We saw the same pattern around the Hedera v0.79 mainnet upgrade and the Flare go-flare hard fork.
Step-by-step checklist before 23 November
1. Update your wallet. Install the latest version of your Stellar wallet from the official app store or website.
2. Keep your memo or muxed ID. When depositing XLM to an exchange, always include the memo or use the M address the exchange gives you. Bell does not change this.
3. Avoid sending near 17:00 UTC on 23 November. If you need to move a large amount, do it earlier or wait until your exchange confirms normal service.
4. Don't paste a W address into a service that rejects it. If a wallet or exchange shows an "invalid address" error for a W address, ask the service whether it supports W addresses. Do not try to "convert" it yourself.
5. Send a small test amount to any unfamiliar address type first.
6. Check status pages. Look at your exchange's official status or announcements page around the vote.
7. Node operators: install v30.0.0 builds of Core, Horizon, RPC and Galexie and upgrade XDR libraries before the vote.
How to verify the upgrade happened
After 23 November, check SDF's protocol upgrades page or a block explorer that shows the current protocol version. If the vote is postponed, SDF will update the date there. Exchanges typically post a short "upgrade completed" notice if they paused deposits.
If a transfer seems stuck after the upgrade, follow the same steps you would for any network event: confirm the transaction on a block explorer, check that your memo was correct, and contact the exchange through its official app. Our network upgrade transfer checklist covers the basics, and our note on wallets dropping network support explains what to do if your wallet app stops showing a chain.
Frequently asked questions
Do I need to do anything with my XLM for the Bell upgrade?
No. There is no migration or token swap, balances do not change and existing addresses remain valid. Just keep your wallet app updated.
What is a Stellar W address?
A W address is a muxed contract address: a smart-contract ID plus a 64-bit customer ID. It is the contract equivalent of the M muxed account addresses exchanges already use.
Will XLM deposits or withdrawals pause on 23 November?
No official source announces downtime. Some exchanges may still pause briefly, so check your exchange's status page before moving funds around the vote.
Does Bell make Stellar quantum-safe?
Not fully. Bell lets smart contracts verify ML-DSA post-quantum signatures, but network transactions still use Ed25519. A quantum-safe signer for classic accounts is planned for a later protocol.
When exactly does Bell activate on mainnet?
Validators are scheduled to vote on 23 November 2026 at 17:00 UTC. Activation needs enough validator support, and SDF says the date is subject to change.
Conclusion
Stellar's Bell upgrade is a back-end change for most people: XLM holders do nothing, while wallets, exchanges and node operators must upgrade before 23 November at 17:00 UTC. Keep your wallet updated, include memos on exchange deposits, avoid large transfers right at the vote, and ignore anyone offering an "XLM migration."
This article is for informational purposes only and is not financial or technical advice. Blockchain Support USA is an independent publication and is not affiliated with the Stellar Development Foundation or any exchange. We will never ask for your seed phrase, secret key, password or 2FA codes.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.