Stellar has activated its Protocol 30 upgrade, codenamed Bell, on testnet, introducing new smart contract capabilities, post-quantum signature verification and changes that could allow faster ledger processing in future upgrades.
<div id="cn-block-summary-block_24591eccc1c8a85e801b9bca67b97a9f" class="cn-block-summary">
 <div class="cn-block-summary__nav tabs">Summary
 </div>
 <div class="cn-block-summary__content">
 <ul>
 <li>Stellar has activated its Protocol 30 Bell upgrade on testnet, with validators scheduled to vote on mainnet activation on November 23 at 17:00 UTC.</li>
 <li>Bell introduces muxed contract addresses that allow exchanges, custodians and payment providers to manage multiple customer balances through a single smart contract.</li>
 <li>The upgrade adds support for post quantum ML DSA signature verification within smart contracts, while network transaction signatures will continue using Ed25519.</li>
 <li>Protocol 30 introduces millisecond ledger timing to support faster processing in future upgrades, although the change does not immediately reduce ledger closing times.</li>
 <li>Wallet providers, exchanges and infrastructure operators must update their software to support the new address format and ledger data changes before mainnet activation.</li>
 </ul>
 </div>
</div>
According to a November 4 announcement from the Stellar Development Foundation, the testnet upgrade has been completed, with validators now scheduled to vote on activating Bell on the mainnet on November 23.
<figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x">
 <div class="wp-block-embed__wrapper">
 <blockquote class="twitter-tweet">
 Bell is live on Testnet. Reminder: the Mainnet vote is November 23rd 🔔 <a href="https://t.co/ppbYDr7CK6" rel="noopener noreferrer nofollow">https://t.co/ppbYDr7CK6</a>— Stellar (@StellarOrg) <a href="https://x.com/StellarOrg/status/2117698451870032089?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">November 3, 2026</a>
 </blockquote>
 </div>
