Stellar Issues Bell Upgrade Guide Ahead of November Votes

The Stellar network has refreshed its Bell upgrade guide, detailing the specific software versions that wallets, exchanges, and infrastructure operators must adopt ahead of the upcoming November network votes. Published on October 23, this update introduces precise release references as development teams ready themselves for ledger data and address modifications tied to Protocol 30.

TL;DR: Stellar’s updated Bell guide identifies software needed before November’s upgrade votes. Applications must handle new addresses and ledger formats; network activation remains conditional.

The revised documentation from the Stellar Development Foundation details required software development kits and infrastructure releases, as well as tracking links for tools maintained by the community. This provides operators with a concrete version checklist that must be completed prior to the network adopting the proposed changes.

New Addresses Need Application Support

The JavaScript SDK v17.3.0, released on October 21, introduces support for updated ledger definitions alongside contract addresses beginning with the letter W. The corresponding release notes feature tools for decoding, encoding, and validating these addresses, as well as handling transfers. This version was accessible immediately prior to the readiness guide’s revision two days later.

Under the Bell upgrade, contract addresses gain the ability to incorporate an additional customer identifier. According to the foundation’s technical briefing, this mechanism allows a single smart contract to accept funds on behalf of multiple users while logging the specific customer tied to each payment, extending functionality previously restricted to classic Stellar accounts.

For custody providers, this capability can streamline a shared account layout. Nevertheless, applications must still be updated to recognize the new address format and correctly link the identifier to the correct user. Simply installing a library that can parse the address does not automatically update all underlying validation and accounting logic.

A separate preparation requirement affects services that read raw ledger data, such as blockchain explorers and indexers. Because Protocol 30 alters the format of the ledger header, the guide cautions that decoders relying on legacy definitions will encounter errors when processing the new values. Consequently, compatibility updates are necessary even for organizations that choose not to implement the new address feature.

Quantum Verification Has A Limited Scope

The Bell upgrade also incorporates support for ML-DSA signature verification directly within smart contracts. While this enables custom accounts to utilize post-quantum authorization, standard network transaction signatures continue to rely on Ed25519. Rather than executing a comprehensive cryptographic migration across the entire network, this update simply provides a foundational component for developers.

Another modification brings millisecond-level ledger timestamps. The foundation notes that this eliminates a technical hurdle for accelerating ledger close times in subsequent phases, though the Bell upgrade by itself does not shorten the current interval. Furthermore, applications should refrain from assuming that successive ledgers will always feature distinct whole-second timestamps.

Certain software tools remain in progress; the documentation marks the Protocol 30 command-line release as pending and the Soroban Rust SDK as a release candidate. Voting for testnet validators is slated for November 3, with the mainnet vote following on November 23, both scheduled for 17:00 UTC. Implementation depends on validator approval, and the foundation has noted that these dates remain subject to change.

Short FAQs

What is the Stellar Bell upgrade guide?

The Bell upgrade guide is an updated resource published by the Stellar Development Foundation that outlines the software versions, SDKs, and infrastructure releases required by operators before November’s network voting.

How do new contract addresses work under Protocol 30?

Contract addresses starting with W can now carry an additional customer identifier. This enables a single smart contract to receive funds for multiple customers while tracking which user a payment belongs to, similar to an arrangement already available for classic Stellar accounts.

Does Bell introduce post-quantum signatures for all transactions?

No. Bell adds support for ML-DSA signature verification inside smart contracts for custom accounts using post-quantum authorization, but ordinary network transactions continue to use Ed25519 signatures.

When are the upgrade votes scheduled to take place?

Testnet validators are scheduled to vote on November 3, and mainnet validators are set to vote on November 23, both at 17:00 UTC. The upgrade will take effect if approved by validators, though the foundation notes these dates are subject to change.