- Stellar’s next network upgrade, named Bell, is 30. It covers smart account addressing, post-quantum signature verification inside , and finer-grained ledger timing.
- Everything here comes from Stellar’s own developer blog and upgrade guide. We found no independent reporting on the release, so treat the detail as the project’s account of its own work.
- Verifying a post-quantum signature inside a contract is not the same as making the network quantum-resistant. Ordinary XLM accounts are unaffected by that part.
“Post-quantum” has started appearing in headlines roughly once a week, usually attached to a claim that some network is now safe from quantum computers. Stellar’s upgrade is a real example of the genre, and it’s also a good place to see where that claim stops being true.
If you hold XLM, nothing in this upgrade requires you to do anything, and nothing in it changes how your account is secured today. What it’s worth understanding is the gap between what gets announced and what gets delivered, because the same gap will show up in every quantum story you read for the next few years. Knowing where the line sits saves you from both the panic and the reassurance.
What a protocol upgrade actually is
Stellar, like most blockchains, is run by a set of independent computers called . Each one keeps a copy of the ledger and agrees with the others on what the next version of it should say.
A protocol upgrade is a new set of rules for those computers. Developers write it, release the software, and then enough validators have to install it and vote to switch it on at an agreed moment. Until that happens, the upgrade exists as code and a date, not as a live change to the network.
This matters for reading announcements. The blog post describing Bell is a description of what the software will do once adopted. Stellar has published a separate upgrade guide aimed at developers, infrastructure operators and validators, with key dates, release links and a list of breaking changes, which is the normal shape of a release that hasn’t gone live yet.
Why quantum computing is treated as a threat at all
Start with how you own crypto. Every account has a , a very long secret number, and a public key derived from it. The public key is visible to everyone. The private key proves the coins are yours.
The security of that arrangement rests on a mathematical one-way street. Going from the private key to the public key is easy. Going backwards, working out the private key from the public one, would take an ordinary computer longer than the universe has existed.
Quantum computers break the symmetry of that problem. A sufficiently large one running a known algorithm, published by Peter Shor in 1994, could reverse the calculation in a practical amount of time. The maths behind almost every blockchain signature in use, Bitcoin’s and Ethereum’s included, sits in exactly that category.
No such machine exists yet. The ones built so far are nowhere near the scale required, and credible estimates for when that changes range from a decade to never. The reason the industry is moving now is that keys are permanent. Coins sitting untouched for years are protected by signatures chosen today, and nobody wants to be migrating in a hurry.
What “signature verification” means here
A signature is the proof you generate with your private key when you authorise a transaction. Verification is the network’s check that the signature matches the public key it claims to come from.
Post-quantum signature schemes are newer designs built on maths that Shor’s algorithm doesn’t unravel. They tend to produce much larger signatures and cost more to check, which is why nobody has simply swapped them in everywhere.
What Stellar says Bell adds is the ability for smart contracts, programs that run on the network, to verify those newer signatures. A contract can be written that accepts a post-quantum signature as valid authorisation.
That is genuinely useful. It’s also narrower than “Stellar is now quantum-resistant”. The ordinary accounts that hold XLM continue to work the way they always have, with the signature scheme they already use. The upgrade gives developers a building block. It does not retrofit the whole network, and Stellar’s own write-up frames it as a capability for contracts rather than a change to base-layer account security. If a headline tells you a chain has been made quantum-proof, the question to ask is which part: the contracts, or every account on it.
Smart accounts and muxed addresses
The second item is muxed contract addresses. The word is short for multiplexed, and the idea is older than smart contracts.
A muxed address lets one underlying account present many distinct addresses, each carrying an identifier that says which customer or sub-account a payment belongs to. Exchanges have used the equivalent on Stellar for years to avoid giving every user a separate funded account, and to stop relying on a memo field that people routinely forget to fill in.
Bell extends that pattern to contract addresses, which is what makes it relevant to smart accounts, where the rules for authorising a transaction live in a contract rather than in a single fixed key. A contract that can distinguish between the parties behind it is easier to build custody and wallet products on. This is plumbing for developers, not something a holder interacts with.
What millisecond ledger timing does and doesn’t change
Stellar closes ledgers at a fixed cadence, roughly every five seconds, and a payment is final when the ledger containing it closes. Finer-grained timing means the network can reason about time in smaller units than a whole ledger.
For someone sending XLM to a friend or an exchange, that is unlikely to feel like anything. Your transfer still waits for a ledger to close, and five seconds was never the part anyone complained about.
Where it counts is in contracts that depend on precise timing: auctions, , anything where a few hundred milliseconds decides an outcome. pricing is one of them, and Chainlink’s price feeds went live on Stellar mainnet recently, which is the kind of application that cares about how precisely a contract can measure elapsed time. Fast settlement is a claim worth separating from fast confirmation. Nothing here shortens the wait for a payment to be considered done.
What you need to do
If you hold XLM on an exchange, nothing. The exchange handles the upgrade, and the work falls on its infrastructure team rather than on you. If you use a maintained wallet, nothing, beyond accepting updates when they arrive in the normal way. The XLM price page and our news archive carry our earlier Stellar coverage.
The people with actual work to do are developers, node operators and validators, which is who the upgrade guide is addressed to. Protocol upgrades on established networks are usually uneventful for holders, and the main thing that occasionally goes wrong is an exchange pausing deposits and withdrawals around the switchover. Our self-custody guide covers the general question of where your coins should sit.
What to watch
Whether validators adopt it on schedule. An upgrade is a plan until enough of the network runs it, and the dates in the guide are targets rather than guarantees.
Beyond that, watch how the post-quantum capability gets used. A verification primitive that nobody builds on is a line in a release note. If wallet providers start shipping smart accounts that use it, that’s the point at which it starts to mean something, and it’s also when the gap between contract-level and network-level protection will matter most to the people writing the headlines.