Skip to content
Morphit
Start— sign in or create an account

Privacy practices for ARRR trades

Pirate Chain (ARRR) launched in 2018 as a fork of the Zcash codebase, configured so that the Sapling shielded pool is the only available transaction type. Every transfer goes through zero-knowledge proofs (zk-SNARKs) that hide sender, recipient, and amount on chain. Pirate Chain sunsetted the transparent pool early in the chain's life and forcibly migrated all transparent balances to shielded — there is no transparent address option. Addresses use the `zs1` Sapling format (bech32, 78 chars total), visually identical to Zcash Sapling addresses. The practices below cover wallet-side hygiene that survives even chain-level shielding — the on-chain payload is private, but what you share off-chain (which addresses you publish, which counterparties you transact with) is what links your Morphit trades together over time.

Use a fresh address every trade

This chain uses transparent addresses with no native stealth. The standard practice: use a Hierarchical Deterministic (BIP-32) wallet that derives a new receive address per request. Most modern wallets do this automatically. The cost of address reuse is severe — every trade you accept at the same address builds a public record of your activity.

Opt-in privacy technologies

Standards that wallets in this ecosystem may implement. Morphit does NOT recommend specific wallet software — even reputable wallets have been compromised. Search for a wallet that supports these standards and review its trust posture yourself.

  • Shielded pools (Sapling + Orchard)

    Zcash's protocol-level privacy. Shielded transactions (zs1 Sapling, u1 Unified Address) use zero-knowledge proofs (zk-SNARKs) to hide sender, recipient, and amount on chain. Sapling is the established shielded pool (since 2018); Orchard is the newer pool (Network Upgrade 5, 2022) accessed through Unified Addresses. Per-address — recipients pick z/u-addr for shielded transactions or t-addr for transparent. Both transparent and shielded are first-class on the protocol. Wallets that fully support shielded sends: Zashi (mobile, official from Electric Coin Co, Sapling + Orchard), Zecwallet (desktop, Sapling), Nighthawk Wallet (mobile, Sapling). Older wallets may only support transparent (t-addr) sends, so confirm your counterparty's wallet supports the address type you intend to use.

Universal practices

**Use a fresh receive address for every trade.** Your wallet should support this; if it doesn't, look for one that does. Address reuse is the single biggest leak.

**Practice coin control when spending.** When sending coins later, avoid combining the trade output with coins from another source — that combines their address histories permanently.

**Broadcast through Tor or your wallet's privacy mode.** Your home IP address sees the transaction first; nodes near your IP can correlate it to you. A Tor-aware wallet broadcasts through Tor by default.

**Avoid sending trade coins to or from KYC exchanges.** Once trade coins touch a KYC exchange, the trade becomes legally identifiable by combining exchange records with chain data. If you need to bridge to fiat, route through a self-custodied intermediate step.

What to avoid

  • Do not paste your same receive address into multiple trades.
  • Do not send the exact amount listed on the order — Morphit's amount-randomizer toggle (the "🔐 Randomize amount" checkbox in the address-share modal) breaks this; leave it ON.
  • Do not combine the trade output with coins from a different source when you later spend it.
  • Do not broadcast from your home IP via a non-private wallet — use Tor.

⚠ Caveats specific to this asset

Pirate Chain's chain-level shielding hides sender, recipient, and amount on chain — but it does not erase off-chain linkability. - **Share fresh addresses per trade.** Using the same `zs1` address across multiple Morphit listings lets observers correlate your orders even though the chain itself reveals nothing. Generate a fresh receive address per trade (Pirate Chain wallets derive these from your HD seed). - **Wallet compatibility.** Not every wallet supports Pirate Chain (the major options are Treasure Chest, Pirate.Black, and Verus-integrated Pirate). Confirm your counterparty has a compatible wallet before agreeing to a price. - **Network-layer privacy still matters.** Broadcasting through Tor or your wallet's privacy mode keeps your home IP off the chain's view of you. - **Visual collision with Zcash Sapling addresses.** Pirate Chain `zs1` addresses look exactly like Zcash `zs1` addresses. Morphit's per-asset tab and placeholder disambiguate, but if you copy an address from a different context, confirm it belongs to the chain you intend to send on.

Morphit does NOT recommend specific wallet software. Even reputable wallets have been compromised or have had hidden flaws. The privacy techniques here are protocol standards, not endorsements — your wallet, your responsibility.