Stellar’s Bell Upgrade Launches on Testnet Ahead of Mainnet Vote

Post‑Quantum Signatures: A New Layer of Security

Stellar’s latest protocol upgrade, dubbed „Bell,” has been activated on the network’s test environment, allowing developers and users to experiment with new features before the mainnet release. The update introduces optional post‑quantum signature verification for smart contracts and requires wallet and indexer software to be refreshed. The testnet rollout began on Monday, with a scheduled mainnet deployment pending community voting.

The Bell upgrade expands Stellar’s cryptographic toolkit by adding support for post‑quantum signatures. Developers can now embed quantum‑resistant checks into their contracts, enhancing security against future quantum computing threats. Wallets and indexer services must update to recognize the new signature format, ensuring compatibility with the upgraded protocol. The Stellar Development Foundation (SDF) has issued a detailed migration guide and encouraged early adoption on the testnet.

What Developers Need to Do – Is a Migration Required?

Stellar’s post‑quantum feature allows smart contracts to verify signatures that are resistant to attacks from quantum computers. This optional capability means that existing contracts remain functional while new ones can opt into quantum‑resistant verification. „We’re giving developers the choice to future‑proof their applications without forcing a hard break,” said a SDF spokesperson. The feature relies on the Dilithium algorithm, which has been vetted by the National Institute of Standards and Technology (NIST) as a candidate for post‑quantum cryptography.

The upgrade also introduces a new transaction type that supports the quantum‑resistant signature scheme. Testnet nodes have reported successful validation of these transactions, and early adopters are already experimenting with contract logic that checks for both classical and post‑quantum signatures. This dual‑signature approach provides a transitional path as the broader ecosystem moves toward quantum‑resistant standards.

How Will the Mainnet Vote Affect the Upgrade?

Developers must update their wallet and indexer software to handle the new signature format. The SDF recommends using the latest Stellar SDK releases, which include libraries for parsing and validating Dilithium signatures. „Updating is straightforward,” the spokesperson added. „You’ll need to pull the new SDK, recompile your code, and run the migration script against your local node.” Contracts that wish to adopt the new feature should include a version flag in their metadata, allowing the network to distinguish between legacy and quantum‑ready code.

Indexers, which track transaction history for explorers and analytics tools, must also adjust their parsing logic. The SDF has released a patch that adds support for the new transaction type, ensuring that explorers will display quantum‑signature transactions correctly. Failure to update could result in missed or incorrectly parsed transactions, potentially affecting user balances and analytics reports.

Frequently Asked Questions

The mainnet deployment of Bell is contingent on a community vote scheduled for next week. Stakeholders will decide whether to adopt the new features, including the optional post‑quantum signatures. If the vote passes, the upgrade will be rolled out network‑wide, and all nodes will need to update their software. A successful vote will also signal Stellar’s commitment to staying ahead of quantum threats, potentially attracting new institutional users concerned about long‑term security.

The SDF has emphasized that the upgrade is designed to be non‑disruptive. Existing contracts will continue to operate as before, while new contracts can opt into the enhanced security layer. This approach mirrors Stellar’s previous upgrades, which have maintained backward compatibility while adding new capabilities.