Stellar Bell Upgrade Targets Business Smart Accounts Ahead of November Vote

What the Stellar Bell upgrade would change

The Stellar Bell upgrade is taking aim at a practical problem for blockchain businesses: managing large numbers of customers without making account infrastructure unnecessarily complicated.

Known as Protocol 30, Bell combines three proposed changes. They address customer identification within smart accounts, verification of post-quantum signatures and more precise ledger timestamps. The Stellar Development Foundation describes the upgrade as preparation for business use at scale, alongside longer-term security and performance improvements.

For a payment provider or custodian, the important question is what those changes make possible in day-to-day operations. Can incoming payments be assigned reliably? Can spending permissions match a company’s internal controls? Can existing software keep working through the transition?

Those questions give Bell a more useful frame than treating it simply as another upgrade announcement.

One smart contract, multiple customer addresses

A central proposal, CAP-84, extends Stellar’s multiplexed-address approach to smart contracts. It would allow a contract address to carry an additional customer identifier, using a new address format beginning with W. Funds would reach the underlying contract, while transfer information would identify the intended customer.

Consider a hypothetical payment company serving thousands of customers. Its accounting system needs to distinguish one customer’s deposit from another’s, even when the business manages funds through shared infrastructure.

Giving each payment a clear destination identifier can simplify that reconciliation process. It does not remove the company’s responsibility to maintain accurate records, protect funds or resolve customer disputes.

Smart accounts also create room for spending rules that go beyond possession of a single private key. The broader design questions—permissions, limits and delegated actions are explored in Bitnxt’s guide to how programmable and autonomous crypto wallets work.

Quantum-safe verification comes with an important limit

Bell’s CAP-87 proposal would let smart contracts verify ML-DSA signatures, a post-quantum digital-signature standard. The proposal places verification within Stellar’s host environment, rather than requiring each contract developer to implement the underlying cryptography independently.

That could give developers a building block for custom account security. However, it is not a network-wide migration: Stellar’s ordinary transaction signatures would remain Ed25519, with native post-quantum signing for classic accounts left to a future protocol change.

For users, the distinction matters. Support for a verification method does not mean every wallet has adopted it, every signing device supports it or every account needs immediate action.

A useful question for wallet providers would be how any future implementation handles recovery, compatibility and user mistakes. Bitnxt’s coverage of Vitalik Buterin’s warning against rushed wallet migrations examines that wider migration problem.

A more precise clock does not mean instant faster settlement

CAP-88 concerns the way ledger closing times are represented. Introducing millisecond precision would remove a technical constraint on future reductions in ledger intervals. It would not, by itself, establish that Stellar is moving to millisecond settlement when Bell activates.

That is a meaningful difference for businesses evaluating infrastructure. Timestamp precision, transaction confirmation and completion of a financial transaction are related concepts, but each answers a different operational question.

For example, a fast blockchain transfer may still sit inside a larger process involving compliance checks, currency conversion or a bank payout. Readers can explore that distinction through Bitnxt’s explanation of atomic settlement and blockchain trading infrastructure.

Where the PwC report fits—and why its date matters

The PwC document appearing alongside the Bell discussion is titled Enhancing the Social Handprint of Financial Service Providers: Using Blockchain to Foster Financial Inclusion. Its cover dates it to September 2023. Stellar also referenced the work in its Q3 2023 review.

The report identifies priorities including products that address access barriers, cooperation with traditional financial institutions, engagement with governments and better public understanding of blockchain. Its emphasis is on whether financial services deliver useful outcomes for people.

That makes it relevant background for Bell. It does not establish that PwC helped design Protocol 30, announced a new Stellar product or endorsed this particular upgrade.

The connection is analytical: improvements to business infrastructure may help providers build usable services, while financial inclusion depends on what those providers actually deliver.

The dates businesses should watch

Stellar’s upgrade guide, last updated October 20, sets out the following preparation schedule:

These are upgrade-vote dates, subject to the rollout process. Operators should follow subsequent coordination updates. Bell, Protocol 30 Upgrade Guide

The preparation work is significant. Stellar says SDK updates are required because the ledger-header format changes. Applications handling addresses must also account for the new W format. Existing smart contracts can continue working, while adopting the new features requires additional integration work.

Bitnxt’s view: judge the services that follow

Bitnxt’s assessment: Bell’s strongest angle is the operational work it could make easier for builders. Clearer payment attribution and more flexible security tools address problems that businesses can evaluate through testing.

The next useful evidence would be working integrations: wallets accepting the new addresses, custodians explaining their security choices and payment companies demonstrating reliable customer reconciliation.

The older PwC report supplies a sensible test for that progress. A technically capable network becomes more valuable to users when services are accessible, understandable and dependable. Successful activation would be one milestone; useful products built on top would be the next.

You might also like: Stablecoin payments for businesses: costs, risks and benefits.