Stellar Adds a Post-Quantum Signature Building Block for Smart Contract Accounts

Stellar’s proposed Bell Protocol 30 upgrade includes a step toward post-quantum cryptographic readiness: smart contracts will be able to verify ML-DSA digital signatures through a Soroban host function. The Stellar Development Foundation describes the feature as a building block for contract accounts that want to require quantum-resistant authorization.

Why quantum readiness is being discussed now

Many blockchain systems rely on public-key cryptography based on mathematical problems that are difficult for classical computers. A sufficiently capable quantum computer could threaten some of these systems. No publicly known quantum computer can currently break the cryptography used by major blockchains, but replacing cryptographic systems across wallets, exchanges and infrastructure would take time. That is why standards and migration plans are being explored before an immediate threat exists.

What is ML-DSA?

ML-DSA is a post-quantum digital signature standard finalized by the US National Institute of Standards and Technology. It is based on lattice cryptography and is designed to resist attacks from both classical and quantum computers. It is one of the standards intended to help organizations prepare for future cryptographic changes.

How CAP-87 works

CAP-87 adds verification support inside Stellar Core, exposed to Soroban smart contracts through host functions. This means contract developers can ask the network runtime to verify an ML-DSA signature rather than implementing the cryptographic algorithm themselves in contract code. Centralizing the implementation can improve consistency and allow it to be tested against official test vectors.

What the proposal does not do

Stellar is careful to distinguish contract-level verification from a complete network-wide migration. Network transaction signatures remain Ed25519 for now. CAP-87 does not make every Stellar account quantum-safe automatically, nor does it mean all wallets or applications will immediately adopt ML-DSA. A custom smart account can choose to require the new signature method as part of its own authorization logic.

Potential applications

Wallet providers and custodians could use smart-account policies to require post-quantum signatures for selected operations. Enterprises managing digital assets may value the ability to adopt new authorization methods without waiting for every account type to change at once. The feature could also support experimentation by developers building hybrid authorization schemes.

Costs and engineering trade-offs

Post-quantum signatures can be larger and more computationally expensive than familiar elliptic-curve signatures. This makes implementation details important: verification needs to be reliable, resource usage must be understood, and contracts should be tested for edge cases. Host-function support helps standardize the operation, but application teams still need security reviews and careful key-management procedures.

Conclusion

CAP-87 is a targeted first step, not a declaration that Stellar has completed a quantum-safe transition. By allowing smart contracts to verify ML-DSA signatures, Bell would give developers a new authorization option while leaving network transaction signatures unchanged. Its value will depend on adoption, wallet support and future protocol work.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *