# Stellar’s Protocol 30 Guide Flags SDK and Ledger Decoder Changes

Published 2026-10-20 · Crypto.world Team · Crypto.world

> The Stellar Development Foundation published a Protocol 30 upgrade guide on October 20, setting out required SDK and XDR updates before planned November votes. Bell adds muxed contract addresses, millisecond-resolution ledger timing and ML-DSA verification for Soroban contracts.

Stellar’s Protocol 30 upgrade is described as additive at the transaction level, but the [Stellar Development Foundation](https://stellar.org/blog/developers/bell-protocol-30-upgrade-guide)’s new preparation guide warns that SDK users and raw-ledger data consumers still need to make changes before the planned network votes. The distinction matters: applications are not expected to face transaction-level incompatibility, yet outdated software may fail to parse new ledger data or recognize a new contract-address format.

The guide, published October 20, sets November 3 at 1700 UTC for a Testnet upgrade vote and November 23 at 1700 UTC for Mainnet. Stellar Core v30.0.0 became available October 16, with further infrastructure and SDK releases scheduled to roll out through October 23. The votes are not guarantees of activation; the Foundation says the upgrade takes effect if validators approve it.

## “Not optional” for SDK users

Stellar makes the software upgrade requirement explicit: “The SDK upgrade is not optional this cycle.” The Foundation says older SDKs may fail to decode Protocol 30 ledgers because CAP-88 changes the ledger-header format. Updated SDKs also carry revised XDR definitions and support for the new muxed contract address type.

Teams using Stellar on Testnet are told to upgrade before November 3, while Mainnet integrations should be ready before November 23. The guide also urges applications to update their own address checks: an SDK can parse the new W-format address, but wallets, exchanges and other products must decide how to validate, display, store and route it.

## W addresses bring multiplexing to contracts

CAP-84 introduces muxed contract addresses: a contract ID paired with a 64-bit multiplexing ID and represented by a new strkey prefix, W. The format lets a contract receive transfers tagged with an identifier, so an application can distinguish customers without deploying a separate contract for each one. Transfer and mint events carry the identifier in the existing `to_muxed_id` field.

The new type has limits developers must account for. A muxed contract address cannot be used as a contract storage key, and a function that accepts a plain `Address` rejects it; a function using `MuxedAddress` accepts both forms. The Foundation says existing Soroban contracts continue working, while teams choosing to use the new address feature need to rebuild and adjust their interfaces.

## Millisecond timestamps change the data contract

CAP-88 adds millisecond-resolution close-time types to Stellar’s ledger data. From the first ledger after an approved upgrade, the older whole-second value types will no longer be produced. Indexers, explorers, analytics systems and custom tools that decode ledger headers, close metadata or SCP history must update to Protocol 30 XDR definitions or risk failing on unfamiliar data structures.

The change does not alter the existing whole-second `closeTime` field or the whole-second semantics of transaction time bounds and Soroban’s `ledger_timestamp`. It does mean consecutive ledgers may close within the same second, so one ledger later no longer necessarily means at least one second later. The millisecond clock enables future work toward faster close times; Protocol 30 itself does not make Stellar produce blocks faster.

## ML-DSA stays inside smart contracts

The third change, CAP-87, adds three Soroban host functions for verifying ML-DSA signatures, a post-quantum signature standard: `verify_sig_ml_dsa_44`, `verify_sig_ml_dsa_65` and `verify_sig_ml_dsa_87`. Contract developers can use them for authorization designs such as custom accounts, but the feature is not a network-wide switch to post-quantum signatures. Stellar’s network-level transaction signatures remain Ed25519.

For operators, the immediate work is more prosaic: install the Protocol 30 versions of Stellar Core, Horizon, RPC and Galexie, and update decoders that consume raw ledger data. Validators are directed to install Stellar Core v30.0.0 ahead of the Mainnet vote. The guide places that vote on November 23, 2026, at 1700 UTC.

## Sources

1. Original source · Blog post [Stellar Development Foundation · Bell protocol upgrade guide](https://stellar.org/blog/developers/bell-protocol-30-upgrade-guide) stellar.org

Other pages read

2. [Stellar Development Foundation · Introducing bell protocol on Stellar](https://stellar.org/blog/developers/introducing-bell-protocol-30-on-stellar) stellar.org
3. [GitHub — stellar/stellar-core](https://github.com/stellar/stellar-core/releases) github.com

## Related stories

- [OpenZeppelin Releases Confidential Token Contracts for Stellar](https://crypto.world/news/openzeppelin-confidential-token-contracts-stellar-v0-8)
- [Stellar’s Project Thruput Hits 7.02M Payments Per Second in Test](https://crypto.world/news/stellar-project-thruput-7-million-payments-per-second)
- [MetaMask Adds Stellar as a Default Network](https://crypto.world/news/metamask-adds-stellar-default-network)
- [Janus Henderson and Centrifuge Launch Nasdaq-100 Fund on Stellar](https://crypto.world/news/janus-henderson-centrifuge-nasdaq-100-fund-stellar)
- [Curve Brings StableSwap to Stellar in Its First Non-EVM Deployment](https://crypto.world/news/curve-stableswap-stellar-first-non-evm-deployment)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/stellar-protocol-30-upgrade-guide-sdk-xdr-changes
