Home » Blockchain » Stellar Bell Upgrade Proposes Quantum-Safe Signatures for Smart Accounts

Stellar Bell Upgrade Proposes Quantum-Safe Signatures for Smart Accounts

Validators haven’t approved anything yet, but Stellar’s next protocol already takes a side in the quantum computing debate: patch smart contracts now, leave everyday signatures for a later fight.

Abstract glowing network nodes representing the Stellar Bell upgrade and quantum-safe signatures

How do you get a payments network ready for a computer that doesn’t exist yet? The Stellar Bell upgrade is the Stellar Development Foundation’s attempt to answer that question, and the first step still needs a vote before any of it becomes real. On October 20, 2026, the foundation published its proposal for Bell, formally Protocol 30. Validators tested it on Stellar’s testnet on November 3. A mainnet vote follows on November 23. None of it has activated yet, and the foundation’s own announcement warns that dates are subject to change.

Bell bundles three separate changes, and each one solves a different problem. One toughens Stellar’s smart contracts against a future quantum computer. One lets a single business wallet handle a flood of customers instead of just a handful. And one quietly removes a speed limit baked into how the network measures time. Here’s what each change does, who it helps, and where the plan still has open questions.

What the Stellar Bell Upgrade Actually Changes

The Stellar blog groups Bell’s changes under three Core Advancement Proposals, or CAPs. Each one ships as stable software before anyone votes on it.

Muxed contract addresses (CAP-84): A Stellar smart contract can now carry a 64-bit customer ID folded into its address. The new address format starts with the letter W.

Post-quantum signature verification (CAP-87): Smart contracts gain the ability to check ML-DSA signatures, a standard NIST finalized in 2024 specifically to resist quantum computer attacks.

Millisecond ledger timing (CAP-88): Stellar’s ledger currently records when a block closes only to the nearest second. Bell adds a millisecond clock instead.

Stellar Core version 30.0.0, the software behind all three changes, became available on October 16. Wallets, exchanges, and software development kits are supposed to update before the votes happen, not after.

The Problem With One Contract Per Customer

Business use of Stellar smart accounts ran into a wall nobody wrote much about until Bell. A smart account holding customer funds has no built-in way to tell one customer’s incoming payment from another’s. The workaround developers used was spinning up a separate contract for every customer.

Jake Urban, a senior engineering manager at the Stellar Development Foundation, put the limit plainly in the foundation’s announcement: that approach “works for ten customers. It doesn’t work for a million.” He also described the new W address format as “an upside-down M,” a small detail that shows how deliberately the foundation designed it to stay recognizable at a glance.

With muxed contract addresses, one contract tracks a 64-bit ID attached to every incoming payment. A payroll app, a subscription service, or a loyalty program can serve many customers from a single contract instead of deploying thousands of near-identical ones. Wallets and block explorers will need updated code to recognize W addresses once Bell activates, and developers must add that address type to their own validation logic.

Why Stellar Is Moving on Quantum Now

Stellar accounts currently sign transactions with elliptic-curve cryptography, the same family of math that secures most of today’s blockchains. A sufficiently powerful quantum computer could, in theory, break those signatures someday. Nobody has built one yet. But migrating an entire live network’s cryptography takes years, and the foundation wants a head start.

CAP-87 is the first onchain piece of what Stellar calls its Quantum Preparedness Plan. It lets a smart contract verify an ML-DSA signature directly inside Stellar Core instead of running the check in contract code. The foundation says that keeps the computation cheap, since it only has to be built once, centrally, rather than inside every contract that wants it.

Does Bell make Stellar quantum-safe? No. The foundation answers that question directly in its own FAQ. Classic account signatures, the ones that move XLM and authorize everyday transactions, stay on Ed25519 for now. A native post-quantum signer for regular accounts is planned as a separate, later protocol change. Bell only opens the door for smart contracts that choose to check post-quantum signatures themselves.

“Dates are subject to change.”
— Stellar Development Foundation, Bell (Protocol 30) announcement

Stellar isn’t the only chain racing that clock. Zcash is targeting its own post-quantum signature work for January, on a completely separate protocol track. Neither chain has flipped the switch yet, and both are treating the transition as a multi-year project rather than a single upgrade.

Who Benefits and How

Bell’s biggest winners, at least at first, are businesses running payment infrastructure on Stellar rather than everyday XLM holders.

  • A business accepting Stellar-based payments at scale, picture a nonprofit running a microdonation platform with thousands of small monthly donors as an illustrative example and not a real organization, could track every donor’s gift through one smart contract instead of deploying a new contract per supporter. That saves the engineering time and ongoing cost of managing thousands of duplicate contracts.
  • Wallet providers and exchanges get a security head start on the quantum problem, even though it won’t protect ordinary transfers yet.
  • Everyday Stellar users see no immediate change. Sending or receiving XLM looks the same once Bell activates, and nobody needs to do anything with their own account.
  • Developers running raw ledger decoders, outside an official SDK, have real work ahead. The ledger header format changes under CAP-88, so outdated decoders will stop working.

None of this ships for free in engineering time. Wallets, SDKs, and exchanges all need updated code before the mainnet vote, whether or not they ever touch the new smart account features themselves.

What’s Not Decided Yet

  • The foundation’s own roadmap calls the whole schedule “proposed” and warns that dates are subject to change.
  • Neither the Stellar Development Foundation’s blog nor independent coverage from October confirms whether the November 3 testnet vote actually passed.
  • No mainnet activation date exists yet. One only gets set if validators approve Bell on November 23.
  • The ledger’s existing closeTime field keeps reporting whole seconds even after CAP-88 adds millisecond precision elsewhere in the ledger.

Stellar’s last major upgrade, Protocol 28, nicknamed Adapter, trimmed mainnet ledger close times from about 5.7 seconds to 5 seconds this September. Bell doesn’t promise a repeat of that speedup on its own. It just clears a technical floor, the one-second ledger timer, that would otherwise block a future speed upgrade from going below one second per ledger. The real test lands November 23. If validators approve Bell, Stellar gets its first working post-quantum building block and a smart account design meant to survive contact with a million customers instead of ten. If they don’t, the foundation goes back to the CAP process and tries again.

Sources

Related Reading