Stellar Bell upgrade adds muxed contract addresses and quantum-safe signature checks
Protocol 30 is set for testnet and mainnet votes in November, bringing new address types, ML-DSA verification and a millisecond ledger clock.
Key takeaways
- Two votes scheduled. Testnet and mainnet upgrade votes are set for November 3 and November 23, 2026 at 1700 UTC.
- Three proposed changes. The upgrade covers muxed contract addresses, ML-DSA signature verification in contracts and millisecond ledger timing.
- SDK work first. Stellar Core v30.0.0 arrived on October 16, and developers are told to update SDKs before the votes.
What happened
Stellar's next protocol release, called Bell or Protocol 30, is heading toward two upgrade votes. The Stellar Development Foundation announced it on October 20, and the testnet vote is scheduled for November 3, 2026, with the mainnet vote following on November 23, 2026. Both votes are set for 1700 UTC.
The release bundles three proposed changes. One is a muxed contract address type under CAP-84, which lets a contract address carry a 64-bit ID written in a format starting with W. Another is CAP-87, which lets smart contracts check ML-DSA signatures, a standard NIST finalized in 2024. The third is CAP-88, which moves the ledger to a millisecond clock and alters the ledger header format.
Jake Urban, Senior Engineering Manager at the Stellar Development Foundation, described the W as an upside-down M. He said the separate type helps developers tell which address they are handling. Stellar Core v30.0.0 became available on October 16, and the Protocol 30 SDKs carry updated XDR definitions plus support for the new address type. Older SDKs may fail to decode Protocol 30 ledgers.
First $0.2161Latest $0.1846-14.6% over the period
Points are daily observations, not closing prices.
Why it matters
Muxed accounts already let exchanges, ramps and custodial products give each customer a unique deposit address while funds land in one account. Smart accounts had no matching feature, so a business holding customer balances needed a separate contract per customer. CAP-84 closes that gap.
The signature work is the first onchain piece of Stellar's Quantum Preparedness Plan, introduced in June 2026. Stellar secures accounts with Ed25519, secp256k1 and secp256r1 elliptic-curve signatures, and a sufficiently large quantum computer could break these in theory. No such machine is publicly known. Network transaction signatures remain Ed25519 for now, and a native post-quantum signer for classic accounts is planned for a later protocol change.
The timing change gives the network a finer clock. In September, Protocol 28 cut mainnet close times from about 5.7 seconds to 5 seconds, and the millisecond clock would let future changes target shorter intervals. Stellar Core developers are already testing faster closes on experimental branches.
What is still unclear
- Stellar has not said when a native quantum-safe signer for classic accounts will ship. The plan targets the end of 2027 for every account to be able to add one through a protocol upgrade while keeping the same address and history, and 2026 for enterprise wallets to move to quantum-safe signing through Soroban contract accounts.
- The reports do not say whether the November votes will pass or what share of validators supports the changes.
What to watch
- 2026-11-23 Mainnet upgrade vote scheduled for 1700 UTC.
Questions readers ask
When is the Stellar Bell upgrade vote?
The testnet vote is scheduled for November 3, 2026 and the mainnet vote for November 23, 2026, both at 1700 UTC. The Stellar Development Foundation announced the release on October 20.
What changes does Protocol 30 bring?
It proposes muxed contract addresses under CAP-84, ML-DSA signature verification in smart contracts under CAP-87, and millisecond ledger timing under CAP-88. The ledger header format also changes.
Do developers need to update their SDKs?
Yes. The Protocol 30 SDKs carry updated XDR definitions and support for the new muxed contract address type, and an older SDK may fail to decode Protocol 30 ledgers. Stellar Core v30.0.0 became available on October 16.
Does Stellar use quantum-safe signatures now?
Smart contracts can verify ML-DSA signatures after this upgrade, but network transaction signatures remain Ed25519 for now. A native post-quantum signer for classic accounts is planned for a later protocol change.