Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
publish · Pirate Chain (ARRR)
- Sequence
- #1
- Score
- →
- Cluster
- mainnet-beta
- Slot
- 459760483
- Off-chain at
- 2026-10-21T20:14:57.436Z
- Anchored at
- 2026-10-21T20:15:03.000Z
- Block time
- 2026-10-21T20:15:03.000Z
Independent verification
- 1. Database (off-chain)
- 9eZF3QibvasSYo8Zowhi13x7SZMStEFDMGYemDnQvnhL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (12757 chars)
{"actor":"system:backfill","investigation_id":"97da5499-cead-40ca-ab1d-5604722dafd0","kind":"publish","page_slug":"pirate-chain-arrr","published_at":"2026-10-21T20:14:57.360Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Pirate Chain (ARRR)","sections":[{"content":"Pirate Chain (ARRR) launched on 29 August 2018, built by developers from the Komodo community as an independent asset chain using Komodo Platform's infrastructure. Unlike privacy coins that make shielding optional, Pirate Chain enforces mandatory zk-SNARK privacy on all transactions, a model it borrows conceptually from Zcash, combined with Komodo's Delayed Proof of Work (dPoW) notarization intended to protect against 51% attacks. The project describes itself as having had a 'fair launch' with no ICO, no premine, and no developer fee, and caps maximum supply at 200 million ARRR. Listings differ on exact circulating-supply figures, with CoinMarketCap data showing roughly 196 million ARRR in circulation prior to the October 2026 incident described below. Claims that figures such as John McAfee and Jeff Berwick were founders appear on some listing pages without clear sourcing and should be treated as unverified.","heading":"Background and Technology","severity":"low","sources":[{"credibility":2,"name":"CoinMarketCap — Pirate Chain (ARRR)","type":"other","url":"https://coinmarketcap.com/currencies/pirate-chain/"}]},{"content":"On 15 October 2026, Pirate Chain confirmed that a flaw discovered the previous day had allowed an attacker to mint approximately 39.8 million ARRR without authorization — about 20% of circulating supply at the time. The flaw stemmed from two transaction-validation failures tied to the 'Ironwood' network upgrade, which had been scheduled to activate on 3 October 2026; one failure allowed transactions to bypass checks meant to cap new-coin issuance. The newly created coins were moved into the project's mandatory Sapling shielded pool, where Pirate Chain's own privacy design prevents the coins' subsequent movement from being traced on-chain. The team stated it found no evidence that its dPoW notary keys or the underlying zk-SNARK cryptography had been compromised, characterizing the bug as a transaction-validation failure rather than a break of the privacy layer itself. A dedicated incident page, 'Pirate Chain (ARRR) Ironwood Exploit,' covers the event's facts and timeline in more depth; this section summarizes it only for context.","heading":"October 2026 Ironwood Exploit and Unauthorized Issuance","severity":"critical","sources":[{"credibility":2,"name":"Pirate Chain exploit mints around 39.8 million ARRR, team proposes rollback","type":"news_article","url":"https://cryptobriefing.com/pirate-chain-exploit-arrr-rollback/"},{"credibility":2,"name":"Pirate Chain Exploit Mints 39.8 Million ARRR, Raising Supply by 20%","type":"news_article","url":"https://www.analyticsinsight.net/news/pirate-chain-exploit-mints-398-million-arrr-raising-supply-by-20"},{"credibility":2,"name":"Pirate Chain Exploit Mints 39.8M ARRR, Rollback Plan Dropped","type":"news_article","url":"https://www.cryptotimes.io/2026/10/16/pirate-chain-exploit-mints-39-8m-arrr-rollback-plan-dropped/"}]},{"content":"Pirate Chain initially proposed reverting the blockchain to its state at 20:00 UTC on 14 October 2026, discarding all blocks produced after the exploit window, and asked dPoW notary operators, exchanges, and mining pools to voluntarily pause activity while this was carried out. On 15 October 2026, in a follow-up statement, the project reversed course, saying it was 'not possible to freeze the network or unilaterally rollback its blockchain history' because of the network's decentralized structure. One Russian-language technology outlet reported that an attempted rollback did not take effect because the network did not comply, though this specific claim has not been corroborated by other outlets found in this research and should be treated as a lower-confidence, single-source report. As of the most recent reporting available (16 October 2026), the roughly 39.8 million unauthorized ARRR have not been removed from supply, the identity and location of the funds remain obscured by the shielded pool, and the project has not published a full technical post-mortem of the two validation failures involved.","heading":"Rollback Reversal and Unresolved Supply Integrity","severity":"high","sources":[{"credibility":2,"name":"Pirate Chain Exploit Mints 39.8M ARRR, Rollback Plan Dropped","type":"news_article","url":"https://www.cryptotimes.io/2026/10/16/pirate-chain-exploit-mints-39-8m-arrr-rollback-plan-dropped/"},{"credibility":2,"name":"Pirate Chain exploit mints around 39.8 million ARRR, team proposes rollback","type":"news_article","url":"https://cryptobriefing.com/pirate-chain-exploit-arrr-rollback/"},{"credibility":3,"name":"SecurityLab.ru — Pirate Chain rollback attempt report (Russian-language)","type":"news_article","url":"https://www.securitylab.ru/news/578954.php"}]},{"content":"Following disclosure of the exploit, exchange NonKYC identified deposits of ARRR linked to the incident, restricted the associated account, and blocked related withdrawals; reporting characterized this as likely preventing at least some of the unauthorized coins from being converted into other assets before detection. MEXC also suspended ARRR deposits and withdrawals at the project's request as a precaution. Price impact in the immediate aftermath was reported inconsistently across outlets: one report placed ARRR trading between $0.27 and $0.28 on 15 October 2026 with no sharp immediate move, while coverage citing CoinGecko data the following day showed a price of $0.2614, a roughly 4% daily decline, with that outlet noting no outlet had firmly linked the drop to the exploit. Given Pirate Chain's historically thin trading liquidity, several reports cautioned that volatility could increase once exchange activity and transfers fully resume.","heading":"Exchange Responses and Market Impact","severity":"medium","sources":[{"credibility":2,"name":"Pirate Chain exploit mints around 39.8 million ARRR, team proposes rollback","type":"news_article","url":"https://cryptobriefing.com/pirate-chain-exploit-arrr-rollback/"},{"credibility":2,"name":"Pirate Chain Exploit: Millions of New ARRR Created, Where Did They Go?","type":"news_article","url":"https://www.coingabbar.com/en/pirate-chain-exploit-arrr-new-coins-hidden-pool-recovery-plan"}]},{"content":"Pirate Chain operates with a largely anonymous or pseudonymous development team, a common feature among privacy-coin projects but one that limits external accountability when incidents like the October 2026 exploit occur. As of the most recent reporting found, the project has communicated primarily through social media posts rather than a detailed technical disclosure, and has given at least two different public positions on remediation within 24–48 hours (first proposing, then abandoning, a chain rollback), which independent reporting described inconsistently across outlets published on 15 and 16 October 2026. Combined with the shielded pool's inherent untraceability — a core design feature of the coin being used, in this instance, to obscure the destination of unauthorized funds — these factors weigh on confidence in the project's ability to resolve supply-integrity issues transparently. No regulatory or law-enforcement action related to this incident was found in this research.","heading":"Transparency and Accountability Considerations","severity":"medium","sources":[{"credibility":2,"name":"Pirate Chain Exploit Mints 39.8M ARRR, Rollback Plan Dropped","type":"news_article","url":"https://www.cryptotimes.io/2026/10/16/pirate-chain-exploit-mints-39-8m-arrr-rollback-plan-dropped/"},{"credibility":2,"name":"Pirate Chain exploit mints around 39.8 million ARRR, team proposes rollback","type":"news_article","url":"https://cryptobriefing.com/pirate-chain-exploit-arrr-rollback/"}]}],"sources_used":[{"credibility":2,"name":"CoinMarketCap — Pirate Chain (ARRR)","type":"other","url":"https://coinmarketcap.com/currencies/pirate-chain/"},{"credibility":2,"name":"Pirate Chain exploit mints around 39.8 million ARRR, team proposes rollback","type":"news_article","url":"https://cryptobriefing.com/pirate-chain-exploit-arrr-rollback/"},{"credibility":2,"name":"Pirate Chain Exploit Mints 39.8 Million ARRR, Raising Supply by 20%","type":"news_article","url":"https://www.analyticsinsight.net/news/pirate-chain-exploit-mints-398-million-arrr-raising-supply-by-20"},{"credibility":2,"name":"Pirate Chain Exploit Mints 39.8M ARRR, Rollback Plan Dropped","type":"news_article","url":"https://www.cryptotimes.io/2026/10/16/pirate-chain-exploit-mints-39-8m-arrr-rollback-plan-dropped/"},{"credibility":2,"name":"Pirate Chain Rolls Back Blockchain After Ironwood Turnstile Exploit","type":"news_article","url":"https://www.cryptotimes.io/2026/10/15/pirate-chain-rolls-back-blockchain-after-ironwood-turnstile-exploit/"},{"credibility":2,"name":"Pirate Chain Exploit: Millions of New ARRR Created, Where Did They Go?","type":"news_article","url":"https://www.coingabbar.com/en/pirate-chain-exploit-arrr-new-coins-hidden-pool-recovery-plan"},{"credibility":3,"name":"SecurityLab.ru — Pirate Chain rollback attempt report (Russian-language)","type":"news_article","url":"https://www.securitylab.ru/news/578954.php"}],"summary":"Pirate Chain (ARRR) is a privacy-focused cryptocurrency launched in 2018 that enforces mandatory zk-SNARK shielding on all transactions, built on Komodo Platform infrastructure. In October 2026 a validation flaw introduced by the project's 'Ironwood' network upgrade allowed an attacker to mint roughly 39.8 million unauthorized ARRR (about 20% of circulating supply) directly into the shielded pool, and the team's proposed rollback was subsequently abandoned as technically unworkable, leaving the inflation unresolved. A dedicated incident page (Pirate Chain (ARRR) Ironwood Exploit) covers that event in detail; this page focuses on the project's general background and the broader trust implications.","timeline":[{"date":"2018-08-29","date_evidence":"Launched on 29 August 2018 by developers from the Komodo community as an independent asset chain built on Komodo Platform technology.","event":"Pirate Chain (ARRR) launches as an independent asset chain on Komodo Platform infrastructure.","source":"CoinMarketCap","source_url":"https://coinmarketcap.com/currencies/pirate-chain/"},{"date":"2026-10","date_evidence":"The incident followed the Ironwood upgrade, which Pirate Chain scheduled for Oct. 3.","date_original":"2026-10-03","event":"Pirate Chain's 'Ironwood' network upgrade is scheduled to activate.","source":"Analytics Insight","source_url":"https://www.analyticsinsight.net/news/pirate-chain-exploit-mints-398-million-arrr-raising-supply-by-20"},{"date":"2026-10","date_evidence":"Pirate Chain confirmed on Oct. 15 that the flaw was discovered on Oct. 14.","date_original":"2026-10-14","event":"A validation flaw tied to Ironwood is discovered, having allowed unauthorized minting of ARRR.","source":"Analytics Insight","source_url":"https://www.analyticsinsight.net/news/pirate-chain-exploit-mints-398-million-arrr-raising-supply-by-20"},{"date":"2026-10","date_evidence":"Pirate Chain confirmed on Oct. 15 that the flaw was discovered on Oct. 14.","date_original":"2026-10-15","event":"Pirate Chain publicly confirms the exploit, reporting approximately 39.8 million ARRR (about 20% of supply) minted into the shielded pool, and initially proposes a rollback to the chain's state at 20:00 UTC on October 14.","source":"Analytics Insight / Crypto Briefing","source_url":"https://cryptobriefing.com/pirate-chain-exploit-arrr-rollback/"},{"date":"2026-10","date_evidence":"The statement said it is \"not possible to freeze the network or unilaterally rollback its blockchain history\" because the network is decentralized.","date_original":"2026-10-15","event":"Pirate Chain reverses its rollback plan, stating a unilateral rollback is not possible given the network's decentralized structure, leaving the unauthorized issuance unresolved.","source":"Crypto Times","source_url":"https://www.cryptotimes.io/2026/10/16/pirate-chain-exploit-mints-39-8m-arrr-rollback-plan-dropped/"},{"date":"2026-10","date_original":"2026-10-16","event":"Follow-up reporting notes the project has not published a full technical post-mortem and that market price moves since the disclosure have not been conclusively linked to the exploit by any outlet reviewed.","source":"Crypto Times / CoinGabbar","source_url":"https://www.coingabbar.com/en/pirate-chain-exploit-arrr-new-coins-hidden-pool-recovery-plan"}]},"v":1}