We use necessary cookies for site function. For analytics and marketing, we need your consent. You can change your mind anytime. Privacy Policy
Olvis Gil · November 16, 2026 · 7 min readThe next Stellar network upgrade is Bell — Protocol 30 — and it is less a routine bump than three structural moves at once: muxed contract addresses that make smart accounts viable at business scale, post-quantum signature verification inside contracts, and a millisecond ledger clock that clears the way for faster close times. The testnet vote happened November 3, 2026; the mainnet vote is November 23, 2026 at 1700 UTC. Here is what each CAP does, who needs to act, and why it matters — based on theSDF announcement and theofficial upgrade guide.
Exchanges and ramps already know muxed accounts: one classic Stellar account plus an ID, so every customer gets a unique deposit address while funds land in a single account tracked off-chain. Smart accounts — accounts that are contracts, able to set their own spending rules like passkeys or policies — had no equivalent: one contract per customer, which does not scale. CAP-84 lets a contract address carry a 64-bit ID, written as a new W address format (the muxed M, upside-down, deliberately distinct so developers always know the type). Payments land in the contract as before; the ID rides along in the transfer event so your app knows whose balance it was.
Stellar accounts rely on elliptic-curve signatures a large enough quantum computer could eventually break. Nobody has that computer today — but public keys sit on the ledger forever, and migrations take years, so the industry starts early. CAP-87 lets smart contracts verify ML-DSA, the NIST post-quantum signature standard already shipping in OpenSSL, Java, and AWS KMS. Verification runs inside Stellar Core rather than contract code, keeping it cheap and implemented once against official test vectors. The honest scope note: this protects authorization inside contracts — network transaction signatures stay Ed25519 until a future protocol change. It is the first onchain step of Stellar’s Quantum Preparedness Plan, not the last word.
Protocol 28 (Adapter) already cut ledger close times to about five seconds. CAP-88 removes the next wall: ledgers currently record close time in whole seconds, so the protocol can never target sub-second intervals. Moving to millisecond timing opens the door for future upgrades to push close times lower — the Stellar Core team is already testing faster ledgers on experimental branches. The catch for builders: this changes the ledger header format, so anything reading raw ledger data needs to understand it.
Most builders have a short list. Upgrade your Stellar SDK before the mainnet vote — that covers the new ledger format and address types. If your product handles addresses, accept W addresses for muxed contracts. And if you decode raw ledger data without an SDK — an indexer, explorer, or analytics pipeline — update your XDR definitions or decoding stops working at the upgrade (the previous closeTime field still reports whole seconds; details are under “Breaking changes” in the upgrade guide). Validators and infrastructure operators should follow the full timeline in the upgrade guide.
October 16, 2026 — Stellar Core v30.0.0 stable released. October 16–23 — infrastructure and SDK releases followed. November 3, 2026 — testnet upgrade vote (done). November 23, 2026, 1700 UTC — mainnet vote; the upgrade takes effect if approved. Dates can shift — coordination happens in the #protocol-next channel of the Stellar Developer Discord.
SDF: Introducing Bell, Protocol 30 · Bell, Protocol 30 Upgrade Guide · CAP-84 · CAP-87 · CAP-88 ·Stellar hub ·How Stellar consensus works ·Soroban glossary ·Stellar Network masterclass

Founder of EduNode and OG Technologies EU — a Vienna consultancy for blockchain payments, tokenization, digital identity, and ISO 20022.