Qogecoin · P2QPK

Active

Qogecoin mainnet now enforces post-quantum signatures.

P2QPK activated on mainnet at block 2,459,520. Qogecoin supports SLH-DSA (FIPS 205) — a stateless hash-based signature scheme whose security rests on the strength of its hash function rather than on factoring or discrete logarithms, and so is not broken by Shor's algorithm. As a soft fork, the rules are enforced by upgraded nodes; nodes still running pre-fork software do not validate P2QPK spends.

Upgrade required P2QPK is only enforced by nodes running the soft-fork release. A pre-fork node will not recognise the deployment and will not validate spends from P2QPK outputs, so it cannot give you the post-quantum guarantee even though the rest of the network is enforcing it. Upgrade before relying on P2QPK for custody, and before mining.

Deployment state

1. DEFINED Parameters committed to consensus
2. STARTED Miners signal on bit 3
3. LOCKED_IN Threshold met, one window to upgrade
4. ACTIVE Enforced by upgraded nodes

P2QPK is live

enforced by upgraded nodes since block 2,459,520

Stratum stratum+tcp://postquantum.qoge.org:3032

Copy

−o stratum+tcp://postquantum.qoge.org:3032 −u <your qoge address>.<worker> −p x

Signature scheme

SLH-DSAFIPS 205, hash-based

Activated at

2459520block height

Chain height

—live from node

Deployment

BIP9version bit 3, soft fork

Lock-in window

8064one retarget period

The deployment completed the full BIP9 lifecycle on mainnet: signalled on version bit 3, locked in at block 2,451,456, and activated one retarget period later at block 2,459,520. Because this is a soft fork, the new rules bind the network through the upgraded majority rather than through every node individually — a pre-fork node follows the same chain but does not itself check P2QPK spends.

check on your own P2QPK node to confirm activation status:

~/qogecoin/src/qogecoin-cli getdeploymentinfo

If p2qpk is absent from that output, the node predates the soft fork and is not enforcing it.