What Protocol 30 adds
Bell introduces three main protocol changes. CAP-0084 adds muxed contract addresses, represented with a new W-address type. CAP-0087 adds host functions that let Soroban contracts verify ML-DSA post-quantum signatures. CAP-0088 records ledger close times with millisecond resolution, creating the protocol base for faster ledgers.
The post-quantum feature is opt-in for smart contracts. Network transaction signatures remain Ed25519, so the upgrade does not make the whole network quantum-safe.
The compatibility risks
The Stellar Development Foundation says the SDK update is not optional this cycle. Protocol 30 changes the ledger-header format. Raw decoders built against older XDR definitions can fail on the new union types immediately after activation.
Applications that validate, display, store or route addresses also need to accept the new W-address variant where appropriate. A newer SDK supplies the parser, but product code must still add the new type to its own checks.
Who should act before the vote
- Validators: install Stellar Core v30.0.0 or the latest compatible release and follow official arming instructions.
- Horizon, RPC and Galexie operators: install Protocol 30 builds.
- Wallets, exchanges, issuers and ramps: update SDKs and address validation; decide how withdrawals to W addresses will work.
- Indexers and analytics teams: update XDR definitions before reading the first Protocol 30 ledger.
- Soroban teams: test timestamp assumptions and adopt new address or ML-DSA features only when needed.
What ordinary users need to know
There is no new Stellar token, claim page or wallet migration. Users should not sign an “upgrade” transaction or reveal a recovery phrase. Any exchange maintenance around the vote should come from that exchange’s official status channel.
What remains unknown
Upgrade votes are subject to change, and the validator arming command is distributed through the usual validator channels. The upgrade guide also lists some SDK releases or tracking issues that may change before mainnet. Teams should use the latest official release notes rather than freeze versions from this article.
What to watch next
- Confirmation that the 23 November vote remains scheduled.
- Final stable SDK releases and exchange-maintenance notices.
- Validator readiness and any testnet issues found after the 3 November vote.
- Post-activation errors involving W addresses or raw ledger decoding.
Sources you can open
01Protocol upgrades do not require ordinary users to move XLM or enter recovery words. Use only official repositories, documentation and exchange status pages.