Mandatory Update: Pirate Chain v6.0.14 is Now Available The Pirate Chain team is pleased to announce that our development team has given the all-clear for the community to resume normal activity once the following mandatory update is completed. All users, Treasure Chest and CLI node operators, miners, pools, exchanges, and service operators must suspend operations on previous versions and update to version 6.0.14 (or greater) immediately. Do not continue running any older versions. Download Links: GitHub: github.com/PirateNetwork/pir… Pirate Chain Website: piratechain.com/wallets/#ful… Re-Index & Bootstrap Instructions: Please note that this update will trigger an automatic, one-time full chain re-index on first start, followed by a wallet scan to reconstruct shielded balances. Please be patient and do not interrupt the process, as this can take some time to complete. To speed up recovery: Users can select the built-in “Reindex and Rescan with Bootstrap” option. Version 6.0.14 utilizes a pre-indexed bootstrap to shorten recovery time and handle the wallet rebuild automatically. Incident Summary & Network Consensus: On October 14, an attacker combined two validation flaws to mint approximately 39.82 million counterfeit ARRR in the transparent coinbase pool, temporarily inflating the supply by ~20%. Both flaws have been patched in record time, closing the exploit path that allowed unauthorized coins to be created and spent, and preventing any permanent economic damage to the chain and its users. Through consensus among the community, node operators, pools, exchanges, and dPoW notaries, the chain has been rolled back to block 4,176,944 (October 14 at 19:55:14 UTC), immediately prior to the exploit: • Exploit Rejection: Version 6.0.14 causes nodes to automatically reject the exploit block and all subsequent blocks built on it. • dPoW Notarizations: The dPoW notaries have agreed to resume notarizing this corrected chain. The old branch will receive no further dPoW notarizations. • Supply Integrity: The counterfeit coin issuance has been completely removed, and all transactions and balances return to their pre-exploit state. Pirate Chain's maximum supply remains strictly at 200M ARRR. We also identified and resolved several minor bugs related to the P2P networking layer. All changelogs from release-notes-6.0.10 onwards are available to read here: github.com/PirateNetwork/pir… Our sincere thanks to the community for its patience and composure throughout this incident, and to our development team for its outstanding response under pressure. We also extend our gratitude to all team members, exchanges, pools, and partners who assisted in containing the incident so promptly and successfully. A comprehensive technical postmortem detailing the exploit, the sequence of events, and our response and recovery measures is currently being compiled and will be published in due course.

Its saying no centralized authority has the ability to roll back the chain. There is no switch to be flipped. An update for full nodes will be released and all operators are being asked to update to it. This will effectively roll back the chain since all operators seem to agree to the change. The same way Bitcoin rolled back the chain.

Pirate Chain Import Exploit Update On 14 October 2026, a transaction validation vulnerability in Pirate Chain source code was discovered which allowed the unauthorized creation of approximately 39.8 million ARRR, increasing the supply by approximately 20%. The newly minted funds were immediately transferred into the Sapling shielded pool. NonKYC subsequently identified suspicious deposits and acted quickly to restrict the associated account and prevent withdrawals. Due to the nature of shielded transactions, the full subsequent movement of the funds cannot be traced, but we believe activity related to the unauthorized issuance was otherwise restricted primarily to on-chain transactions. The exploit combined two validation failures bypassing the issuance check and incorrect interpretation of the output scripts. Evidence does not indicate any compromise of notary keys or the cryptography underlying Pirate Chain's shielded transactions. As a voluntary precaution, dPoW operators have collectively agreed to temporarily suspend notarizations, while exchanges and mining pools have been asked to voluntarily pause operations as a recovery plan is developed. Because Pirate Chain is decentralized, it is not possible to freeze the network or unilaterally rollback its blockchain history. Pirate Chain remains operational, but we ask that all users temporarily refrain from sending or moving funds. The Pirate Chain team is currently investigating the event and developing solutions in collaboration with other communities. Further technical details and recovery instructions will be provided in the forthcoming post-mortem.