PriFi.info

Pirate Chain

A proof-of-work cryptocurrency built on Komodo and Zcash code that allows only shielded transactions between users, so the sender, receiver and amount of every payment are encrypted.

LivePrivacy coin

As of 23 October 2026 the network ran releases 6.0.10 to 6.0.14, which reject the blocks with the unbacked ARRR created in the exploit found on 14 October; how affected users and exchanges would be treated had not been settled in the sources found.

Market cap
$36.9MDefiLlama, 29 Oct 2026
Launched
Aug 2018
Token
ARRR
Chains
Pirate Chain

Checked on 23 Oct 2026. Information only, not investment advice.

How it works

Pirate Chain is a cryptocurrency with its own blockchain, started in August 2018 as a Komodo asset chain, a runtime fork of Zcash code, with an initial supply of zero. Miners add a block about every minute with Equihash proof-of-work; the reward started at 256 ARRR and halves every 388,885 blocks, about 270 days, towards a supply of about 200 million ARRR. The chain is also protected by Komodo's delayed proof of work (dPoW): Komodo's notary nodes record Pirate's blocks on the Komodo chain, whose state has been notarised to Litecoin since June 2021, so that rewriting Pirate's history would also mean attacking those chains.

Privacy is mandatory. The chain runs with the parameter -ac_private=1, under which no transparent transactions are possible between users: coins move only between shielded addresses, using zk-SNARKs, so the sender, the receiver and the amount of every payment are encrypted on chain, and transparent outputs are restricted by address. Pirate launched with Zcash's Sprout pool and moved to Sapling, disabling Sprout addresses after 15 February 2019. On 3 October 2026 it activated Ironwood, a second shielded pool on the Halo2 proving system that began as an integration of Zcash's Orchard and, unlike Sapling, needs no trusted setup. Users can disclose a key that decrypts a single Sapling output or Ironwood action without exposing their spending key.

On 14 October 2026, eleven days after Ironwood activated, the project found that about 39.8 million ARRR, about 20% of supply, had been created without backing. Version 6.0.10, a mandatory release of 18 October, named two consensus flaws: block validation skipped the burn-proof checks on coin-import transactions, and a misreading of non-standard time-locked scripts let an output pass the transparent-address restriction while staying spendable by its author. The new coins entered the Sapling pool. The team asked exchanges and mining pools to pause and notaries suspended notarisations; 6.0.10 re-validates the chain under the corrected rules, so blocks with unproven imports are rejected.

Pirate Chain does not hide everything. Every shielded transaction is still a public record that a transaction happened, with its contents encrypted. In September 2019 a flaw disclosed for Zcash and its forks, Pirate among them, let someone who paid a shielded address learn the IP address of the full node holding it; routing through Tor avoided it. A disclosure key, once shared, reveals the output it covers to whoever holds it.

Market cap over time

No daily history for Pirate Chain is held on this site: the daily market caps on this site come from Coin Metrics Community Data, which does not cover ARRR, so only the current market cap from DefiLlama is shown, at the top of the page.

What it hides and what it does not

What it hides

  • The sender, the receiver and the amount of every payment between users: the chain allows no transparent transactions between users, only shielded ones.
  • Balances: coins are held only as encrypted notes in the Sapling and, since 3 October 2026, Ironwood shielded pools.

What it does not hide

  • That a transaction took place: each shielded transaction is still a public record on the chain, with its contents encrypted.
  • The IP address of a full node holding a shielded address, to someone who paid that address, under a flaw disclosed for Zcash and its forks, Pirate among them, in September 2019; routing through Tor avoided it.
  • A single Sapling output or Ironwood action, to anyone given its disclosure key.

Drawn from how it works, above; the sources are listed at the end of the page. Where privacy still leaks explains the patterns, such as timing and amounts, that can give users of any design away.

Audits

One security review, with what each covered and found. Dates are when each report was issued, unless the entry says otherwise.

DateFirmScope and findings
Not dated Not named in the sources found

A code security review of the Pirate wallet is linked from Pirate Chain's website and from exchange listing pages, but the page could not be read when this profile was checked, so its author, scope and findings are not confirmed. No audit of the chain's consensus code was found.

Source: Code security review: Pirate wallet Pirate Chain

Incidents

