Reporting: sourced factual coverage reviewed by the editorial desk.
The Stellar Development Foundation published its Bell upgrade guide on October 20, setting out software changes ahead of proposed Protocol 30 votes on testnet on November 3 and mainnet on November 23. Both votes are scheduled for 17:00 UTC. These are planned governance events, not confirmation that the upgrade has already activated.
The immediate consequence is preparation for the businesses handling readers’ payments. The guide tells wallets, exchanges, custodians, issuers and other operators to update their software before the relevant vote. Stellar Core v30.0.0 was released October 16, while other infrastructure and SDK releases are scheduled across October 16–23.
An SDK update alone does not complete every integration. Bell adds muxed contract addresses with a W prefix. Applications that validate, display, store or route addresses need to support that form in their own code, including transfer destinations. Exchanges and custodians are advised to prepare withdrawal support. For a reader, that means checking the receiving service’s support before relying on a new address format.
Raw-ledger readers face a separate compatibility change. Bell introduces millisecond-resolution close-time types in ledger data. Indexers, explorers and custom decoders need updated definitions; the foundation warns older definitions will fail to decode the new types. Existing whole-second time fields retain their stated semantics, but consecutive ledgers could share a whole-second timestamp.
The cryptography change also has a defined boundary. Protocol 30 adds ML-DSA signature-verification functions for Soroban smart contracts, enabling developers to build such verification into custom accounts and other contract logic. It does not replace network-level transaction signatures: those remain Ed25519. Calling the entire network quantum-safe would go beyond the guide.
The foundation says existing smart contracts continue to work. New features require adoption through compatible tooling and application changes. An announced capability therefore should not be confused with every wallet having deployed it.
RailsRecord’s assessment: the most useful near-term signal is operator readiness, not a token-price narrative. The guide gives payment businesses concrete work and dates against which that readiness can be checked. Whether the votes pass, the upgrade activates as scheduled and integrations work in practice remain matters for subsequent verification.
Illustration: Original AI-generated conceptual artwork created for this headline. It represents software preparation and future upgrade decisions; it is not a photograph or evidence of an activated upgrade.
Sources & evidence
Stellar Development Foundation — Bell Protocol 30 upgrade guide, October 20 ↗
Visual: original AI-generated conceptual illustration, created for this headline. It does not document an actual event.
Author disclosure
AI assisted review and drafting from the Stellar Development Foundation's dated official upgrade guide, discovered through its official @StellarOrg post and corroborated on stellar.org. No interviews, independent integration tests or validator vote verification were conducted. RailsRecord is a Joaico publication; relevant publisher holdings have not been established. Original AI conceptual illustration.
Corrections
Identify this article and the disputed claim in a correction request to corrections@railsrecord.com ↗. The publisher reviews supporting primary evidence.
Reader discussion
Comment on this article or reply to another reader. Comments and replies are held for review before appearing publicly.
Loading discussion…