</figure>
The upgrade introduces three changes under CAP-84, CAP-87 and CAP-88, covering how smart contracts handle customer addresses, verify cryptographic signatures and record ledger closing times.
In its <a href="https://stellar.org/blog/developers/introducing-bell-protocol-30-on-stellar" rel="noopener noreferrer nofollow">October 20 announcement</a>, the foundation explained that Bell is designed to help businesses manage customer funds through smart accounts while preparing the network for quantum-resistant security and faster transaction processing.
The testnet activation followed a validator vote scheduled for November 3 at 17:00 UTC. The mainnet vote is scheduled for the same time on November 23, with activation dependent on validator approval.
<h2 class="wp-block-heading" id="strong-stellar-protocol-30-introduces-muxed-smart-contract-addresses-strong">Stellar Protocol 30 introduces muxed smart contract addresses</h2>
One of Bell’s main changes is CAP-84, which introduces muxed contract addresses that allow businesses to manage funds belonging to multiple customers through a single smart contract.
Previously, Stellar supported muxed accounts that let exchanges and custodians receive deposits from different customers into one account while identifying individual users through separate IDs.
Smart accounts, which use programmable contracts to control spending permissions, did not have the same capability. Businesses using them generally needed separate contracts to distinguish customer balances.
With CAP-84, a contract address can carry a 64-bit identifier that identifies the intended customer without requiring a separate smart contract for every user.
The new addresses use a format beginning with the letter W, distinguishing them from existing muxed account addresses that begin with M.
You might also like: <a href="https://crypto.news/stellar-via-labs-cross-chain-messaging-ethereum/" rel="noopener noreferrer nofollow"> Stellar launches cross-chain messaging with ethereum through VIA Labs </a>
When tokens are transferred to one of these addresses, the funds reach the underlying contract while the customer’s identifier is recorded in the transfer event.
According to Stellar, exchanges, payment providers and custodians can use the system to manage customer deposits through smart accounts without deploying individual contracts for potentially millions of users.
The change requires wallet providers and other applications that process Stellar addresses to support the new format.
<h2 class="wp-block-heading" id="strong-bell-brings-post-quantum-signature-verification-to-smart-contracts-strong">Bell brings post-quantum signature verification to smart contracts</h2>
Another major component, CAP-87, introduces support for verifying ML-DSA signatures within Stellar’s Soroban smart contract environment.
ML-DSA is a post-quantum digital signature algorithm standardized by the US National Institute of Standards and Technology in 2024.
Unlike existing elliptic-curve signature systems, ML-DSA is designed to resist attacks from sufficiently powerful quantum computers.
Stellar currently uses cryptographic signature schemes including Ed25519, secp256k1 and secp256r1, which could become vulnerable to future advances in quantum computing.
Under Bell, developers can create smart accounts that require ML-DSA signatures before authorizing transactions, allowing wallets and custodians to introduce quantum-resistant spending controls.
The foundation said the verification process runs through Stellar Core because checking ML-DSA signatures requires considerably more computing resources than conventional signatures.
Protocol 30 supports three ML-DSA verification functions corresponding to the algorithm’s different security levels.
The feature is the first onchain component of Stellar’s Quantum Preparedness Plan, although network-level transaction signatures will continue using Ed25519 until a future protocol upgrade.
Other blockchains have been exploring similar protections. In August, <a href="https://crypto.news/sui-targets-2027-mainnet-rollout-for-native-quantum-safe-account-authentication/" rel="noopener noreferrer nofollow">Sui outlined plans</a> to introduce quantum-safe account authentication using NIST-approved signature schemes.
<h2 class="wp-block-heading" id="strong-millisecond-ledger-timing-prepares-stellar-for-faster-processing-strong">Millisecond ledger timing prepares Stellar for faster processing</h2>
Bell’s third component, CAP-88, changes how Stellar records the time at which ledgers close.
Currently, Stellar records ledger closing times in whole seconds, which prevents the network from targeting intervals shorter than one second.
The new system introduces millisecond-resolution timestamps, allowing future protocol changes to support more precise ledger closing intervals.
In September, Stellar’s Protocol 28 upgrade reduced typical mainnet ledger closing times from approximately 5.7 seconds to five seconds.
CAP-88 does not immediately reduce those times further. Instead, it removes an existing technical restriction, with Stellar Core developers already experimenting with faster ledger processing.
The change introduces a new ledger header format, requiring applications that decode raw blockchain data to update their software.
According to the foundation’s <a href="https://stellar.org/blog/developers/bell-protocol-30-upgrade-guide" rel="noopener noreferrer nofollow">upgrade guide</a>, older SDKs may fail to decode Protocol 30 ledgers, while indexers and analytics services must update their XDR definitions.
Existing Soroban contracts can continue operating without modification, although developers must update their tools to use Bell’s new features.
<h2 class="wp-block-heading" id="strong-mainnet-upgrade-scheduled-for-november-23-strong">Mainnet upgrade scheduled for November 23</h2>
Ahead of the mainnet vote, Stellar has released Protocol 30-compatible versions of its Core, Horizon, RPC and Galexie infrastructure software.
Its October 23 upgrade guide listed JavaScript SDK v17.3.0 and Go SDK v0.8.0 among the available developer releases, alongside a release candidate for the Soroban Rust SDK.
Validators have been instructed to install Stellar Core v30.0.0 before the mainnet vote, while exchanges, wallet providers and other infrastructure operators must prepare their integrations for the new ledger format.
The upgrade follows recent developments across Stellar’s ecosystem, including <a href="https://crypto.news/stellar-via-labs-cross-chain-messaging-ethereum/" rel="noopener noreferrer nofollow">VIA Labs’ integration</a> of cross-chain messaging between Stellar and Ethereum in late October.
The integration allows Soroban smart contracts to exchange messages with Ethereum-based contracts, supporting applications involving stablecoins, tokenized assets and cross-chain transactions.
Stellar’s mainnet upgrade vote is scheduled for November 23 at 17:00 UTC, with the foundation coordinating preparations through its developer community and validator channels.
Read more: <a href="https://crypto.news/bitmart-confirms-hack-suspects-same-group-behind-mercado-bitcoin-attack/" rel="noopener noreferrer nofollow"> BitMart confirms hack, suspects same group behind Mercado Bitcoin attack </a>

Stellar Protocol 30 Bell upgrade goes live on testnet ahead of mainnet vote

Table of Contents

crypto.news

Other articles published on Nov 4, 2026

Join our free newsletter for daily crypto updates!