The Ledger
Pirate Chain’s v6.0.14 Notes Say No Reindex or Consensus Change
Pirate Chain’s v6.0.14 release notes describe header-sync and wallet-bootstrap fixes, not a consensus change. The project says the upgrade requires no reindex for nodes running versions 6.0.10 through 6.0.12.

Pirate Chain’s v6.0.14 release notes describe a drop-in node upgrade, not a consensus change or a required chain reindex. The GitHub release page lists the signed version as published on October 21, while the accompanying notes recommend the update for every node and say it builds on v6.0.10, which they identify as the mandatory security release.
The distinction matters because the notes set narrow expectations for operators: nodes upgrading from versions 6.0.10 through 6.0.12 do not need to reindex or change configuration. The documented work addresses header synchronization, recovery when a node’s tip stops advancing, and wallet cleanup during blockchain bootstrap.
What Pirate Chain says v6.0.14 changes
The notes describe a problem in which a peer could keep a node’s header-sync slot occupied by returning headers for a block the node had already rejected. Version 6.0.14 manages outbound header requests per peer, limits each peer to one in-flight request, retries unanswered requests on a timer and records progress only when a batch is accepted.
The node also keeps a lower-work announced chain as a fallback if a peer’s higher-work chain proves invalid. That change is intended to prevent a discarded branch from blocking downloads of valid blocks announced by another peer, according to the release document.
“This release makes no consensus change and no block-index format change, so no reindex is required over 6.0.10 through 6.0.12 — it is a drop-in upgrade.”
Pirate Chain’s v6.0.14 release notes
A stalled tip triggers another header request
After initial synchronization, a node usually learns of new blocks through peer announcements. The release notes say v6.0.14 detects when a synced node’s tip has failed to advance for several block intervals and asks peers for newer headers instead of waiting indefinitely.
The check stays dormant while the node’s tip is current, the notes say, so the recovery behavior does not add traffic to a healthy, synchronized node. The change targets missed announcements or peers that do not announce blocks to that node.
Bootstrap now clears wallet history before rebuilding
Pirate Chain also fixes a bootstrap option that had left the wallet wipe disabled. The bootstrap process is meant to clear wallet transactions and rebuild them from the downloaded chain; without the wipe, a rescan could leave stale transaction data from the previous chain.
The corrected process clears and rebuilds the wallet, including Sapling and Ironwood shielded state, whether an operator starts the bootstrap from the command line or the graphical interface. The release notes’ instructions are to stop the old node, install v6.0.14 and restart it; no configuration change is required.
6.0.10 remains the named security release
The notes call v6.0.14 “recommended for every node” but distinguish it from the earlier mandatory security release, v6.0.10. They do not describe v6.0.14 as changing consensus rules, altering the block-index format or requiring a reindex for the listed prior versions.
The project’s GitHub releases page lists v6.0.14 as the latest signed release and links to these notes. For operators on 6.0.10 through 6.0.12, the published upgrade path is a stop, install and restart—not a chain rebuild.
Sources
- Original source · Release notes Pirate Chain on GitHub · Release notes 6.0.14 github.com
Other pages read
- Pirate Chain on GitHub · page 2 github.com
Related stories
- Pirate Chain Rewinds to Block 4,176,944 After 39.82M ARRR Mint
- BitcoinZ Rewinds Its Chain After a Block Mints 105 Billion BTCZ
- Zebra 7.1.0 fixes ten Zcash node security advisories
- Bitcoin Core Releases 31.2 With a 10,000-Entry Queue Limit
- Arkadiko Governance Attack Drains Vault Collateral, Knocks USDA Off Peg