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
60 → 60 (0)
Cluster
mainnet-beta
Slot
462187208
Off-chain at
2026-10-27T19:21:33.930Z
Anchored at
2026-10-27T19:21:58.000Z
Block time
2026-10-27T19:21:58.000Z

Independent verification

1. Database (off-chain)
3YfcCZMwdGy24Qtf8HZiWD5Ro8cJnwgbDqv39pmWe6Cq
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1589 chars)
{"actor":"judge","artifact_identity":"7bfda89c31bae41caf4f8f12bf85056c","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:21:33.655Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"f78211a6-4a7d-45e8-843e-69c3fdbe0683","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"fetch-ai","prev_score":60,"reason":"Of 8 claim findings, 1 was excluded because the source blocked the reviewer (claim_findings[5]). Of the remaining 7, 3 were disputed or unverifiable (about 43%), which falls in the significant-issues band. Two of those are the same one-day error in the Ocean Protocol withdrawal date (Oct 10 on the page, Oct 9 per The Block; claim_findings[0] and [1]), and the page's 10% FET drop is not supported by that source (about 3.8%). The mid-2026 price range could not be checked (claim_findings[7]). The penalty is kept at the mild end of the band because the disputed items are secondary details, the core merger and exploit facts were confirmed, and reviewer confidence is only 0.5. The Fetch-Ocean dispute status has not been updated since October 2025 (a high-priority coverage gap), and attribution of the September 2026 exploit to Fetch.ai versus SingularityNET infrastructure is contested (claim_findings[3]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}