BLQ v0.1.4
Canonical-gossip recovery update
This update fixes a moving-tip recovery edge case.
A recovering node could receive its first missing canonical block through normal authenticated P2P gossip, but its durable recovery cursor could still request that already committed height again. v0.1.4 records the verified canonical root, advances recovery across the local prefix, and resumes from the next genuinely missing block.
Timed-out bounded recovery connections now also end cleanly. The verified recovery cursor and spool remain available for the next authenticated provider instead of retaining a dead connection.
What changed
- Advances durable forward recovery after canonical P2P gossip.
- Avoids re-requesting blocks that are already committed locally.
- Reconnects timed-out recovery transports cleanly.
- Preserves bounded recovery ranges and durable resume behavior.
- Adds regression coverage for canonical-gossip recovery.
Compatibility
This is a node synchronization update only.
- No chain reset or database migration is required.
- Chain ID, genesis hash, and BLQ-RX/2 are unchanged.
- Transaction validation, block validation, mining rules, issuance, and canonical fork choice are unchanged.
- Existing node configuration and chain data remain compatible.
Validation
- Rust formatting, workspace checks, and workspace tests passed.
- Public RPC gateway tests passed.
- Native BLQ-RX/2 builds passed on GitHub Actions for Windows and Ubuntu.
- The production rollout converged across all three nodes on a fresh live canonical block.
Assets
-
Ubuntu native build
sha256:b8e03935467b0b6ca1c80c68c96e5cd96703e963aa2ad41692a8dca21cc56c96 -
Windows native build
sha256:774133990269b38b3e8f449c9e5b15fc316015ce118a8151ba858c3bd2c3926f