Five incidents, oldest first: flaws, exploits, sanctions, prosecutions and other events that affected the project or its users.

  1. Duke Leto, a Komodo developer, disclosed a flaw in Zcash and most of its forks, Pirate among them, that let someone who paid a shielded address learn the IP address of the full node holding it; users who had never used a shielded address or who routed through Tor were not affected.

    Source: Vulnerabilidad permite revelar direcciones IP en Zcash y otras 14 criptomonedas CriptoNoticias, 30 Sep 2019

  2. Release 5.7.5 added a cleanup mode, an aggressive consolidation for addresses that had been spammed, and a filter that ignores spam dust transactions below a threshold; release 5.8.0 of 7 March 2024 then indexed Sapling output and spend proofs so that one proof cannot be used twice, against transaction spam.

    Sources: Version 5.7.5 Signed Release PirateNetwork (GitHub), 14 Aug 2023; Version 5.8.0 Signed Release PirateNetwork (GitHub), 7 Mar 2024

  3. KuCoin removed its ARRR/USDT and ARRR/BTC pairs at 07:00 UTC under its Special Treatment rules, announced the day before with ETN, SWINGBY, GENS, ACOIN and BUX, and closed withdrawals on 28 March 2024; it had listed ARRR on 22 June 2021.

    Sources: ST: KuCoin Will Delist Certain Projects KuCoin, 21 Sep 2023; Pirate Chain (ARRR) Gets Listed on KuCoin! KuCoin, 21 Jun 2021

  4. Release 5.9.3 patched CVE-2024-52911, a security issue published for Bitcoin Core without details, and a denial-of-service issue, both found by anticsdecoded.

    Sources: Version 5.9.3 Signed Release PirateNetwork (GitHub), 25 Jun 2026; CVE-2024-52911 CVE Program (MITRE)

  5. Exploit

    About 39.8 million ARRR, about 20% of supply, were created through two consensus flaws, an unchecked coin-import path and a misread time-locked script, and moved into the Sapling shielded pool. The team asked users not to move funds and exchanges and mining pools to pause, NonKYC restricted the associated account, and notaries suspended notarisations; a proposed rollback to 20:00 UTC on 14 October gave way to a coordinated recovery, and the mandatory release 6.0.10 of 18 October rejects blocks with the unbacked imports. The team said there was no sign that the zk-SNARK cryptography or the notary keys had been compromised.

    Sources: Release notes 6.0.10 (mandatory security release) PirateNetwork (GitHub), 18 Oct 2026; Pirate Chain exploit mints around 39.8 million ARRR, team proposes rollback Crypto Briefing, 15 Oct 2026; Pirate Chain Hack Creates 39.8 Million ARRR, Increasing Token Supply by 20% KuCoin, 19 Oct 2026

Milestones

Eight milestones, oldest first.

  1. The PIRATE asset chain launched on Komodo with an initial supply of zero and only shielded transactions between users; its announcement thread opened on 30 August 2018.

    Source: [ANN] PIRATE: privacy, shielded, z-transactions-only chain Bitcointalk, 30 Aug 2018

  2. Sprout addresses were disabled, after holders had to move their funds to Sapling addresses.

    Source: How to migrate Pirate (ARRR) from Sprout address to Sapling address PirateNetwork (GitHub wiki), 23 Oct 2026

  3. Komodo's dPoW, which notarises Pirate Chain, moved its cross-chain notarisations from Bitcoin to Litecoin at the start of notary Season 5.

    Source: Komodo's dPoW Now Supports Litecoin Notarizations For 51% Attack Protection Komodo Platform

  4. KuCoin listed ARRR with ARRR/USDT and ARRR/BTC pairs.

    Source: Pirate Chain (ARRR) Gets Listed on KuCoin! KuCoin, 21 Jun 2021

  5. MEXC opened ARRR/USDT trading in its Innovation Zone after a Kickstarter vote.

    Source: Voting Result and Listing Arrangement for Kickstarter -Pirate Chain (ARRR) MEXC, 9 Jan 2024

  6. The deadline for the hard fork for Komodo's dPoW Season 8, shipped in version 5.9.0 on 6 September 2024: every wallet had to be updated by then to keep syncing.

    Source: Version 5.9.0 Signed Release PirateNetwork (GitHub), 6 Sep 2024

  7. Ironwood, a shielded pool on the Halo2 proving system derived from Zcash's Orchard, activated at 19:00 UTC by timestamp rather than block height.

    Source: Release notes 6.0.0 (Ironwood) PirateNetwork (GitHub), 23 Oct 2026

  8. Mandatory security release 6.0.10 fixed the consensus flaws behind the October exploit and re-validated the chain under the corrected rules; 6.0.14 followed on 21 October with header-sync fixes for nodes meeting the discarded chain.

    Sources: Release notes 6.0.10 (mandatory security release) PirateNetwork (GitHub), 18 Oct 2026; Release notes 6.0.14 PirateNetwork (GitHub), 21 Oct 2026

Funding

One source of funding. Amounts are in US dollars; a dash means the sources give no US dollar figure.

DateRoundAmountInvestors

No premine: the chain launched with an initial supply of zero (-ac_supply=0), so every ARRR comes from mining; the announcement thread also described an airdrop of 250,000 ARRR to early users who supplied a shielded address (in ARRR, so no US dollar amount)

Sources: [ANN] PIRATE: privacy, shielded, z-transactions-only chain Bitcointalk, 30 Aug 2018; Pirate Chain README: tech specification PirateNetwork (GitHub), 23 Oct 2026

 – –

Risks

In October 2026 two consensus flaws let about 39.8 million ARRR, about 20% of supply, be created without backing; the coins went into the shielded pool, where they cannot be traced, and recovery depended on every node, miner, pool, notary and exchange moving to the corrected releases, with the treatment of affected users unsettled in the sources found. Because all balances are encrypted, the supply cannot be checked by adding up balances, so its integrity rests on the correctness of consensus checks such as those that failed. The Sapling pool, where most coins are held, depends on a trusted setup inherited from Zcash, which the newer Ironwood pool avoids. Protection against 51% attacks depends on Komodo's notary nodes and their notarisations to Litecoin, which were suspended during the incident. No audit of the chain's consensus code was found, and the wallet review linked from the website could not be confirmed. Access through large exchanges is narrow: of the 14 this site checks, only Gate and MEXC listed ARRR on 13 October 2026, KuCoin delisted it in 2023, and from 10 July 2027 the EU's Anti-Money Laundering Regulation will bar crypto-asset service providers from keeping accounts that allow transactions to be anonymised or obscured, including through anonymity-enhancing coins.

Sources

The documents this profile rests on. Each audit, incident, milestone and funding round above also links its own sources.

Checked on 23 Oct 2026. Confidence: reported. Information only, not investment, legal or tax advice.

Other profiles