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
0 → 0 (0)
Cluster
mainnet-beta
Slot
462174124
Off-chain at
2026-10-27T18:35:37.378Z
Anchored at
2026-10-27T18:35:41.000Z
Block time
2026-10-27T18:35:41.000Z

Independent verification

1. Database (off-chain)
F5VnrDZamq8CxiH1WyZfXNqb8SG5NbgSYNQYT4TfuhJm
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1663 chars)
{"actor":"judge","artifact_identity":"da50fda24aa03063726cb89c4e10bea2","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:35:37.127Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4118,"investigation_id":"ca87c557-c87e-4c4a-9f51-3b8425ec02ab","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"vbit-technologies-corp-danh-c-vo","prev_score":0,"reason":"Of 18 claim findings, 1 was unverifiable only because the source blocked the reviewer and is excluded; of the remaining 17, 5 were disputed and 2 were unsupported by any source, giving about 41%. The page's core SEC allegations (amounts, investor count, rig counts, departure dates) were confirmed against the complaint, but it misdates the Washington consent order (claim_findings[9], [10]), says the May 2025 seizure was ordered in the SEC action seven months before that action was filed (claim_findings[12]), and wrongly names a friend and a daughter's trust as relief defendants (claim_findings[3]). It also states that the case was 'filed in absentia' and that Vo posted 'retired for life' with no supporting source (claim_findings[5], [6]). The one omission, that the family relief defendants consented to judgments, is minor and does not change the band; the Post-Gazette-sourced claims could not be read and remain a coverage limit rather than a defect.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":17,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}