Altcoins
IoTeX opens vote on a post-quantum key for staking
IOTX holders can vote on IIP-65 through November 28. The proposal would add a hash-based key to some native staking positions, with activation dependent on a network upgrade.

Optional protection for native staking
Voting on IIP-65 opened on November 21 at 00:00 UTC on the IoTeX governance portal. It is due to close at the same time on November 28. The proposal from Raullen Chai and Chen Chen would allow the owner of a native staking position to attach an additional security key to it. The option targets IOTX tokens already locked for staking. Voting is underway and activation would depend on a later upgrade.
These positions are currently managed with an ECDSA key, a type of elliptic-curve signature. Under the proposal, holders could use their existing key to install the new key on a specific position. Once protected, withdrawals, transfers, and delegate changes would require a signature from the new key. The position would keep earning rewards and counting toward votes under existing rules.
Larger signatures and a key to keep safe
The proposal chooses SLH-DSA, a family of hash-based signatures standardized by NIST in FIPS 205. The variant selected by the authors produces a 16,224-byte signature. At the minimum gas price used in their estimates, a guarded operation would cost about 1.79 IOTX. Installing a new key as part of such an operation would raise the estimate to about 3.57 IOTX. The design is intended for infrequent operations.
The security key and the account key have separate backups. The proposal allows the security key to be restored from its recovery phrase. If an owner loses both the key and its backup, the position remains locked because the design provides no fallback. The protection must be set up before any compromise of the existing key. Holders who keep their current setup would continue to manage their positions under the same rules as today.
A limited scope ahead of possible activation
The proposal excludes liquid tokens, contract-managed staking, delegates’ own self-stake positions, and positions subject to a delegate endorsement. Reward routing remains an account-level setting. The new key protects funds already locked and the votes of the position to which it is bound. A broader migration of accounts and delegate keys is covered by the separate IIP-64 proposal.
IoTeX’s code repository contains a reference implementation submitted for review. The deployment plan calls for testnet trials and an external audit before activation. Under the proposal, the rules would take effect at a block height set for a future upgrade. The vote that opened on November 21 concerns the proposed mechanism. Its outcome and the technical steps that follow will determine whether and when holders can use it.
