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
#3
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
462182414
Off-chain at
2026-10-27T19:04:48.429Z
Anchored at
2026-10-27T19:04:58.000Z
Block time
2026-10-27T19:04:58.000Z

Independent verification

1. Database (off-chain)
FLCz55mG7s3vLhPyYXFPZduPj6cpWMWoNCZqz3V5QTJq
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1507 chars)
{"actor":"reviewer","artifact_identity":"5ffa61b9c9553d6160384ee91a565f19","blocked_count":2,"decided_at":"2026-10-27T19:04:48.317Z","decision":"review","disputed_pct":0.125,"findings_hash":"EHmPJpfFkxAPWriF17MufEk4N6dPKq9Nn9muCLNsNmAt","investigation_id":"6d170ce4-25fc-4295-94b8-a51859bde52c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_content_hash":"817dcc623eea1c4bc26e0603f3e3725a9429359935bca660fd8dba61079e0671","page_slug":"flamingo-finance","prev_score":26,"reason":"The core incident claims (Aug 2026 staking exploit, Sept 2026 VaultYUSDT flash loan, Aug 2024 Poly Network bridge hack, April 2026 open letter) match the cited reporting. Two timeline defects were found. The Binance Monitoring Tag event adds an 'expanded review of listed tokens' framing that the cited source does not contain. The 2020 launch is labeled 'on Neo N3', which launch-era coverage does not support. The Crypto Times and DefiLlama sources were blocked (403), so the comment-request claim and the TVL figures are unchecked. The sources are credible but mostly Neo News Today, with limited independent corroboration of the August 2026 exploit.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}