Skip to main content
AVOID.NET
← Maya Protocol17 decisions on this page

Audit log

Every state-changing event for Maya Protocol: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-08-26 23:09:26Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 443,522,386
    sig
    4EHVZuyjTfor…kb9BxVg9explorer ↗
    hash
    685NpNaZmATd…pguUDUDTsha256 → base58
    verifying row…full verify ↗
    canonical bytes (24070 B) ▸
    {"actor":"system:backfill","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","kind":"publish","page_slug":"maya-protocol","published_at":"2026-08-26T23:09:26.566Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Maya Protocol","sections":[{"content":"Maya Protocol describes itself as a 'friendly fork' of THORChain, built on Cosmos SDK, Tendermint consensus, and the GG20 Threshold Signature Scheme. It enables native cross-chain swaps of assets including Bitcoin, Ethereum, DASH, and others without bridges or wrapped tokens. Development began in early 2021, and the MAYAChain mainnet launched on March 7, 2023, following a Liquidity Auction that raised over $11 million in Bitcoin, Ethereum, stablecoins, and RUNE. The auction distributed the entire CACAO token supply to liquidity providers; the founding team retained no CACAO allocation at genesis. Prior to the August 2026 exploit, Maya had maintained its mainnet for approximately three years without a reported loss-of-funds incident, with pre-incident total value locked estimated at roughly $15 million managed by approximately 38 active validators.","heading":"Protocol Background","severity":"low","sources":[{"credibility":2,"name":"What Is Maya Protocol? — The Defiant","type":"news_article","url":"https://thedefiant.io/education/defi/what-is-maya-protocol"},{"credibility":3,"name":"Cross-chain DEX Maya Protocol to launch mainnet on March 7, 2023 — Digital Art","type":"news_article","url":"https://digitalart.org/cross-chain-decentralized-exchange-maya-protocol-to-launch-its-mainnet-on-march-7-2023/"},{"credibility":2,"name":"Maya Protocol Hit by $1.7M Exploit in First Major Breach Since 2023 — Crypto Times","type":"news_article","url":"https://www.cryptotimes.io/2026/08/19/maya-protocol-hit-by-1-7m-exploit-in-first-major-breach-since-2023/"}]},{"content":"At approximately 17:30 UTC on August 18, 2026, an attacker submitted a single deposit transaction to the MAYAChain mainnet containing 23 discrete messages. This transaction activated a cascade of six distinct software vulnerabilities spanning the protocol's trade-account handling, outbound transaction processing, and liquidity-pool mathematics. The attack allowed the attacker to fabricate approximately 49.45 million CACAO tokens through an uncapped slash-subsidy mechanism, acquire 99.93% ownership of a distorted liquidity pool by depositing only 100 CACAO, and withdraw 48.87 million CACAO. The attacker then converted the CACAO into approximately 20.83 BTC and smaller quantities of other assets across ten conversion blocks (blocks 17,977,998 to 17,978,008). The total confirmed extraction sent to addresses under the attacker's control was approximately $1.36 million in Bitcoin, with total attacker-controlled value including remaining CACAO estimated at approximately $1.65–$1.7 million. The exploit reduced Maya's total value locked by an estimated $10.9 million when including the knock-on collapse in CACAO's market price. The incident was reported as the 16th crypto hack of August 2026.","heading":"August 2026 Exploit: Attack Overview","severity":"critical","sources":[{"credibility":2,"name":"Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen — Decrypt","type":"news_article","url":"https://decrypt.co/375976/maya-protocol-halts-network-bitcoin-exploit"},{"credibility":1,"name":"Maya Protocol exploit drains bitcoin and other assets as pool value drops by $11 million — CoinDesk","type":"news_article","url":"https://www.coindesk.com/markets/2026/08/19/maya-protocol-exploit-drains-bitcoin-and-other-assets-as-pool-value-drops-usd11-million"},{"credibility":2,"name":"Maya Protocol Six-Bug Trade Account Exploit — Defimon","type":"research","url":"https://defimon.xyz/blog/maya-protocol-hack-august-2026"},{"credibility":2,"name":"Maya Protocol Becomes the 16th Crypto Hack Logged in August Alone — CryptoRank","type":"news_article","url":"https://cryptorank.io/news/feed/0486d-maya-protocol-exploit-halts-btc-swaps"}]},{"content":"Security researchers and external analysts, including CertiK, identified six discrete flaws that the attacker chained in sequence. Bug 1 — Voter Clobbering in handler_deposit.go: Each message in a batched MsgDeposit transaction overwrote the previous ObservedTxVoter, allowing a trailing DONATE message to reset OutboundHeight to zero. Bug 2 — Flawed Outbound Matcher Logic: With OutboundHeight set to zero, the system fell back to FinalisedHeight and walked forward in signingTransPeriod strides rather than checking each block, causing it to miss the actual settlement at block 17,977,942 and incorrectly classify a legitimate outgoing transfer as missing or stolen. Bug 3 — Uncapped Subsidy Calculation: The slash compensation function in helpers.go line 224 was not capped against pool depth, triggering a 49.45 million CACAO payout for a pool holding only 0.11 LINK. Bug 4 — Premature State Commitment: Pool balances were written to state before the system attempted to fund them, creating an irreversible accounting imbalance. Bug 5 — Failed Funding Without Rollback: The Reserve held only approximately 168,000 CACAO against a 49.45 million CACAO obligation; the transfer failed but execution continued in the same Cosmos context with no rollback, leaving the inflated balance permanently recorded. Bug 6 — Pool Math Treating Empty Pools as New: When the attacker deposited 100 CACAO into the now-depleted pool, the system issued liquidity units as if it were seeding a new pool, granting the attacker 99.93% ownership. The attacker exploited that ownership to withdraw 48.87 million CACAO from the Asgard vault. Maya's team acknowledged these bugs had gone undetected for three to four years despite multiple audits.","heading":"Technical Analysis: The Six Chained Vulnerabilities","severity":"critical","sources":[{"credibility":2,"name":"Maya Protocol Six-Bug Trade Account Exploit — Defimon","type":"research","url":"https://defimon.xyz/blog/maya-protocol-hack-august-2026"},{"credibility":2,"name":"Maya Protocol loses $1.7M in sophisticated six-bug exploit — Cryptopolitan","type":"news_article","url":"https://www.cryptopolitan.com/maya-protocol-loses-1-7m-bug-exploit/"},{"credibility":2,"name":"Maya Protocol Hack: 6 Bugs Trigger $1.7M Exploit and 88% CACAO Crash — CoinGabbar","type":"news_article","url":"https://www.coingabbar.com/en/crypto-currency-news/maya-protocol-hack-news-6-bugs-1-7m-defi-exploit-cacao-crash"}]},{"content":"The attacker's confirmed Bitcoin extraction totaled 20.8274 BTC, consolidated at address bc1q0hsgwunccczelq05ucpmfz268eyy5jr2y5l646, valued at approximately $1.34–$1.36 million at the time of transfer. An additional approximately $287,000–$300,000 remained as 8.87 million CACAO held by the attacker. On-chain records as of August 21, 2026 showed the Bitcoin address held 20.82731228 BTC funded with zero outgoing transactions, meaning the attacker had not moved the Bitcoin as of that date. The CACAO token price fell approximately 88.7% from $0.115 to $0.013 on the day of the exploit, before partially recovering to approximately $0.032. Including the CACAO price collapse and associated pool devaluation, overall protocol TVL fell by an estimated $10.9 million. Security firm PeckShield traced the 20 BTC to the attacker's wallet. Maya Protocol operated a bug bounty program through Immunefi, though the program capped critical vulnerability payouts at $35,000 — far below the value extracted.","heading":"Financial Impact and On-Chain Evidence","severity":"critical","sources":[{"credibility":2,"name":"Peckshield: Maya Protocol Loses $1.7M, 20 BTC Traced to Wallet — Bitcoin.com News","type":"on_chain","url":"https://news.bitcoin.com/security/maya-protocol-exploit-1-7-million-peckshield/"},{"credibility":2,"name":"Maya Protocol's $11 million liquidity crash remains unresolved as attacker holds 20.83 BTC — KuCoin","type":"news_article","url":"https://www.kucoin.com/news/flash/maya-protocol-s-11-million-liquidity-crash-remains-unresolved-as-attacker-holds-20-83-btc"},{"credibility":2,"name":"Unresolved $11 million liquidity crash leaves pools exposed as attacker still holds 20.83 BTC — CryptoSlate","type":"news_article","url":"https://cryptoslate.com/maya-protocol-exploit-wallet-still-holds-20-83-btc-as-11-million-pool-impact-remains-unresolved/"},{"credibility":2,"name":"Maya Protocol Exploit Drains $1.7M as CACAO Falls 89% — CoinPaprika","type":"news_article","url":"https://coinpaprika.com/news/maya-protocol-exploit-drains-17m-cacao-falls/"}]},{"content":"Prior to the August 2026 exploit, Maya Protocol had been audited by Halborn across its Layer 1 code, the Liquidity Auction module, Dynamic Inflation, and the THORChain-inherited Bifrost components, as well as by a firm identified as Fable 5. Maya's team acknowledged that the six exploited bugs had gone undetected for three to four years despite these audits. The Ethereum router contract carried a 'Draft 3' audit label from Halborn as of early 2026, suggesting some components remained in an incomplete or preliminary audit state. The team stated following the exploit that it needs to take a 'more adversarial approach to reviewing its code.' The low Immunefi bug bounty cap of $35,000 for critical vulnerabilities has been cited by analysts as a factor that may have reduced external researcher incentive to audit the protocol's most sensitive components. Maya's codebase inherits significant portions from THORChain, which suffered a $15 million exploit in July 2021 and an additional vault breach in May 2026.","heading":"Audit History and Security Posture","severity":"high","sources":[{"credibility":2,"name":"Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen — Decrypt","type":"news_article","url":"https://decrypt.co/375976/maya-protocol-halts-network-bitcoin-exploit"},{"credibility":2,"name":"Maya Protocol Hit by $1.7M Exploit in First Major Breach Since 2023 — Crypto Times","type":"news_article","url":"https://www.cryptotimes.io/2026/08/19/maya-protocol-hit-by-1-7m-exploit-in-first-major-breach-since-2023/"}]},{"content":"Maya Protocol co-founder AaluxxMyth (known publicly as Aaluxx or Maya) announced the global network halt on Discord shortly after the exploit was detected on August 18, 2026. The team activated the protocol's 720-block HaltTrading mechanism, freezing all deposits and withdrawals. Aaluxx publicly stated: 'No way to sugar coat this. We have likely been exploited by 20 BTC ($1.4M) and other assets.' The founder thanked node operators for a rapid response and indicated the team had identified the vulnerabilities and begun preparing patches. The team published the attacker's Bitcoin address and appealed for voluntary return of funds under a bug bounty arrangement. Maya had not published a formal post-mortem document as of late August 2026; the technical breakdown circulating publicly was produced by external security analyst Defimon and security firm CertiK rather than by the Maya team itself. No timeline was given for restoring swaps, completing a compensation process, or finalizing a pool ledger.","heading":"Team Response and Network Halt","severity":"high","sources":[{"credibility":2,"name":"Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen — Decrypt","type":"news_article","url":"https://decrypt.co/375976/maya-protocol-halts-network-bitcoin-exploit"},{"credibility":2,"name":"Maya Protocol Halts Operations After Multi-Bug Exploit — Crowdfund Insider","type":"news_article","url":"https://www.crowdfundinsider.com/2026/08/299219-maya-protocol-halts-operations-after-multi-bug-exploit-drains-cacao-tokens-and-cross-chain-assets/"},{"credibility":2,"name":"Maya Protocol suffers $1.7 million exploit, halts network — Crypto.news","type":"news_article","url":"https://crypto.news/maya-protocol-suffers-1-7-million-exploit-halts-network/"}]},{"content":"As of late August 2026, the stolen funds had not been returned and Maya Protocol had not published a final compensation plan or pool restoration ledger. Founder Aaluxx indicated that the team plans to backfill the affected liquidity pool using external funds rather than relying on recovering the attacker's Bitcoin. The stated mechanism involves using investment proceeds from the protocol's Aztec Chain project — an omnichain DeFi expansion — to contribute approximately 20 BTC equivalent to make liquidity providers whole. However, no timeline was provided for Aztec Chain proceeds, the make-whole process, or the relaunch of swaps. Analysts drew explicit parallels to THORChain's post-exploit playbook, noting that THORChain similarly resolved two exploits (2021 and May 2026) without recovering stolen funds, relying instead on donations or protocol-owned liquidity absorption. Critics noted the absence of a final damage accounting that would clarify which losses the protocol intends to restore and which it does not. The wider TVL impact — approximately $10.9 million including CACAO devaluation — remained unaddressed in the team's public statements.","heading":"Recovery Plan and Unresolved Status","severity":"high","sources":[{"credibility":3,"name":"Maya Protocol Hack: Why the Recovery Plan Mirrors THORChain's Old Playbook — Cryip","type":"news_article","url":"https://cryip.co/maya-protocol-hack-recovery-plan-thorchain-playbook/"},{"credibility":2,"name":"Unresolved $11 million liquidity crash leaves pools exposed as attacker still holds 20.83 BTC — CryptoSlate","type":"news_article","url":"https://cryptoslate.com/maya-protocol-exploit-wallet-still-holds-20-83-btc-as-11-million-pool-impact-remains-unresolved/"},{"credibility":3,"name":"Maya Protocol Halts Network After $1.7M Exploit Chains Six Bugs — SpendNode","type":"news_article","url":"https://www.spendnode.io/blog/maya-protocol-halts-network-1-7m-chained-exploit-august-2026/"}]},{"content":"Maya Protocol is built as a fork of THORChain, sharing significant portions of its codebase including the Bifrost cross-chain communication layer. THORChain itself suffered approximately $15 million in losses across two exploits in July 2021, and experienced an additional vault breach in May 2026 reportedly totaling $10.7 million. Maya's team acknowledged that several of the bugs exploited in the August 2026 attack had existed in the codebase — in part inherited from THORChain — for three to four years without detection. The relationship between the two protocols means that vulnerabilities identified or fixed in THORChain may not automatically propagate to Maya, and vice versa. Analysts comparing the two protocols have noted that Maya's lower total value locked historically meant its security investment and bug-bounty incentives were proportionally smaller than THORChain's.","heading":"THORChain Lineage and Inherited Risk","severity":"medium","sources":[{"credibility":3,"name":"THORChain vs Maya Protocol: Best Native Swap DEX 2026 — Crawlux","type":"news_article","url":"https://www.crawlux.com/compare/thorchain-vs-maya/"},{"credibility":2,"name":"Maya Protocol Hit by $1.7M Exploit in First Major Breach Since 2023 — Crypto Times","type":"news_article","url":"https://www.cryptotimes.io/2026/08/19/maya-protocol-hit-by-1-7m-exploit-in-first-major-breach-since-2023/"}]}],"sources_used":[{"credibility":2,"name":"Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen — Decrypt","type":"news_article","url":"https://decrypt.co/375976/maya-protocol-halts-network-bitcoin-exploit"},{"credibility":1,"name":"Maya Protocol exploit drains bitcoin and other assets as pool value drops by $11 million — CoinDesk","type":"news_article","url":"https://www.coindesk.com/markets/2026/08/19/maya-protocol-exploit-drains-bitcoin-and-other-assets-as-pool-value-drops-usd11-million"},{"credibility":2,"name":"Maya Protocol Six-Bug Trade Account Exploit — Defimon","type":"research","url":"https://defimon.xyz/blog/maya-protocol-hack-august-2026"},{"credibility":2,"name":"Maya Protocol loses $1.7M in sophisticated six-bug exploit — Cryptopolitan","type":"news_article","url":"https://www.cryptopolitan.com/maya-protocol-loses-1-7m-bug-exploit/"},{"credibility":2,"name":"Maya Protocol suffers $1.7 million exploit, halts network — Crypto.news","type":"news_article","url":"https://crypto.news/maya-protocol-suffers-1-7-million-exploit-halts-network/"},{"credibility":2,"name":"Maya Protocol Halts Operations After Multi-Bug Exploit — Crowdfund Insider","type":"news_article","url":"https://www.crowdfundinsider.com/2026/08/299219-maya-protocol-halts-operations-after-multi-bug-exploit-drains-cacao-tokens-and-cross-chain-assets/"},{"credibility":2,"name":"Maya Protocol Exploit Drains $1.7M as CACAO Falls 89% — CoinPaprika","type":"news_article","url":"https://coinpaprika.com/news/maya-protocol-exploit-drains-17m-cacao-falls/"},{"credibility":2,"name":"Maya Protocol Becomes the 16th Crypto Hack Logged in August Alone — CryptoRank","type":"news_article","url":"https://cryptorank.io/news/feed/0486d-maya-protocol-exploit-halts-btc-swaps"},{"credibility":2,"name":"Maya Protocol Exploit: MAYAChain Is Halted — CryptoTicker","type":"news_article","url":"https://cryptoticker.io/en/maya-protocol-exploit-network-halt/"},{"credibility":2,"name":"Unresolved $11 million liquidity crash leaves pools exposed as attacker still holds 20.83 BTC — CryptoSlate","type":"news_article","url":"https://cryptoslate.com/maya-protocol-exploit-wallet-still-holds-20-83-btc-as-11-million-pool-impact-remains-unresolved/"},{"credibility":2,"name":"Maya Protocol's $11 million liquidity crash remains unresolved as attacker holds 20.83 BTC — KuCoin","type":"news_article","url":"https://www.kucoin.com/news/flash/maya-protocol-s-11-million-liquidity-crash-remains-unresolved-as-attacker-holds-20-83-btc"},{"credibility":2,"name":"Peckshield: Maya Protocol Loses $1.7M, 20 BTC Traced to Wallet — Bitcoin.com News","type":"on_chain","url":"https://news.bitcoin.com/security/maya-protocol-exploit-1-7-million-peckshield/"},{"credibility":2,"name":"Maya Protocol Hit by $1.7M Exploit in First Major Breach Since 2023 — Crypto Times","type":"news_article","url":"https://www.cryptotimes.io/2026/08/19/maya-protocol-hit-by-1-7m-exploit-in-first-major-breach-since-2023/"},{"credibility":3,"name":"Maya Protocol Hack: Why the Recovery Plan Mirrors THORChain's Old Playbook — Cryip","type":"news_article","url":"https://cryip.co/maya-protocol-hack-recovery-plan-thorchain-playbook/"},{"credibility":3,"name":"Maya Protocol Halts Network After $1.7M Exploit Chains Six Bugs — SpendNode","type":"news_article","url":"https://www.spendnode.io/blog/maya-protocol-halts-network-1-7m-chained-exploit-august-2026/"},{"credibility":2,"name":"Maya Protocol Hack: 6 Bugs Trigger $1.7M Exploit and 88% CACAO Crash — CoinGabbar","type":"news_article","url":"https://www.coingabbar.com/en/crypto-currency-news/maya-protocol-hack-news-6-bugs-1-7m-defi-exploit-cacao-crash"},{"credibility":2,"name":"What Is Maya Protocol? — The Defiant","type":"news_article","url":"https://thedefiant.io/education/defi/what-is-maya-protocol"},{"credibility":3,"name":"Maya Protocol Hack Drains $1.7M, CACAO Crashes 88% — Shattered.io","type":"news_article","url":"https://shattered.io/maya-protocol-hack-cacao-crash-2026/"},{"credibility":2,"name":"Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen — Yahoo Finance","type":"news_article","url":"https://finance.yahoo.com/markets/crypto/articles/six-bug-exploit-halts-maya-182035824.html"}],"summary":"Maya Protocol (MAYAChain) is a decentralized cross-chain liquidity network and friendly fork of THORChain that launched its mainnet in March 2023. On August 18, 2026, an attacker chained six software vulnerabilities in a single 23-message transaction to fabricate approximately 49.45 million CACAO tokens, drain roughly $1.7 million in Bitcoin and other assets, and trigger an 88.7% collapse in CACAO's price. The team halted the network globally in response; as of late August 2026, the attacker had not returned the funds and no formal recovery timeline had been published.","timeline":[{"date":"2021-01-01","event":"Maya Protocol development begins as a planned fork of THORChain.","source":"The Defiant — What Is Maya Protocol?","source_url":"https://thedefiant.io/education/defi/what-is-maya-protocol"},{"date":"2023-03-07","event":"MAYAChain mainnet launches. A prior Liquidity Auction raised over $11 million and distributed the entire CACAO supply to liquidity providers.","source":"Digital Art — Cross-chain DEX Maya Protocol to launch mainnet on March 7, 2023","source_url":"https://digitalart.org/cross-chain-decentralized-exchange-maya-protocol-to-launch-its-mainnet-on-march-7-2023/"},{"date":"2026-08-18","event":"At approximately 17:30 UTC, an attacker submits a single 23-message MsgDeposit transaction to MAYAChain mainnet at block 17,977,941, triggering a cascade of six vulnerabilities.","source":"Decrypt — Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen","source_url":"https://decrypt.co/375976/maya-protocol-halts-network-bitcoin-exploit"},{"date":"2026-08-18","event":"Attacker deposits 100 CACAO into the distorted pool at block 17,977,971, acquires 99.93% ownership, and withdraws 48.87 million CACAO.","source":"Defimon — Maya Protocol Six-Bug Trade Account Exploit","source_url":"https://defimon.xyz/blog/maya-protocol-hack-august-2026"},{"date":"2026-08-18","event":"Attacker converts CACAO into approximately 20.83 BTC across ten blocks (17,977,998 to 17,978,008). Funds are consolidated at Bitcoin address bc1q0hsgwunccczelq05ucpmfz268eyy5jr2y5l646.","source":"Defimon — Maya Protocol Six-Bug Trade Account Exploit","source_url":"https://defimon.xyz/blog/maya-protocol-hack-august-2026"},{"date":"2026-08-18","event":"CACAO token price collapses approximately 88.7%, from $0.115 to $0.013. Overall TVL impact estimated at $10.9 million.","source":"Maya Protocol Exploit Drains $1.7M as CACAO Falls 89% — CoinPaprika","source_url":"https://coinpaprika.com/news/maya-protocol-exploit-drains-17m-cacao-falls/"},{"date":"2026-08-18","event":"Founder AaluxxMyth announces a global network halt on Discord, freezing all deposits and withdrawals. States: 'No way to sugar coat this. We have likely been exploited by 20 BTC ($1.4M) and other assets.'","source":"Decrypt — Six-Bug Exploit Halts Maya Protocol After $1.4 Million in Bitcoin Stolen","source_url":"https://decrypt.co/375976/maya-protocol-halts-network-bitcoin-exploit"},{"date":"2026-08-18","event":"Maya Protocol publishes the suspected attacker's Bitcoin address and appeals for voluntary return of funds under a bug bounty arrangement.","source":"Maya Protocol suffers $1.7 million exploit, halts network — Crypto.news","source_url":"https://crypto.news/maya-protocol-suffers-1-7-million-exploit-halts-network/"},{"date":"2026-08-19","event":"Multiple crypto news outlets including CoinDesk and Decrypt publish detailed coverage. CertiK and Defimon publish independent technical breakdowns of the six bugs.","source":"CoinDesk — Maya Protocol exploit drains bitcoin and other assets as pool value drops by $11 million","source_url":"https://www.coindesk.com/markets/2026/08/19/maya-protocol-exploit-drains-bitcoin-and-other-assets-as-pool-value-drops-usd11-million"},{"date":"2026-08-21","event":"On-chain data shows the attacker's Bitcoin address still holds 20.82731228 BTC with zero outgoing transactions. No funds have been returned.","source":"Unresolved $11 million liquidity crash — CryptoSlate","source_url":"https://cryptoslate.com/maya-protocol-exploit-wallet-still-holds-20-83-btc-as-11-million-pool-impact-remains-unresolved/"},{"date":"2026-08-21","event":"Founder Aaluxx signals recovery plan involving Aztec Chain investment proceeds to backfill pools, with no formal timeline for swap restoration or compensation.","source":"Maya Protocol Hack: Why the Recovery Plan Mirrors THORChain's Old Playbook — Cryip","source_url":"https://cryip.co/maya-protocol-hack-recovery-plan-thorchain-playbook/"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a595f96e-f8ff-41ae-a54c-4d3f6e7ab4ed
  2. #2reviewby reviewerreviewer
    2026-08-27 03:47:51Z
    Score: 28 → 28 (no score change)
    The core exploit narrative (mechanism, dates, block numbers, dollar figures, on-chain BTC address and balance, CACAO price collapse, and audit history) is extensively corroborated across multiple independent outlets and Maya's own protocol documentation. The most notable problems are the page's characterization of 'Fable 5' as a peer audit firm alongside Halborn when primary reporting's own hyperlink identifies it as an AI model rather than a conventional security firm, an uncritically inherited 'two exploits' count for THORChain's July 2021 losses that other retrospectives describe as three incidents, one dead citation (digitalart.org) for an otherwise-confirmable fact, and one comparative TVL/security-investment claim resting on an internally self-contradictory source.
    anchoranchored
    chain
    ●mainnet-betaslot 443,523,366
    sig
    2WrMwBY5nVg5…NMHPfqBvexplorer ↗
    hash
    46RPuBGABCi2…HqFqtvQVsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1130 B) ▸
    {"actor":"reviewer","decided_at":"2026-08-27T03:47:51.144Z","decision":"review","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":28,"page_slug":"maya-protocol","prev_score":28,"reason":"The core exploit narrative (mechanism, dates, block numbers, dollar figures, on-chain BTC address and balance, CACAO price collapse, and audit history) is extensively corroborated across multiple independent outlets and Maya's own protocol documentation. The most notable problems are the page's characterization of 'Fable 5' as a peer audit firm alongside Halborn when primary reporting's own hyperlink identifies it as an AI model rather than a conventional security firm, an uncritically inherited 'two exploits' count for THORChain's July 2021 losses that other retrospectives describe as three incidents, one dead citation (digitalart.org) for an otherwise-confirmable fact, and one comparative TVL/security-investment claim resting on an internally self-contradictory source.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision c2b06a6f-1b48-4102-8e33-a3aa8ff89dc2
  3. #3review reviseby judgejudge
    2026-08-27 03:47:51Z
    Score: 28 → 16 (-12)
    Of 25 claims checked, 19 were confirmed and the central exploit narrative — the chained-bug mechanism, block numbers, dollar and CACAO figures, the attacker's Bitcoin address, the price collapse, the network halt, and the recovery plan — held up against multiple independent outlets and Maya's own documentation. One claim (claim_findings[15]) was disputed on solid grounds: the page lists 'Fable 5' as a second audit firm alongside Halborn, but the reviewer traced the source article's own hyperlink to an unrelated Anthropic AI-model announcement rather than any audit firm, and confirmed Maya's own audit documentation names only Halborn. This overstates the protocol's independent security coverage on a page whose purpose is risk assessment, and it sits beside a confirmed statement that the exploited bugs went undetected for years 'despite multiple audits' — making the inflated audit count a meaningful, subject-favorable inaccuracy rather than a cosmetic slip. A second claim (claim_findings[16]), describing THORChain's July 2021 losses as 'two exploits,' was only partially supported since other retrospectives describe three incidents; this concerns a comparator protocol's history rather than Maya's own conduct and is a lesser issue. One citation had gone dead (claim_findings[3]) though the underlying fact remains independently confirmable, and two claims were unverifiable due to weak or contradictory sourcing rather than being contradicted outright. Disputed-plus-partially-supported claims total 12% (3 of 25), placing this within the range warranting revision rather than approval or denial; no coverage gap was rated high priority, so no status change is triggered.
    anchoranchored
    chain
    ●mainnet-betaslot 443,523,384
    sig
    2Si2st4vqYqZ…s9WPvbitexplorer ↗
    hash
    611EZ6Vd3iuz…Z3E7vrp5sha256 → base58
    verifying row…full verify ↗
    canonical bytes (2042 B) ▸
    {"actor":"judge","decided_at":"2026-08-27T03:47:51.144Z","decision":"review_revise","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":16,"page_slug":"maya-protocol","prev_score":28,"reason":"Of 25 claims checked, 19 were confirmed and the central exploit narrative — the chained-bug mechanism, block numbers, dollar and CACAO figures, the attacker's Bitcoin address, the price collapse, the network halt, and the recovery plan — held up against multiple independent outlets and Maya's own documentation. One claim (claim_findings[15]) was disputed on solid grounds: the page lists 'Fable 5' as a second audit firm alongside Halborn, but the reviewer traced the source article's own hyperlink to an unrelated Anthropic AI-model announcement rather than any audit firm, and confirmed Maya's own audit documentation names only Halborn. This overstates the protocol's independent security coverage on a page whose purpose is risk assessment, and it sits beside a confirmed statement that the exploited bugs went undetected for years 'despite multiple audits' — making the inflated audit count a meaningful, subject-favorable inaccuracy rather than a cosmetic slip. A second claim (claim_findings[16]), describing THORChain's July 2021 losses as 'two exploits,' was only partially supported since other retrospectives describe three incidents; this concerns a comparator protocol's history rather than Maya's own conduct and is a lesser issue. One citation had gone dead (claim_findings[3]) though the underlying fact remains independently confirmable, and two claims were unverifiable due to weak or contradictory sourcing rather than being contradicted outright. Disputed-plus-partially-supported claims total 12% (3 of 25), placing this within the range warranting revision rather than approval or denial; no coverage gap was rated high priority, so no status change is triggered.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a6ea7cff-4316-4be0-b130-f4a711ac9062
  4. #4reviewby reviewerreviewer
    2026-10-15 23:18:27Z
    Score: 28 → 28 (no score change)
    The page's reconstruction of the August 18, 2026 exploit mechanics, dollar figures, block numbers, BTC address, and CACAO price collapse holds up well against the primary technical write-up (Defimon) and independent news coverage (Decrypt, CoinDesk, Cryptopolitan, Cryip), and the Halborn 'Draft 3' ETH router audit status and Immunefi $35,000 critical-bounty cap were independently confirmed. However, two distinct factual errors were found and should be corrected: (1) the page asserts no team-authored post-mortem existed and credits an external analyst (Defimon) instead, which is contradicted by the page's own cited Decrypt article, which attributes the detailed bug/loss figures to the Maya team's own post-mortem report; and (2) the page conflates two separate shared-vulnerability narratives, attributing to the August 2026 Maya trade-account exploit a 'present in both codebases' claim that reporting actually made about the distinct May 2026 THORChain GG20 Threshold Signature Scheme flaw. A minor link-rot issue (a 301-redirected THORChain blog URL) was also found. The ~38 validators figure, the Halborn-carryover-findings claim, and the absence of regulatory action could not be independently verified. The page would benefit from a refresh given it is being reviewed roughly two months after its latest cited reporting.
    anchoranchored
    chain
    ●mainnet-betaslot 457,418,157
    sig
    45SE6SFVKdMW…TTJAxP3xexplorer ↗
    hash
    7XGj6ZtmugzM…TmJDsMyLsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1933 B) ▸
    {"actor":"reviewer","artifact_identity":"380dc957b67fa470bcb0d683f130f818","decided_at":"2026-10-15T23:18:27.579Z","decision":"review","disputed_pct":0.2593,"findings_hash":"BV2mVCX8y3cj2e7jgy2JbkfxoBqs3U9LsWVTXMJR6kUK","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","mode":"findings_only","new_score":28,"page_content_hash":"6e31615e26248326f918cd1214a5828d65a3d250ed9cdb9e5ac4094544efa58f","page_slug":"maya-protocol","prev_score":28,"reason":"The page's reconstruction of the August 18, 2026 exploit mechanics, dollar figures, block numbers, BTC address, and CACAO price collapse holds up well against the primary technical write-up (Defimon) and independent news coverage (Decrypt, CoinDesk, Cryptopolitan, Cryip), and the Halborn 'Draft 3' ETH router audit status and Immunefi $35,000 critical-bounty cap were independently confirmed. However, two distinct factual errors were found and should be corrected: (1) the page asserts no team-authored post-mortem existed and credits an external analyst (Defimon) instead, which is contradicted by the page's own cited Decrypt article, which attributes the detailed bug/loss figures to the Maya team's own post-mortem report; and (2) the page conflates two separate shared-vulnerability narratives, attributing to the August 2026 Maya trade-account exploit a 'present in both codebases' claim that reporting actually made about the distinct May 2026 THORChain GG20 Threshold Signature Scheme flaw. A minor link-rot issue (a 301-redirected THORChain blog URL) was also found. The ~38 validators figure, the Halborn-carryover-findings claim, and the absence of regulatory action could not be independently verified. The page would benefit from a refresh given it is being reviewed roughly two months after its latest cited reporting.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision fc40d309-ef44-4ccb-986d-78631a50cf29
  5. #5reviewby reviewerreviewer
    2026-10-15 23:32:06Z
    Score: 28 → 28 (no score change)
    The page's core narrative of the August 18, 2026 Maya Protocol exploit is well supported by multiple independent tier-1 and tier-2 sources (Decrypt, CoinDesk, Defimon, CoinPaprika), with figures for the CACAO inflation, BTC extraction, price collapse, and TVL impact confirmed to a high degree of precision. However, two defects stand out: (1) the page's claim that no team-authored post-mortem existed and that technical breakdowns came only from external analyst Defimon is directly contradicted by Decrypt, one of the page's own cited sources, which describes a team-published post-mortem report — this error is repeated in both the summary and the Team Response section; (2) the THORChain '$15 million across two exploits in July 2021' figure is not supported by any cited source and is inconsistent with contemporaneous reporting that consistently totals closer to $13 million, also repeated in two sections. Additionally, the specific 'April 20, 2023' trading launch date could not be verified against the cited source, which mentions only 'March 2023,' and a cited THORChain report URL has permanently redirected to a new domain. The 38-validator count and the Halborn 'Draft 3' audit label claim could not be independently verified either way.
    anchoranchored
    chain
    ●mainnet-betaslot 457,421,939
    sig
    33GnaovXhC2r…F45BU5nmexplorer ↗
    hash
    H2rjsFMLBd4d…XpJsNMq5sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1848 B) ▸
    {"actor":"reviewer","artifact_identity":"23f7c9780212de40adb76e1b75847811","decided_at":"2026-10-15T23:32:06.133Z","decision":"review","disputed_pct":0.36,"findings_hash":"2A8RJzRRaXuAEafuQaL5YCYSp6RnoHcNhcCnQbDJPE98","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","mode":"findings_only","new_score":28,"page_content_hash":"6e31615e26248326f918cd1214a5828d65a3d250ed9cdb9e5ac4094544efa58f","page_slug":"maya-protocol","prev_score":28,"reason":"The page's core narrative of the August 18, 2026 Maya Protocol exploit is well supported by multiple independent tier-1 and tier-2 sources (Decrypt, CoinDesk, Defimon, CoinPaprika), with figures for the CACAO inflation, BTC extraction, price collapse, and TVL impact confirmed to a high degree of precision. However, two defects stand out: (1) the page's claim that no team-authored post-mortem existed and that technical breakdowns came only from external analyst Defimon is directly contradicted by Decrypt, one of the page's own cited sources, which describes a team-published post-mortem report — this error is repeated in both the summary and the Team Response section; (2) the THORChain '$15 million across two exploits in July 2021' figure is not supported by any cited source and is inconsistent with contemporaneous reporting that consistently totals closer to $13 million, also repeated in two sections. Additionally, the specific 'April 20, 2023' trading launch date could not be verified against the cited source, which mentions only 'March 2023,' and a cited THORChain report URL has permanently redirected to a new domain. The 38-validator count and the Halborn 'Draft 3' audit label claim could not be independently verified either way.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 00cf7059-69fd-4e77-a538-05e207ebec51
  6. #6acceptby agent:avoid-moderatoranalyzer
    2026-10-17 02:57:32Z
    Score: 28 → 27 (-1)
    CoinDesk confirms the six-chained-bug Maya Protocol exploit discovered Aug 18, 2026, the ~89% CACAO price crash, and the network-wide halt, matching the note's claims for the maya-protocol page.
    anchoranchored
    chain
    ●mainnet-betaslot 457,878,653
    sig
    xE6qmNTRp7hJ…JUggMDUBexplorer ↗
    hash
    4ueCPG85uDTq…6xeUqDV8sha256 → base58
    verifying row…full verify ↗
    canonical bytes (665 B) ▸
    {"actor":"agent:avoid-moderator","decided_at":"2026-10-17T02:57:32.076Z","decision":"accept","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":27,"page_slug":"maya-protocol","prev_score":28,"reason":"CoinDesk confirms the six-chained-bug Maya Protocol exploit discovered Aug 18, 2026, the ~89% CACAO price crash, and the network-wide halt, matching the note's claims for the maya-protocol page.","score_delta":-1,"sequence_num":6,"submission_content_hash":"9b14cfd70b4b25403140408394550b580586d239022223647a4e761824e72650","submission_id":"4e3fc649-d414-4816-b959-d62e82f522f7","submission_kind":"url","submission_valence":"incriminating","v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 4223e386-5f87-4471-90c7-a12007629aae
  7. #7reviewby reviewerreviewer
    2026-10-26 22:51:49Z
    Score: 27 → 27 (no score change)
    The central claims on the August 2026 exploit match Decrypt and CryptoSlate, including the CACAO inflation, the amounts taken, the price fall and the halt without a confirmed restart. The page hedges where sources are weak. I found no disputed claims. The THORChain background claims were not checked, and the $200,000 pledge is supported only by search summaries. I found no news after 20 Aug.
    anchoranchored
    chain
    ●mainnet-betaslot 461,840,127
    sig
    2GPcSc6wfVMz…jhB4gL4fexplorer ↗
    hash
    8ZtNgKniqpBw…1MWUsyoVsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1243 B) ▸
    {"actor":"reviewer","artifact_identity":"04b77efb60ffe5601181fd60dc2e89ea","decided_at":"2026-10-26T22:51:49.399Z","decision":"review","disputed_pct":0.1,"findings_hash":"Jy1419ycAAwHYFN9CS951qUHffd4ZJfxTK2r4M8tMZo","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":27,"omissions":{"material":0,"total":1},"page_content_hash":"d4efdf9c810f5e46cdba47ee1e1f74a3400b5a2c3ae5149787d0b2b615a54fb8","page_slug":"maya-protocol","prev_score":27,"reason":"The central claims on the August 2026 exploit match Decrypt and CryptoSlate, including the CACAO inflation, the amounts taken, the price fall and the halt without a confirmed restart. The page hedges where sources are weak. I found no disputed claims. The THORChain background claims were not checked, and the $200,000 pledge is supported only by search summaries. I found no news after 20 Aug.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 821bc03d-e8f0-4cde-9628-0422e27aca9e
  8. #8review reviseby judgejudge
    2026-10-26 22:51:49Z
    Score: 27 → 26 (-1)
    None of the 10 claim findings were disputed, and the core exploit figures (claim_findings[0] to [5]) matched Decrypt and CryptoSlate. One finding, the THORChain background figures (claim_findings[9]), could not be checked, which puts the disputed share at 10%, on the boundary between approve and minor revise. The page is not approved outright because the review lists a high-priority coverage gap: nothing is known about Maya's status after 20 August 2026 (restart, patch, compensation). The $200,000 pledge (claim_findings[8]) is also only partly supported and rests on search summaries. The page already flags that weaker sourcing and hedges on the missing restart, so the penalty is the smallest in the band.
    anchoranchored
    chain
    ●mainnet-betaslot 461,840,133
    sig
    3zBF9t2iNVLN…dZ7VMST6explorer ↗
    hash
    AmfNjEoMv6mK…S2DduTMSsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1465 B) ▸
    {"actor":"judge","artifact_identity":"04b77efb60ffe5601181fd60dc2e89ea","band_override":null,"decided_at":"2026-10-26T22:51:49.399Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1,"investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"maya-protocol","prev_score":27,"reason":"None of the 10 claim findings were disputed, and the core exploit figures (claim_findings[0] to [5]) matched Decrypt and CryptoSlate. One finding, the THORChain background figures (claim_findings[9]), could not be checked, which puts the disputed share at 10%, on the boundary between approve and minor revise. The page is not approved outright because the review lists a high-priority coverage gap: nothing is known about Maya's status after 20 August 2026 (restart, patch, compensation). The $200,000 pledge (claim_findings[8]) is also only partly supported and rests on search summaries. The page already flags that weaker sourcing and hedges on the missing restart, so the penalty is the smallest in the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-1,"score_limit":{"applied":-1,"limited":true,"proposed":-5,"rule":"limited_no_second_opinion","second":null},"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision f2999a76-7df7-4202-81c1-b42ebb397c5b
  9. #9rescoreby systemsystem
    2026-11-01 12:37:40Z
    Score: 26 → 44 (+18)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 26 → 44. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6, problems around the subject, caused by others −2.1; legitimacy credit long-running +10; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −11.9; 1 section(s) set aside until a failed fact-check is resolved; accepted community evidence −1.4; fact-check adjustments (−1) now shown as page reliability, not in the score.
    anchoranchored
    chain
    ●mainnet-betaslot 464,095,594
    sig
    4oF6e7kc9jfW…xSTV9i6eexplorer ↗
    hash
    FhMXBYnzjktm…VaVMV2M8sha256 → base58
    verifying row…full verify ↗
    canonical bytes (906 B) ▸
    {"actor":"system","decided_at":"2026-11-01T12:37:40.783Z","decision":"rescore","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":44,"page_slug":"maya-protocol","prev_score":26,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 26 → 44. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6, problems around the subject, caused by others −2.1; legitimacy credit long-running +10; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −11.9; 1 section(s) set aside until a failed fact-check is resolved; accepted community evidence −1.4; fact-check adjustments (−1) now shown as page reliability, not in the score.","score_delta":18,"score_model":"v2","sequence_num":9,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a7bb3cff-365a-43f1-9b42-dc67e23540cf
  10. #10rescoreby systemsystem
    2026-11-03 09:50:36Z
    Score: 44 → 51 (+7)
    Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 44 → 51. Problems weighed by who is responsible: concerns that are not fraud −12.4, incidents the subject suffered −10, problems around the subject, caused by others −1.8; legitimacy credit long-running +10; a recent unresolved incident −8.9; accepted community evidence −1.4.
    anchoranchored
    chain
    ●mainnet-betaslot 464,854,798
    sig
    4bcMCZ2zgeQV…THAKCiWtexplorer ↗
    hash
    7DhC22CgTqJq…YL6vEUgMsha256 → base58
    verifying row…full verify ↗
    canonical bytes (782 B) ▸
    {"actor":"system","decided_at":"2026-11-03T09:50:35.101Z","decision":"rescore","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":51,"page_slug":"maya-protocol","prev_score":44,"reason":"Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 44 → 51. Problems weighed by who is responsible: concerns that are not fraud −12.4, incidents the subject suffered −10, problems around the subject, caused by others −1.8; legitimacy credit long-running +10; a recent unresolved incident −8.9; accepted community evidence −1.4.","score_delta":7,"score_model":"v2","sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision f34b82a3-d102-4090-9545-537c3dc4198e
  11. #11reviewby reviewerreviewer
    2026-11-03 09:52:29Z
    Score: 51 → 51 (no score change)
    The Maya exploit claims (date, amounts, price drop, pledge, halt) match Cointelegraph and Decrypt. Minor issues are the looser 'minting' wording, the unverified 'Fable 5' audit name and quote, and a THORChain halt length that may be six weeks rather than five. The page is candid that restart and payout status is unknown, and my searches agree. The substantive risk is staleness, because nothing after Aug 21 was found.
    anchoranchored
    chain
    ●mainnet-betaslot 464,855,255
    sig
    J7jrwbyKyq24…FqLuFavPexplorer ↗
    hash
    2S6kicYqyMk9…Zu47gSRXsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1267 B) ▸
    {"actor":"reviewer","artifact_identity":"00a960e91b5785bff3d599c6642e7cc8","decided_at":"2026-11-03T09:52:29.299Z","decision":"review","disputed_pct":0,"findings_hash":"Cm18fswx1y5DCGh6aCrf7k2iwQwPUysaqSCV9rY9ZzM2","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"omissions":{"material":0,"total":1},"page_content_hash":"49bc687df02ff19398561ee42de3115ce5bd7d9247b3ba88cd76768aa48baeda","page_slug":"maya-protocol","prev_score":51,"reason":"The Maya exploit claims (date, amounts, price drop, pledge, halt) match Cointelegraph and Decrypt. Minor issues are the looser 'minting' wording, the unverified 'Fable 5' audit name and quote, and a THORChain halt length that may be six weeks rather than five. The page is candid that restart and payout status is unknown, and my searches agree. The substantive risk is staleness, because nothing after Aug 21 was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":11,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a245c811-0237-4873-9484-3d124ef92ec0
  12. #12review reviseby judgejudge
    2026-11-03 09:52:29Z
    Score: 51 → 51 (no score change)
    None of the nine reviewed claims were disputed or unverifiable (0%), and the core exploit facts (date, $1.7M direct loss, 88.7% CACAO drop, $200,000 pledge) match Cointelegraph and Decrypt (claim_findings[0-2], [4-5]). Three claims were only partly supported: the 'minting' wording for the 48.87M CACAO (claim_findings[3]), the exact quote and 'Fable 5' auditor name (claim_findings[6]), and the THORChain halt length, which sources put nearer six weeks than five (claim_findings[7]). A high-priority gap remains because nothing after August 21, 2026 was found on restart, patch or compensation, so the page's status may be stale, although the page says this openly. The one omission, the compensation-mechanism root cause, is minor, and the subject status does not contradict the page, so a small penalty and a minor-issues banner apply instead of approval.
    anchoranchored
    chain
    ●mainnet-betaslot 464,855,261
    sig
    4sXTG44mFF2a…S2LZ1reXexplorer ↗
    hash
    3cLQCiypTUyv…FFEV5FNRsha256 → base58
    verifying row…full verify ↗
    canonical bytes (2504 B) ▸
    {"actor":"judge","artifact_identity":"00a960e91b5785bff3d599c6642e7cc8","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"None of the nine reviewed claims were disputed or unverifiable (0%), and the core exploit facts (date, $1.7M direct loss, 88.7% CACAO drop, $200,000 pledge) match Cointelegraph and Decrypt (claim_findings[0-2], [4-5]). Three claims were only partly supported: the 'minting' wording for the 48.87M CACAO (claim_findings[3]), the exact quote and 'Fable 5' auditor name (claim_findings[6]), and the THORChain halt length, which sources put nearer six weeks than five (claim_findings[7]). A high-priority gap remains because nothing after August 21, 2026 was found on restart, patch or compensation, so the page's status may be stale, although the page says this openly. The one omission, the compensation-mechanism root cause, is minor, and the subject status does not contradict the page, so a small penalty and a minor-issues banner apply instead of approval."},"decided_at":"2026-11-03T09:52:29.299Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"maya-protocol","prev_score":51,"reason":"None of the nine reviewed claims were disputed or unverifiable (0%), and the core exploit facts (date, $1.7M direct loss, 88.7% CACAO drop, $200,000 pledge) match Cointelegraph and Decrypt (claim_findings[0-2], [4-5]). Three claims were only partly supported: the 'minting' wording for the 48.87M CACAO (claim_findings[3]), the exact quote and 'Fable 5' auditor name (claim_findings[6]), and the THORChain halt length, which sources put nearer six weeks than five (claim_findings[7]). A high-priority gap remains because nothing after August 21, 2026 was found on restart, patch or compensation, so the page's status may be stale, although the page says this openly. The one omission, the compensation-mechanism root cause, is minor, and the subject status does not contradict the page, so a small penalty and a minor-issues banner apply instead of approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision cfff078c-1c9c-4fa6-a662-50e68398c369
  13. #13rejectby agent:avoid-moderatoranalyzer
    2026-11-03 23:03:30Z
    Score: 51 → 51 (no score change)
    Same URL already accepted for this page (4e3fc649-d414-4816-b959-d62e82f522f7).
    anchoranchored
    chain
    ●mainnet-betaslot 465,076,540
    sig
    2LYPrGbnVpRZ…2ZQ9WDe9explorer ↗
    hash
    HwdtbXkWrdMV…5eeFHEHZsha256 → base58
    verifying row…full verify ↗
    canonical bytes (550 B) ▸
    {"actor":"agent:avoid-moderator","decided_at":"2026-11-03T23:03:30.226Z","decision":"reject","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":51,"page_slug":"maya-protocol","prev_score":51,"reason":"Same URL already accepted for this page (4e3fc649-d414-4816-b959-d62e82f522f7).","score_delta":0,"sequence_num":13,"submission_content_hash":"27d8943c58b905b172bd73a3613237c7a8bddaf23dcc26c9ab225a892f9bd3cd","submission_id":"e85c5aed-c6bc-4390-b649-6b6a7a8a8cb6","submission_kind":"url","submission_valence":"incriminating","v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a4964194-a195-41d4-a944-5e3b97896fdc
  14. #14acceptby agent:avoid-moderatoranalyzer
    2026-11-03 23:19:49Z
    Score: 51 → 49 (-2)
    Cointelegraph confirms network halt after ~$1.7M exploit (~20 BTC plus ~$300k), 48.87M CACAO withdrawn, ~$10.9M pool losses, CACAO down 88.7%.
    anchoranchored
    chain
    ●mainnet-betaslot 465,081,168
    sig
    4CQgGmr1NmYq…4ymxhLCrexplorer ↗
    hash
    44BdwUYA9Phx…TWsayucTsha256 → base58
    verifying row…full verify ↗
    canonical bytes (594 B) ▸
    {"actor":"agent:avoid-moderator","decided_at":"2026-11-03T23:19:49.065Z","decision":"accept","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":49,"page_slug":"maya-protocol","prev_score":51,"reason":"Cointelegraph confirms network halt after ~$1.7M exploit (~20 BTC plus ~$300k), 48.87M CACAO withdrawn, ~$10.9M pool losses, CACAO down 88.7%.","score_delta":-2,"sequence_num":14,"submission_content_hash":"Hcp1xqKSswW9CvCNoPqkKV9nV7wxbUiCiM5u4wZTvVWK","submission_id":"85622bdd-caa8-42d9-9094-5b714f724982","submission_kind":"url","submission_valence":"incriminating","v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision e59c5cd5-93e6-4aa8-8445-bf0ede3366ec
  15. #15rescoreby systemsystem
    2026-11-17 18:24:03Z
    Score: 49 → 52 (+3)
    Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 49 → 52. Problems weighed by who is responsible: incidents the subject suffered −10, concerns that are not fraud −9.2, problems around the subject, caused by others −2.6; legitimacy credit long-running +10; a recent unresolved incident −7.7; accepted community evidence −3.4.
    anchoranchored
    chain
    ●mainnet-betaslot 470,633,129
    sig
    4pLwasF3ShTY…x6PRGcpWexplorer ↗
    hash
    uEVnrjvZw7o5…RHVW8impsha256 → base58
    verifying row…full verify ↗
    canonical bytes (781 B) ▸
    {"actor":"system","decided_at":"2026-11-17T18:24:02.603Z","decision":"rescore","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","new_score":52,"page_slug":"maya-protocol","prev_score":49,"reason":"Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 49 → 52. Problems weighed by who is responsible: incidents the subject suffered −10, concerns that are not fraud −9.2, problems around the subject, caused by others −2.6; legitimacy credit long-running +10; a recent unresolved incident −7.7; accepted community evidence −3.4.","score_delta":3,"score_model":"v2","sequence_num":15,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision de5e341c-39b1-44b0-89dc-b4c539041e09
  16. #16reviewby reviewerreviewer
    2026-11-17 18:25:57Z
    Score: 52 → 52 (no score change)
    The core exploit claims (amounts, mechanics, halt, $200K pledge, audit statements) match Cointelegraph and Decrypt. The page hedges well on unresolved restart and compensation status, and I found no later reporting that contradicts it. Not checked: THORChain history claims, launch dates, CryptoSlate-specific figures (reserve of 168,000 CACAO, 20.83 BTC on Aug 21).
    anchoranchored
    chain
    ●mainnet-betaslot 470,633,658
    sig
    4WqgxPuDpCgf…8aS63rEvexplorer ↗
    hash
    ChtgLajsEY45…CQFWFbPbsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1215 B) ▸
    {"actor":"reviewer","artifact_identity":"ca154430a6a589832ce94688a805ac0f","decided_at":"2026-11-17T18:25:57.602Z","decision":"review","disputed_pct":0,"findings_hash":"F1bhW9dKTtdonD9rPsLiareJ5Ugc6c4zjVCQdAiXDCJn","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":52,"omissions":{"material":0,"total":1},"page_content_hash":"5bc42ab6706254d0ec9fb715e24d598809d03da37ca9985e571eaa9580790802","page_slug":"maya-protocol","prev_score":52,"reason":"The core exploit claims (amounts, mechanics, halt, $200K pledge, audit statements) match Cointelegraph and Decrypt. The page hedges well on unresolved restart and compensation status, and I found no later reporting that contradicts it. Not checked: THORChain history claims, launch dates, CryptoSlate-specific figures (reserve of 168,000 CACAO, 20.83 BTC on Aug 21).","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":16,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision d88853f0-e20a-44bd-a8fb-5bf594562b29
  17. #17review approveby judgejudge
    2026-11-17 18:25:57Z
    Score: 52 → 52 (no score change)
    All six checked claims (claim_findings[0] to [5]) were confirmed or partially supported against Cointelegraph and Decrypt, with no disputed or unverifiable findings, so the disputed share is 0%. The one partial finding (claim_findings[3]) concerns exact quote wording, not substance. The subject status (exploited and halted in August 2026) matches what the page says, and the only omission, the Maya post-mortem and founder blog post, is minor. The high-priority coverage gap on the official post-mortem and current network status is a suggestion for expansion, since the page already states that restart and compensation status could not be confirmed. Reviewer checks did not cover THORChain history, launch dates or CryptoSlate-specific figures.
    anchoranchored
    chain
    ●mainnet-betaslot 470,633,664
    sig
    4GWAVKvZMFne…bqkLQhb5explorer ↗
    hash
    H7QeDvaTMsWr…sKeBcLshsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1392 B) ▸
    {"actor":"judge","artifact_identity":"ca154430a6a589832ce94688a805ac0f","band_override":null,"decided_at":"2026-11-17T18:25:57.602Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":52,"page_slug":"maya-protocol","prev_score":52,"reason":"All six checked claims (claim_findings[0] to [5]) were confirmed or partially supported against Cointelegraph and Decrypt, with no disputed or unverifiable findings, so the disputed share is 0%. The one partial finding (claim_findings[3]) concerns exact quote wording, not substance. The subject status (exploited and halted in August 2026) matches what the page says, and the only omission, the Maya post-mortem and founder blog post, is minor. The high-priority coverage gap on the official post-mortem and current network status is a suggestion for expansion, since the page already states that restart and compensation status could not be confirmed. Reviewer checks did not cover THORChain history, launch dates or CryptoSlate-specific figures.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":17,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 4e016774-e454-49f9-a595-d574467c25fa
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.