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
#8
Score
34 → 42 (+8)
Cluster
mainnet-beta
Slot
470678448
Off-chain at
2026-11-17T21:06:36.456Z
Anchored at
2026-11-17T21:07:15.000Z
Block time
2026-11-17T21:07:15.000Z

Independent verification

1. Database (off-chain)
sSBpEibWKcBVvJZgXcSfKcF9o8otXriuZ8BFarrsurt
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1513 chars)
{"actor":"judge","artifact_identity":"ac00ecf7c7875b17d708465a8342ccf4","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:06:36.099Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"f7355ad7-81ed-4dcf-8292-ca6069b7ca2b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":42,"page_slug":"doingud-nft-diamond-bidding-contract-exploit","prev_score":34,"reason":"Of the six claims checked, five were confirmed or supported by their cited sources and one (claim_findings[3], the Crunchbase listing) could not be read because the source blocked the reviewer; that claim is left out of the percentage, which comes to 0% disputed. claim_findings[4] was only partly supported (the founder role is confirmed but the expanded full name was not seen on the cited profile), a minor point. The review found no omissions and no conflict between the page and the subject's status, and the page already labels the September 2026 exploit as alleged and single-sourced. The open high-priority gap (on-chain verification of the exploit) is a suggestion for expanding the page, not a defect in what it currently says.","replaces_fact_checks":{"score_before_fact_checks":42,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":8,"scored_claims":5,"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}