Skip to main content
Hashbeam

Crypto protocols, markets and policy

0dd160

Stellar’s Bell upgrade clears testnet, mainnet vote set for Nov. 23

Stellar’s Bell Protocol 30 upgrade is live on testnet, adding muxed contract addresses and contract-level ML-DSA checks before validators vote on mainnet Nov. 23.

The Hashbeam Desk··3 min read

Stellar’s Bell upgrade clears testnet, mainnet vote set for Nov. 23

Stellar’s Bell upgrade, Protocol 30, is live on testnet after the Nov. 3 validator vote, putting three protocol changes through network use before a scheduled mainnet vote on Nov. 23. CoinMarketCap reported the testnet activation; mainnet adoption still depends on validators approving the upgrade.

The changes are CAP-84, CAP-87 and CAP-88. Together they add customer identifiers to smart contract addresses, let Soroban contracts verify ML-DSA signatures, and change ledger timing to millisecond resolution. The Stellar Development Foundation’s Bell announcement describes them as proposed changes and sets the mainnet vote for Nov. 23 at 17:00 UTC. That date is subject to change.

How does CAP-84 route deposits to different customers?

CAP-84 adds a muxed contract address: a contract address with a 64-bit ID encoded in a new address format beginning with W. When a token is sent to that address, it reaches the contract as before, while the ID is recorded in the transfer event. The receiving application can use that ID to associate the deposit with a customer.

The change gives smart accounts a way to use an omnibus model: one contract can hold funds for multiple customers, rather than requiring a separate contract for each customer. The identifier does not itself establish a customer’s identity or move balances between internal customer accounts; the business application still needs to track and account for those balances.

W is a distinct address type, not a cosmetic change to an existing address. Wallets, exchanges and other applications that validate, display, store or route addresses need to accept it. The SDK can parse the new format, but applications must also update their own address handling.

What does CAP-87 change about signature checks?

CAP-87 adds Soroban host functions for verifying ML-DSA signatures, allowing a smart contract account to require such a signature to authorize spending. Signature verification runs inside Stellar Core rather than in each contract’s own code, according to the foundation.

This is contract-level support, not a change to how the network signs transactions. Stellar’s network transaction signatures remain Ed25519 under Protocol 30; classic accounts do not gain a native post-quantum signer in this upgrade. A contract can choose to require ML-DSA authorization, but the upgrade does not make every Stellar account or transaction post-quantum.

Will CAP-88 immediately make Stellar ledgers faster?

No. CAP-88 changes the ledger header to record close times in milliseconds, removing the protocol’s one-second timing floor and enabling future changes to target shorter intervals. The existing closeTime field still reports whole seconds, and Protocol 30 alone does not guarantee faster ledger closes.

The header-format change has an immediate compatibility consequence: software decoding raw ledger data must use updated XDR definitions or it may fail on the new header. SDK users should update as well. These steps matter before the mainnet vote, because an approved protocol upgrade changes the format that downstream systems must read. Testnet activation provides a chance to exercise the new format before validators decide whether to apply Bell to mainnet.

References