BLQ Node v0.1.4

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

BLQ Node v0.1.3

BLQ Node v0.1.3

BLQ Node v0.1.3 improves pending-transaction accuracy, public mining responsiveness, and historical data resilience across independent nodes.

Pending Transaction Reconciliation

Nodes now reconcile their local mempool against their own canonical sender nonces before returning pending transactions and during normal mempool persistence.

A transaction that has already been included in a canonical block will no longer remain incorrectly visible as pending after a node catches up or imports blocks.

Mining And RPC Responsiveness

• Public mining template and block-submission capacity remain isolated from ordinary read traffic.
• Template caches are invalidated after accepted, stale, duplicate, or tip-changing submissions.
• Bounded canonical maintenance work keeps block verification and post-block cleanup from unnecessarily holding the immediate RPC/template path.
• Node 39 remains the public mining upstream; nodes 43 and 201 remain independent read, relay, and validation nodes.

Explorer Data Resilience

This release improves the data path behind explorer.blq-chain.online and creates a reusable foundation for independent community explorers.

Nodes now advertise safe explorer and archive capabilities to authenticated peers.

• Archive nodes index and share canonical historical data by default.
• Operators can opt out of sharing or indexing.
• Pruned nodes can forward bounded, read-only historical lookups to verified archive peers.
• Historical block and transaction retrieval prefers compatible archive/share peers before configured fallback routes.
• Explorer sharing never relays writes, mining, admin requests, arbitrary URLs, credentials, or private peer data.

Node 43 now serves as an archive/share provider for canonical historical reads. This improves the resilience of explorer data if node 39 is unavailable.

Any community-operated explorer can independently index BLQ’s canonical chain data and use compatible archive/share providers for bounded historical reads. The current public explorer UI and primary index remain separate services; multi-provider explorer indexing is future work.

Verification

• Native BLQ-RX/2 builds passed on Ubuntu and Windows.
• Formatting, native RandomX checks, and full workspace tests passed in GitHub Actions.
• The deployed artifact was rolled out in order: node 201, node 43, then node 39.
• Nodes 39, 43, and 201 converged on the same canonical height, tip, state root, receipts root, and zero active pending transactions after deployment.

Checksums

• Ubuntu: 8d4045df6fa5cc993785cefa11f477dd0cd3c935ed9ffb1d944a5bdf51aeedef
• Windows: c52291be345963a6f442070bd17ba0d9d2660ed46544ba211662858f5fc61391

BLQ Node v0.1.2

Recovery synchronization

v0.1.2 prevents concurrent moving-tip recovery providers from racing a node's durable recovery cursor. A node keeps one active ordered range provider, while authenticated compatible peers remain bounded witness and failover candidates.

Verified builds

• Ubuntu native build and workspace tests passed.
• Windows native build and workspace tests passed.

Assets

• blq-node-ubuntu-latest-a8440c5fd689cdf49556ebde5ccf9eeff75d1971.zip
  SHA-256: a84eab487c8919fec0e4b10adc08f95e421594fcf16d35a55ef6fd6ff7f93b79
• blq-node-windows-latest-a8440c5fd689cdf49556ebde5ccf9eeff75d1971.zip
  SHA-256: d479d5c34ad9ca73d67378f8382d3c4a8751c71caa5c53e51feea4af18d735a9

BLQ Node v0.1.1

Native node binaries

This release provides verified native BLQ node builds for Linux and Windows. It keeps the active BLQ-RX/2 consensus profile unchanged and fixes RandomX cache handling for the upstream compatibility example vector.

Verification

• Chain ID: 707070
• Genesis: 79a7f512edc606d2ef444382099b870edc0c4e78b82b8a3d81d758254e49d352
• Proof of Work: BLQ-RX/2
• Ubuntu native artifact SHA-256: 0760e392dae2892bd7a2c409bb865f36ed79ab40f9842b0bd401c5a69577a504
• Windows native artifact SHA-256: e8cb0419c750b4ff4a88572d937effa68236408fd342c327378c68433af6c599

The tagged source and native build workflow passed on Ubuntu and Windows.

Run

Verify the downloaded artifact checksum before use, then follow the repository README. The public node configuration keeps mining disabled by default and bootstraps only through the documented authenticated P2P seed endpoints.

This release is not an independent security audit.