TL;DR: On Monday, November 23, 2026, at 17:00 UTC, Stellar validators vote on whether to activate Protocol 30, code-named Bell. The upgrade bundles three changes: muxed contract addresses that let one smart account serve many customers (CAP-84), verification of ML-DSA post-quantum signatures inside Soroban smart contracts (CAP-87), and millisecond ledger close times (CAP-88). Bell does not make Stellar post-quantum: transaction signatures stay Ed25519, and only smart contracts gain the ability to check quantum-safe signatures. XLM holders do not vote — validators do. The November 23 date is a scheduled vote, not a guaranteed activation.
Last updated: November 2026
Key Takeaways:
- The vote is by validators, not XLM holders. Validators arm their nodes for November 23 at 17:00 UTC, and Bell activates only if enough of them agree.
- CAP-84 gives contract addresses a 64-bit customer ID in a new W format, so one smart account can receive payments for many customers instead of needing a contract per customer.
- CAP-87 lets smart contracts verify ML-DSA signatures, the post-quantum standard NIST finalized in 2024. Network transaction signatures stay Ed25519 — Bell is a quantum-safe option inside contracts, not a post-quantum network.
- CAP-88 records ledger close times in milliseconds instead of whole seconds. Ledgers do not close faster yet; the change is the prerequisite for faster ledgers later, and it changes the ledger header format.
- If the vote fails, nothing changes on mainnet. The upgrade waits for a new vote date, and wallets, exchanges, and indexers keep running on Protocol 29.
Most blockchain upgrades arrive as a launch date. Bell arrives as a vote. On November 23, the people who run Stellar's validator nodes decide whether the network adopts three new rules at once — and the decision is theirs alone. No token holder ballot, no foundation switch, no automatic activation at a block height. The Stellar Development Foundation (SDF) has published the code, the guide, and the timetable, but the network moves only when the validators agree.
That makes Bell worth understanding before the vote, not after it. This article works through what each of the three changes does, who has to act before November 23, and what happens if the vote goes the other way.
What Is Stellar's Bell Upgrade?
Stellar is a layer-1 blockchain built for payments, and Soroban is its smart-contract platform. Protocol versions are how Stellar changes its own rules: each new protocol version bundles a set of Core Advancement Proposals (CAPs), formal requests to change network behavior. Bell is Protocol 30, and it carries exactly three CAPs — no fee-market change, no change to how the network reaches consensus, and nothing else.
SDF describes the release in one sentence: "It's designed to make smart accounts ready for businesses at scale and start the work on two longer-term goals: quantum-safe signatures and faster ledgers." A smart account is a contract that controls funds and enforces its own spending rules, rather than a plain keypair account. Bell's three changes each remove a different obstacle to running those accounts for many customers.
The engineering started on October 16, 2026, when Stellar Core v30.0.0 shipped as a stable build, followed by Protocol 30 versions of Horizon, RPC, Galexie, and the maintained SDKs. The JavaScript SDK v17.3.0 followed on October 21. The testnet vote passed on November 3 at 17:00 UTC, putting Bell live on testnet. The mainnet vote is scheduled for November 23 at the same time — Monday at 17:00 UTC, Tuesday, November 24, at 00:00 WIB.
Who Votes on November 23 — and Who Doesn't
Stellar does not switch protocols at a fixed block height. Validators — the node operators who run the network — enter a protocol version and a point in time into their configuration, and the network raises its version only once enough voting weight comes together. The vote uses the same trusted-validator sets and thresholds that approve transaction sets. SDF distributes the command validators use to arm their nodes through validator channels ahead of the date, and status updates go to the #protocol-next channel of the Stellar Developer Discord.
That mechanism has two consequences. First, XLM holders do not vote: holding the token gives you no ballot; the decision sits with the operators who run the infrastructure. Second, the date is a scheduled vote, not a delivery guarantee — SDF's own page says dates are subject to change, and the upgrade takes effect only if the vote reaches the consensus threshold.
For end users and holders, the upgrade guide contains no instructions — not an oversight, but a consequence of the design. The work sits with the operators, not with the owners of the balances. If you hold XLM, there is nothing to sign, nothing to migrate, and nothing to claim. The people with homework are validators, exchanges, wallet developers, and anyone who reads raw ledger data.
CAP-84: One Smart Account, Many Customers
The most immediately practical of the three changes is CAP-84, muxed contract addresses. A contract address can now carry a 64-bit identifier, written in a new address format that begins with the letter W. The identifier is recorded in the transfer event, so a payment to a W address can be traced to the customer it belongs to.
To see why that matters, consider an exchange or a payment provider that holds customer funds in a smart account. Before Bell, one contract could not easily tell whose money was whose. The workaround was to deploy a separate contract for every customer — an approach SDF describes bluntly as working for ten customers, not for a million. With CAP-84, a single smart account can serve many customers: each customer gets a W address that points at the same contract plus their own 64-bit ID, and the contract can route and account for each payment separately.
This mirrors something Stellar's classic accounts have had for years. Ordinary Stellar accounts support memo-based routing, where a payment carries a memo identifying the customer. Muxed contract addresses bring the same convenience to smart accounts, with the identifier built into the address itself rather than attached as a memo. Wallets, exchanges, and on- and off-ramps have to add W addresses to their validation, display, and storage logic — accepting the new format is not automatic, and apps that validate addresses with their own code must update it even though the SDKs parse the new format.
One thing CAP-84 does not do: it does not prove that customer balances are legally or operationally segregated. The identifier is an accounting convenience, not a custody guarantee.
CAP-87: Post-Quantum Signatures, but Only Inside Smart Contracts
CAP-87 is the change that makes the headlines, and it is also the easiest to misunderstand. It adds three host functions to Soroban, Stellar's smart-contract environment, that verify ML-DSA signatures: verify_sig_ml_dsa_44, verify_sig_ml_dsa_65, and verify_sig_ml_dsa_87, one per parameter set of the ML-DSA standard. ML-DSA (Module-Lattice-Based Digital Signature Algorithm) is one of the post-quantum signature standards the US National Institute of Standards and Technology finalized as FIPS 204 in 2024. It is built on lattice mathematics, which — unlike the elliptic-curve math behind today's signatures — is believed to resist attacks from a sufficiently powerful quantum computer.
Like almost every major blockchain, Stellar secures accounts with elliptic-curve signatures, which a large enough quantum computer could break by running Shor's algorithm. That is the threat behind all the quantum talk in crypto: a machine that can derive a private key from a public one breaks the link between an address and its owner. Ethereum faces exactly the same exposure, and Vitalik's quantum-safe plan for Ethereum follows the same logic as Bell — give contracts a way to check a quantum-resistant signature before letting money move.
What CAP-87 actually does is narrower than the headlines suggest. It lets a smart contract verify an ML-DSA signature. A custom account contract can now require a quantum-safe signature to spend: the contract checks the ML-DSA signature, and only then authorizes the transaction. Verification runs inside Stellar Core rather than in contract code, which keeps it cheap to call and means the implementation is written and tested once, against the official test vectors, instead of being reimplemented by every contract author. The three parameter sets trade size against security, with ML-DSA-87 using larger keys and signatures for a higher margin than ML-DSA-44.
What it does not do is equally important. Network transaction signatures stay Ed25519. The overwhelming majority of Stellar accounts — the ones that are plain keypairs rather than contracts — are unaffected. SDF's own FAQ answers the obvious question directly: "Does Bell make Stellar post-quantum? No. It lets smart contracts verify ML-DSA signatures, so contract accounts can opt into quantum-safe authorization. Network transaction signatures remain Ed25519." A native post-quantum signer for classic accounts is left to a future protocol change. Bell is the first onchain component of Stellar's Quantum Preparedness Plan, not the plan itself.
The core team also warns against adopting ML-DSA too early: passkeys today use secp256r1, and post-quantum passkeys need platform and wallet support first. Giving up hardware signing just to get a post-quantum property would be a step backward. The option exists now; the right time to use it depends on the wallet and custody stack around it.
CAP-88: A Millisecond Clock for the Ledger
CAP-88 is the quietest of the three changes and the one that demands the most attention from infrastructure teams. It records ledger close times in milliseconds instead of whole seconds. That sounds like a small formatting detail, and in one sense it is: it changes the ledger header format so that close times carry millisecond precision.
The reason it matters is that it is the protocol-level prerequisite for faster ledgers. Stellar ledgers currently close about every five seconds, and Bell does not change that. But with close times recorded only to the second, the network could not express a shorter interval even if the consensus machinery were ready for one. With millisecond timestamps in the header, future protocol changes can support more precise closing intervals. Stellar Core developers are already experimenting with faster processing, but that work ships later.
The catch is that changing the ledger header format breaks anything that reads raw ledger data without understanding the new format. SDF says so plainly: "Bell changes the format of the ledger header so anything that reads the ledger data needs to understand the format." SDK users should upgrade before the vote, and anything that decodes raw ledger data — indexers, explorers, analytics pipelines — must update its XDR definitions. Older SDKs may fail to decode Protocol 30 ledgers entirely.
Timeline: From Core v30.0.0 to the Mainnet Vote
| Date (2026) | Event |
|---|---|
| Sep 17 | Core team presents CAP-87 at the Stellar protocol discussion; ML-DSA host functions and costs are reviewed publicly. |
| Oct 16 | Stellar Core v30.0.0 ships as a stable build, implementing all three CAPs. |
| Oct 20 | SDF introduces Bell, Protocol 30, and publishes the upgrade guide. |
| Oct 21–23 | Protocol 30 versions of Horizon, RPC, Galexie, and the SDKs ship, including JavaScript SDK v17.3.0. |
| Nov 3, 17:00 UTC | Testnet upgrade vote. Validators approve, and Bell goes live on testnet. |
| Nov 4 | SDF announces the testnet activation and reminds the ecosystem the mainnet vote is November 23. |
| Nov 23, 17:00 UTC | Mainnet upgrade vote. Bell activates only if validators reach the consensus threshold. |
The Three CAPs at a Glance
| Proposal | What it changes | Who it helps first | What it does not do |
|---|---|---|---|
| CAP-84 | Muxed contract addresses: a 64-bit customer ID in a new W address format | Exchanges, custodians, payment providers, smart-account builders | Prove customer funds are legally or operationally segregated |
| CAP-87 | Three Soroban host functions verifying ML-DSA-44, ML-DSA-65, and ML-DSA-87 signatures | Smart-account and custody contract developers | Make Stellar's network signatures post-quantum; those stay Ed25519 |
| CAP-88 | Ledger close times recorded in milliseconds instead of whole seconds | Core infrastructure, SDKs, indexers, and future performance work | Make ledgers close faster; they still close about every five seconds |
Who Has to Do What Before November 23
The upgrade guide splits the work cleanly by role, and the deadlines are the same for everyone: before the vote.
Validators install Stellar Core v30.0.0 and wait for the arming command, which SDF distributes through validator channels ahead of the date. Their job on November 23 is to vote — and the vote is the upgrade. There is no separate activation step afterwards.
Exchanges and custodians upgrade their SDKs and add support for withdrawing to muxed contract addresses. A customer asking to withdraw to a W address is a normal request after Bell, and an exchange that cannot validate or store that address format will fail the withdrawal.
Wallets and on- and off-ramps add W addresses to validation, display, and storage. A wallet that rejects a W address as invalid, or displays it without the customer ID, breaks the feature for the person it was built for. Account security does not change with Bell, but it is worth re-checking how wallet drainers work and how to check and revoke token approvals — a new address format is exactly the kind of change phishing copycats exploit.
Indexers, explorers, and analytics services update their XDR definitions before the vote. Anything that decodes raw ledger data without an SDK has to understand the new header format, or it will misread Protocol 30 ledgers.
Contract developers do not have to change existing contracts, which keep working after the upgrade. But teams that want the ML-DSA functions must rebuild against the Protocol 30 Soroban SDK and use a matching or newer Stellar CLI. The new host functions are opt-in capacity, not a change to existing behavior.
What Happens If the Vote Fails
If validators do not reach the threshold on November 23, nothing changes on mainnet. Protocol 29 keeps running, existing contracts and wallets keep working exactly as before, and Bell waits for a new vote date. That is the design: a failed vote is a "not yet," not a crisis.
The more interesting failure mode is not the vote itself but readiness: an indexer that cannot decode the new ledger header, a wallet that rejects W addresses, an exchange that cannot process a withdrawal to a muxed contract address. The testnet vote on November 3 existed so those integrations could be exercised before real money was involved.
There is also a timing risk: the vote date is scheduled, not guaranteed, and SDF says dates are subject to change. If a critical SDK is not ready, or a testnet issue surfaces late, the vote can move. Treat November 23 as the date of the vote, not the date Bell is live.
Why Bell Matters Beyond Stellar
Bell is a small upgrade with a long shadow. Two things make it worth watching even if you never touch XLM.
First, it is the clearest example yet of how a major chain handles the quantum question in practice: not with a flag-day migration of every account, but by adding a quantum-safe option where it can be adopted voluntarily. Ethereum is walking the same path — its quantum-safe work also starts inside contracts and wallets, not by replacing network signatures overnight. The two chains are converging on the same answer: give builders the verification primitive now, migrate the network later. The difference is that Stellar is shipping the primitive first, in a scheduled vote with a date attached.
Second, CAP-84 is a bet on what institutional crypto looks like. Exchanges, custodians, and payment providers do not want a thousand contracts; they want one account that can serve a million customers with clean accounting. Muxed addresses are plumbing, not a product — but plumbing determines whether a business can run on a chain at all.
What XLM Holders Should Check
If you hold XLM, the short version is that you do not need to do anything. But a few checks are worth making before the vote, because upgrade weeks are when confusion — and scams — cluster.
- Do not expect a vote, an airdrop, or a migration. XLM holders do not vote on Bell, and there is no new token or claim page. Anything asking you to connect a wallet to "vote" on Bell or "claim" an upgrade reward is a scam.
- Check that your wallet has published a Protocol 30 update, and install it before November 23. A wallet on an old SDK may fail to decode Protocol 30 ledgers. This is the same habit as why your wallet needs more than one blockchain — the wallet is where network changes become your problem, so keeping it current is the cheapest insurance.
- Watch for W addresses after the vote, and treat them as normal. A payment address starting with W is a muxed contract address, not an error. If your wallet rejects one, that is a wallet bug to report, not a network problem.
- Do not trade the vote as a price event. Bell changes developer capacity, not XLM supply, fees, or consensus. A successful vote is good plumbing, not a catalyst with a price target.
- Follow the vote result from SDF's channels, not from social media summaries. Status updates go to the #protocol-next channel of the Stellar Developer Discord and to SDF's official announcements. The vote result is a fact to read from the source, not a rumor to trade on.
None of this is financial advice. Bell is an infrastructure upgrade with a vote attached, and its value will show up over months in what developers build with it — not in a single day's price chart.
Frequently Asked Questions
Does Bell make Stellar post-quantum?
No. Bell lets smart contracts verify ML-DSA signatures, so contract accounts can opt into quantum-safe authorization. Network transaction signatures remain Ed25519, and plain keypair accounts are unaffected.
Do XLM holders vote on Bell?
No. Validators vote, using the same trusted-validator sets and thresholds that approve transaction sets. XLM holders have no ballot in a protocol upgrade. The vote is scheduled for November 23, 2026, at 17:00 UTC.
What happens if validators reject Bell?
Nothing changes on mainnet. Protocol 29 keeps running, existing contracts and wallets keep working, and Bell waits for a new vote date.
Will my Stellar wallet stop working after November 23?
It should not, as long as it is up to date. Wallets should install the Protocol 30 SDK update before the vote. An old SDK may fail to decode Protocol 30 ledgers, and a wallet that has not added W-address support may reject muxed contract addresses. Check for an update from your wallet provider before the vote.
What are muxed contract addresses (W addresses)?
A contract address with a 64-bit customer ID attached, written in a new format starting with W. One smart account can receive payments for many customers, with each payment tagged by the ID in the transfer event. It is the contract equivalent of the memo routing that classic Stellar accounts already use.
Will Stellar get faster after Bell?
Not immediately. CAP-88 records ledger close times in milliseconds, which is the prerequisite for faster ledgers, but ledgers still close about every five seconds after the upgrade. Faster closing intervals are future protocol work; Bell only removes the timestamp restriction that blocked them.
Sources
- Stellar.org: Protocol Upgrades — Bell | Protocol 30 (vote dates, CAP-84, CAP-87, CAP-88 summaries)
- CoinMarketCap Academy: Stellar's Bell Upgrade Goes Live on Testnet Ahead of Nov. 23 Mainnet Vote (November 2026)
- BlockchainReporter: Stellar Protocol 30: What Bell Changes For XLM (November 2026)
- crypto.news: Stellar Protocol 30 Bell upgrade goes live on testnet ahead of mainnet vote (November 2026)
- Stellar Developer Docs: 2026-09-17 Protocol Discussion — CAP-87 presentation (September 17, 2026)
- KuCoin: Stellar's Bell Upgrade Live on Testnet, Mainnet Vote Set for Nov 23 (November 2026)
- Coindaro: Stellar Protocol 30 Bell upgrade: mainnet vote 23 Nov (November 2026)
- block2learn: Stellar Protocol 30 Builds a Quantum Exit Before Crisis (November 2, 2026)

