Neutral

Stellar schedules Bell Protocol 30 testnet vote Nov 3, mainnet Nov 23

На русском
3 min

TL;DR: Stellar Development Foundation proposed Bell, the Protocol 30 upgrade: testnet validator vote on November 3, 2026; mainnet validator vote on November 23, 2026. Scope: muxed contract addresses for large-scale account management, support for verifying post-quantum signatures inside smart contracts, and groundwork for faster ledger closes. Developers should monitor the testnet vote, compatibility notes, documentation, and November mainnet vote results.

The October 20, 2026 announcement defines upgrade components and governance milestones. Dates signal intent and coordination points, not immediate feature activation across the network. Bell aggregates three proposals to streamline smart-account operations, enable contract-level verification of post-quantum signatures, and adjust ledger timing mechanics for potential speed gains. It does not introduce a new chain.

What the source establishes

Bell focuses on operational scale and security primitives:

  • Muxed contract addresses: extends muxed-account patterns to contracts. Implication for exchanges, on/off-ramps, and custodians: simpler consolidation of many customer relationships under shared contract logic while retaining per-customer identifiers. Implementation must preserve strict separation of customer records and authorizations.
  • Post-quantum signature verification in contracts: adds the ability to verify PQ signatures within smart contracts. This is a building block, not a network-wide cryptographic migration. Full migration requires alignment across accounts, recovery flows, libraries, and operational procedures.
  • Ledger timing refinements: removes a technical obstacle to faster closes and enables finer-grained intervals. Potential effect: more responsive payments and trading. Constraints: validator coordination, network stability, and the distinction between faster ledger closes and legal settlement of offchain obligations.

Governance timeline: testnet vote on November 3, 2026; mainnet vote on November 23, 2026. These are decision points that can shift schedules based on validator participation and results.

Implications and open questions

  • Infrastructure impact: benefits skew to service operators managing large user bases, not end-user wallet features. Success depends on careful contract patterns and operational controls.
  • Security path: PQ support within contracts enables experimentation and phased adoption. Network-wide quantum resistance remains a multi-layer migration with policy and tooling dependencies.
  • Performance: tighter ledger intervals can improve UX under load if validator coordination remains robust. Predictable throughput and stability will decide enterprise utility more than peak benchmarks.
  • Market interpretation: the announcement defines capabilities and governance steps. Price effects depend on adoption by customers, execution quality, cost-benefit outcomes, and broader market conditions.

What to watch

  • Testnet vote outcome and any compatibility advisories.
  • Upgrade documentation and sample patterns for muxed contract addresses.
  • Benchmarking data on ledger close times and stability under stress.
  • Mainnet vote on November 23 and any date adjustments from governance.
  • Evidence of live usage by exchanges, ramps, and custodians, including how they segregate customer identifiers and authorizations.

Primary source: original company statement (2026-10-20).

Written by the News Desk and edited by Samuel Rae.

Original publication

Authors credited by the source: NewsBTC Editorial Team

Published by Holder based on an external source.