Q-BitX Core 0.3.0 — hardfork updateIn 0.3.0 we implemented a major network upgrade, made Q-BitX more resilient as a PoW network, and brought the transaction layer to proper operation with Dilithium signatures.
Q-BitX uses post-quantum signatures. They are larger and heavier than classical ECDSA signatures, so the network cannot live forever on the old legacy model without separate logic for weight, sigops, and witness data accounting.
1. The main change in 0.3.0 — addition of PQ Witness.Before witness activation, the Dilithium signature is located in the legacy part of the transaction. For post-quantum cryptography this is a heavy format: signatures are large, transactions grow quickly, and the number of transactions per block remains limited.
PQ Witness moves heavy Dilithium data into the witness part of the transaction and enables a separate weight accounting model for PQ witness.
After activation, the coefficient is used:
K=16
Practical effect:
right now, approximately 50 heavy PQ transactions fit into a block roughly every 2.5 minutes.
After PQ Witness activation at height 230,000, the expected capacity increases to roughly 600–700 PQ transactions per block.
That means in 10 minutes this is roughly 2500–3000 transactions instead of about 200.
At the same time, PQ Witness does not disable legacy.
Legacy PQ addresses remain valid.
Old coins remain spendable.
Old exchange deposit addresses continue to work.
There is no swap.
There is no forced migration.
There is no coin freeze.
PQ Witness activation: block 230,000.
2. PQ SigopsPreviously, the legacy logic did not provide a full model for separately accounting PQ load. In 0.3.0, separate PQ sigops accounting was added so the network understands how many actually heavy post-quantum operations are present in transactions and blocks.
What changes:
Dilithium signature checks are counted separately;
the mempool starts accounting PQ load more correctly;
block validation gets a more honest cost model for PQ operations;
the risk of spam with heavy PQ scripts is reduced;
when crossing the activation height, the mempool is cleared of old assumptions about sigops/weight.
This is an important part of the hardfork, because witness without proper sigops accounting would be an incomplete solution. It is necessary not only to move signatures into witness, but also to correctly account for the cost of verifying them.
PQ Sigops activation: block 230,000.
PQ Sigops activates together with PQ Witness so that the transaction layer, weight accounting, and signature-operation accounting move to the new model at the same time.
3. LWMA Difficulty AdjustmentThe old EDA difficulty mechanism reacts more slowly.
LWMA was added so difficulty can react faster to real changes in hashrate.
What LWMA provides:
faster reaction to hashrate growth or decline;
lower risk of long block stalls;
more stable block time;
more predictable network operation for miners;
better resilience to sudden hashrate entries/exits.
Parameters:
LWMA activation: block 200,001
LWMA window: 18 blocks
4. wQBX on Base and bridgeAs part of the ecosystem update, we also added wQBX on Base.
wQBX is the wrapped version of QBX on the Base EVM network. It is needed so that QBX can be used outside the main Q-BitX network: in EVM infrastructure, DeFi, liquidity pools, wallets, and other services that work with ERC-20 tokens.
Contract address on Base:
0x9beEe07a920ac571b33a1cc8B2A4395b724dA110
A technical bridge interface for wrapping and unwrapping between native QBX and wQBX is available on the official project website.
https://exchange.qbitx.orgWe ask all miners and QBX holders to update their binaries
https://github.com/q-bitx/Source-/releases/tag/v0.3.0
Other improvements:
Pool ranking and total hashrate
https://pools.qbitx.org
