Newsroom
21 October, 2026 / News / AI / Tags: stellar, bell, november, kits, upgrade

Stellar’s Protocol 30, known as Bell, advances quantum-resistant signatures for contracts, new address formats for multi-customer accounts, and millisecond ledger timing, with a mainnet validator vote set for November 23
Stellar is preparing a major network upgrade designated Protocol 30 and commonly called Bell. Validators are scheduled to vote on the changes at noon Eastern Time on November 23, equivalent to 17:00 UTC. If approved, the upgrade will take effect on the mainnet. A preceding testnet vote is planned for November 3 at the same time of day.
The proposal centers on three technical improvements designed to support commercial use of smart contracts and prepare the network for future performance and security needs. These changes are mandatory for node operators, wallet providers, exchanges and software development kits. Participants that do not update risk losing the ability to process new ledger blocks.
One component of Bell enables smart contracts to verify ML-DSA post-quantum signatures. A contract-based account could require such a signature before authorizing a spend. This protection applies specifically to Soroban smart contracts and does not alter the network’s existing transaction signature scheme, which continues to rely on Ed25519. As a result, the upgrade does not render the entire Stellar network post-quantum resistant.
The addition is intended to strengthen security for contract-controlled accounts without raising transaction costs. It forms part of broader efforts to position the network for institutional and real-world asset applications that demand stronger cryptographic guarantees.
Another change introduces W-format contract addresses that incorporate a 64-bit identifier. This format allows a single smart contract to receive and distinguish payments intended for multiple customers. Banks, exchanges and custodial services can therefore manage large numbers of client balances through one contract rather than creating individual wallets for each user.
The multiplexing capability is expected to simplify custody operations and lower administrative overhead for fintech platforms integrating with Stellar. Developers and operators have been advised to update their software development kits in advance so that applications can correctly interpret the new address structure.
Bell also records ledger close times with millisecond precision instead of whole seconds. The change does not alter the current five-second target for ledger closure. It establishes the technical foundation for potential later reductions in settlement time, including sub-second finality if the network later decides to pursue that direction.
Stable versions of core infrastructure and software development kits began rolling out between October 16 and October 23. Network participants are expected to adopt these releases ahead of the November votes.
The upgrade is structured as a required transition. Validators, nodes, wallets and exchanges that fail to implement Protocol 30 by the mainnet activation date will be unable to read subsequent ledgers. This unified approach is designed to prevent network fragmentation or unofficial forks.
Individual holders of Stellar’s native token, XLM, are not required to take any action. Existing balances remain unaffected, and the process is intended to proceed without asset migration or manual conversion. XLM continues to serve as the unit for paying network transaction fees.
The combined technical adjustments aim to remove barriers that have limited commercial adoption of smart accounts on the network. By improving support for custodial multiplexing, strengthening contract-level cryptography and refining timing infrastructure, the upgrade seeks to make Stellar more suitable for fintech platforms, cross-border payment systems and real-world asset tokenization use cases.
The Stellar Development Foundation oversees protocol development and the governance process that will determine whether Protocol 30 advances. The November 3 testnet vote will provide an early indication of validator support before the decisive mainnet ballot on November 23.









