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
#7
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
463282146
Off-chain at
2026-10-30T12:17:15.180Z
Anchored at
2026-10-30T12:17:38.000Z
Block time
2026-10-30T12:17:38.000Z

Independent verification

1. Database (off-chain)
3M3kwyKHug8hkZi8hinNvsk5xbfxWUG8AKfoTUpLBK7o
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1433 chars)
{"actor":"judge","artifact_identity":"6159b94fc9f2fe3dc06fd20ead5bfb46","band_override":null,"decided_at":"2026-10-30T12:17:14.910Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"a40409a6-9de6-46ce-98c4-986fc81c21c0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"blockfills-reliz-technology-group","prev_score":26,"reason":"Three of eight claim findings (37.5%) could not be verified against the cited sources: the roughly 2,000 institutional clients figure, which appears twice (claim_findings[3], [4]) and is absent from the cited Block article, and the $77 million shortfall (claim_findings[6]), which is not in the Cointelegraph article. None were disputed, and the core chronology (Dominion suit, Chapter 11 filing, plan confirmation, Keyrock sale) is confirmed by Tier 1 and 2 sources. The two 2,000-client findings are one defect counted twice, and the $77 million check left other cited sources unchecked, so the penalty is set at the mild end of the band. The one omission (court approval of the sale on June 16) is minor, and the page already discloses the shutdown and bankruptcy.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}