Pirate Chain

Pirate’s white paper traces the project to a Discord discussion on 29 August 2018. Komodo’s asset-chain tools made it possible to launch a chain that inherited Zcash-style shielded transactions while keeping its own miners, monetary schedule and network.

The launch terms shaped the project’s identity: no premine, founder fee or block tax. Mining distributed ARRR, and no company sale created a contractual class of buyers. That does not prove perfectly even distribution, but it removes a treasury allocation that could be mistaken for holder entitlement.

On transparent chains, privacy depends on who opts in and when. Pirate required ordinary peer-to-peer transfers to pass through its shielded pool. Validators see a proof that the spend is valid without seeing the payment graph that a block explorer would normally expose.

The slogan needs limits. Coinbase outputs and notarization data are protocol artifacts; a careless device or exposed network route can reveal a user; and viewing keys let the wallet owner reveal information. Shielding protects ledger details. It does not turn every surrounding activity into a secret.

Pirate blocks come from Equihash proof-of-work. dPoW periodically anchors a recent state through a notary network and onward to Litecoin. Once notarized, rewriting older history requires defeating more than the local chain. Before the next anchor, recent blocks still face the ordinary security of Pirate’s own hash rate.

Komodo sunset its legacy dPoW in January 2026. Pirate’s Q1 report says ARRR moved to Komodo Classic without losing Litecoin notarizations. This is an external service boundary: the reviewed materials define no ARRR-balance election of notaries, and dPoW is not a backdoor that can move a holder’s shielded coins.

Pirate tested Orchard early in 2026, then the July update recorded a decision to skip it and move directly to Ironwood. The choice avoided shipping one privacy pool only to replace it again, but it also showed why testnet announcements must not be written as completed mainnet history.

By 18 August, signed version 6.0.0 was available. Full-node users were told to update before block 4,141,650 around 19 September, with Ironwood planned for 3 October. On this page’s review date, Sapling remained the live baseline and Ironwood remained scheduled.

Native ARRR travels inside the shielded Pirate chain. Ethereum wARRR and BSC wARRR travel on public account ledgers. The Ethereum wrapper’s verified code has an owner who can change whitelist and fee destinations; live calls also show an owner for the BSC contract. Those permissions belong to wrapper contracts, not the native protocol.

An older official guide described 1:1 bridge backing and a 1% transfer fee. The reviewed current material did not supply an independent reserve attestation. A wrapper holder therefore holds a claim mediated by bridge operations and contract administration, while a native holder controls ARRR under Pirate consensus. Similar names should not blur that difference.