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
38 → 26 (-12)
Cluster
mainnet-beta
Slot
462186389
Off-chain at
2026-10-27T19:18:57.674Z
Anchored at
2026-10-27T19:19:04.000Z
Block time
2026-10-27T19:19:04.000Z

Independent verification

1. Database (off-chain)
5zct3XEw46FzKgPwAaxDcSGZxVRy7PGj27Cu4WZMqmEJ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1704 chars)
{"actor":"judge","artifact_identity":"c9d40c19e0b1ea58114c548d05e1ddd2","band_override":null,"decided_at":"2026-10-27T19:18:57.403Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"0916dae3-2850-4575-9a85-2db38c3ff3e8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"hemi-genesis-drop-merklebox-exploit","prev_score":38,"reason":"Three of nine claims (claim_findings[2], [3], [7]) could not be verified, which puts the unverified share at about 33%, in the significant-issues band. The core facts (exploit date, amount, proceeds, flash loan, Upbit and Bithumb actions) were confirmed against the postmortem relay and news reports, and none were disputed, so the penalty is set at the mild end of the band. The most concrete defect is that the stablecoin figures in the funds section contradict each other (about $243,100 versus about $254,947), and the 63-call count and the March 2025 mainnet launch were not found in the fetched sources. One further claim, that no user funds were at risk, is only partly supported because it is the project's own assessment and the page omits that unclaimed airdrop recipients lost their allocations; that omission was rated minor. The reviewer's confidence was moderate (0.6) and only some cited sources were fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"score_limit":{"applied":-12,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}