What is Pirate Chain?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
Pirate Chain is a privacy cryptocurrency where every single transaction is shielded using zk-SNARKs — unlike Zcash where transparent transactions are still permitted, Pirate Chain's protocol makes shielded-only transactions the only option, combined with Komodo's delayed proof-of-work security anchored to Bitcoin.
The problem with optional privacy
Zcash allows both transparent and shielded transactions. In practice, the majority of Zcash transactions historically used transparent addresses — meaning Zcash's blockchain had a visible public transaction graph alongside its shielded pool. This is a problem: if most users transact transparently, the shielded users stand out as a suspect minority, and their anonymity set (the group of people their transaction could be confused with) is limited to other shielded users.
Pirate Chain's response: remove the choice entirely. The protocol enforces that all transactions must be shielded. There are no transparent addresses. There are no visible transaction amounts. There are no visible senders or receivers. The entire blockchain is a shielded pool. This maximises the anonymity set — every transaction looks identical to every other transaction from the outside.
Technical foundation — Zcash's Sapling + Komodo's dPoW
Pirate Chain (launched August 2018) is built on Komodo's Smart Chain framework, using Zcash's Sapling zk-SNARK technology for privacy. It inherits Komodo's delayed proof-of-work security — the chain state is periodically notarised into Komodo's blockchain, which in turn is notarised into Bitcoin. This gives Pirate Chain a security chain that ultimately traces to Bitcoin's hashrate, making 51% attacks prohibitively expensive despite Pirate Chain's small native hashrate.
ARRR token supply and mining
ARRR has a maximum supply of 200 million tokens. Mining uses the Equihash 200,9 proof-of-work algorithm. The block reward decreases over time following a schedule similar to Zcash's. No pre-mine, no ICO — all ARRR was distributed through mining from genesis.
Is it legal in India?
Yes. ARRR is a VDA under Indian law. 30% tax and 1% TDS apply. Privacy coins face heightened regulatory scrutiny globally — verify exchange availability before trading. See India regulation.
🟡 A bit more detail
For when you want to go a little deeper.
Why mandatory privacy changes the anonymity model
In any optional-privacy system, the size of the shielded pool limits anonymity. If only 10% of users shield transactions, then when someone does use shielded addresses, the anonymity set is restricted to that 10%. An observer knows the transaction came from someone in the shielded pool — narrowing the possibilities significantly. With mandatory shielding: every transaction in history is shielded. The anonymity set is the entire transaction history. There is no pattern distinguishing "private users" from "standard users" because all users are the same class.
Pirate Chain developed a significant community of privacy advocates who prefer its mandatory shielding model over Zcash's optional approach. The chain has been listed on several exchanges, though like all privacy coins it faces ongoing regulatory scrutiny and periodic exchange delistings. Pirate Chain's community maintains a wallet (Pirate Ocean), a light wallet, and various integrations. The ARRR ticker is a deliberate reference to pirate culture — a branding choice that reflects the community's anti-surveillance ethos. The chain has processed millions of private transactions since 2018.
Komodo dPoW integration
Pirate Chain's connection to Komodo's notary node network means its chain state is notarised into Komodo's blockchain every few minutes, and Komodo's state is in turn notarised into Bitcoin. This two-hop security model gives Pirate Chain Bitcoin-equivalent reorganisation resistance for transactions older than the most recent notarisation. An attacker wanting to double-spend an old ARRR transaction would need to reorganise both Komodo and Bitcoin simultaneously — an essentially impossible task.
Key Pirate Chain metrics: transaction volume (fully private, so only count is visible — not amounts or parties), ARRR hashrate, notarisation frequency, and exchange listing status. The mandatory shielding is both the strongest argument for ARRR and the primary regulatory concern — there is no mechanism for selective disclosure (unlike Zcash's view keys or Firo's audit keys). Live data: CoinGecko · Pirate Chain Explorer.
🟣 The full technical picture
For the technically curious.
The Sapling circuit on Pirate Chain
Pirate Chain uses Zcash's Sapling zk-SNARK proving system — the same circuit that reduced Zcash's shielded transaction proving time from ~40 seconds to ~2 seconds and memory from ~3GB to ~40MB. The Sapling circuit (a PLONK-inspired SNARK using BLS12-381 elliptic curve operations) generates a proof that: (1) the input notes exist in the note commitment tree, (2) the nullifiers are computed correctly from the spending keys, and (3) the transaction is value-balanced (inputs equal outputs plus fee). Unlike Zcash's Orchard (which uses Halo 2 with no trusted setup), Pirate Chain's Sapling circuit relies on the Zcash Powers of Tau trusted setup ceremony.
Source: Pirate Chain documentation. piratechain.com · Zcash Sapling specification: zips.z.cash/protocol/sapling.pdf
The enforcement mechanism
Mandatory shielding is enforced at the consensus layer — the Pirate Chain node software simply rejects any transaction that does not use the shielded note format. There is no code path for transparent transactions. Miners will not include them in blocks. Nodes will not relay them. The enforcement is not policy — it is protocol. There is no way to create a transparent ARRR transaction any more than there is a way to create a Bitcoin transaction without a valid signature. This is the fundamental difference from Zcash's "shielded by default" marketing — Pirate Chain's shielding is not a default, it is the only option.
Pirate Chain's note commitment tree uses the same Merkle tree structure as Zcash's Sapling — an incremental Merkle tree (Merkle tree that can have leaves appended without recomputing the entire tree) of depth 32, capable of storing 2³² = 4.3 billion note commitments. Each new shielded transaction appends new note commitments. The tree root is included in each block header. Provers use the root to demonstrate their note exists in the tree without revealing which leaf it is. The incremental structure allows efficient root computation after each new commitment, important for the continuous flow of new private transactions.
Key facts
- Privacy model: Mandatory shielded (all transactions private)
- Technology: Zcash Sapling zk-SNARKs (Komodo Smart Chain framework)
- Security: dPoW (notarised into Komodo → Bitcoin)
- Mining: Equihash 200,9 (PoW)
- ARRR supply: 200 million (max)
- Launch: August 2018 (no pre-mine)
- No transparent transactions: Enforced at protocol level