Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#4
Score
12 → 12 (0)
Cluster
mainnet-beta
Slot
457708353
Off-chain at
2026-10-16T16:43:07.318Z
Anchored at
2026-10-16T16:43:31.375Z
Block time
—

Independent verification

1. Database (off-chain)
EwXh8TZRwuPLw87h7y38xXvMmfANNpAetpEMQXbR2jbw
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2120 chars)
{"actor":"reviewer","artifact_identity":"76e941bbea27b74245ad94e243108bd4","decided_at":"2026-10-16T16:43:07.097Z","decision":"review","disputed_pct":0.2667,"findings_hash":"aJTu9JonqsxG3PAkLDxiFjEApU9on5Ab7C23UmcxABa","investigation_id":"7a479b99-7618-46da-8526-cef7c896c96e","mode":"findings_only","new_score":12,"page_content_hash":"06df894bea0b39105604ece440890273a1275eb5b4d0fdc37ca274da4e94c643","page_slug":"maya-protocol-mayachain","prev_score":12,"reason":"The page's core narrative of the August 18, 2026 six-bug exploit — the transaction mechanics, dollar figures, BTC tracing, CACAO price collapse, network halt, and recovery plan — is well supported by multiple live, credible, and mutually consistent sources (CoinDesk, CryptoSlate, Decrypt, Cryptopolitan, DeFiMon, Bitcoin.com News, Crowdfund Insider, CoinPaprika), all of which loaded successfully and matched the cited claims. Tokenomics (CACAO supply/distribution), audit history (Halborn Draft 3 label, Fable 5), the $35,000 Immunefi cap, and the THORChain-exploit comparisons all check out against primary or tier-1/2 sources. The most substantive problem found is a factual error in the Protocol Overview section claiming Arbitrum was among the chains supported 'at launch' in 2023, when multiple sources (including the page's own timeline, which correctly lists RUNE/USDC/USDT at the April 2023 launch and omits Arbitrum) show Arbitrum was integrated roughly a year later, in April 2024. A second, more minor issue is a timeline citation that points to the wrong Radix DLT blog post (an April 2024 'planned' announcement rather than the September 2024 completion post that actually substantiates the date). A handful of granular details (exact BTC decimal/transaction-count attribution to PeckShield, the specific 15.6% MAYA founder allocation, and the BeInCrypto '16th hack' framing, which returned a 403 on fetch) could not be fully independently confirmed, though none are contradicted by other sources.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}