Skip to content

BLQ Node v0.1.3

Choose a tag to compare

View all tags
@blq-chain blq-chain released this 19 Sep 19:04
· 2 commits to main since this release
v0.1.3
b981798

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
Assets 4
Loading