Repository navigation
QDAY v0.7.1: The Mempool Has Object Permanence
A node that arrived after a transaction was first broadcast could sync the chain and completely miss the existing mempool.
The transaction was alive. The node was just born too late. Very philosophical. Bad networking.
What changed
- New and restarted peers receive the current mempool after they sync.
- Mempool changes are offered again while peers remain connected, including required unconfirmed parents.
- Sends, burns and PQ Day proofs all use the same path.
- Existing validation and duplicate suppression remain unchanged.
Compatibility
Same mainnet. Same genesis. Same consensus. Same wallet and chain data. No resync.