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
0 → 0 (-12)
Cluster
mainnet-beta
Slot
462186227
Off-chain at
2026-10-27T19:18:01.364Z
Anchored at
2026-10-27T19:18:29.000Z
Block time
2026-10-27T19:18:29.000Z

Independent verification

1. Database (off-chain)
GqJajhamzrKnZvc3ExNUSQXax44DQwa2m1NpzW6wcJ6L
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1548 chars)
{"actor":"judge","artifact_identity":"2edc74401a44c5d51e1f4a820901881a","band_override":null,"decided_at":"2026-10-27T19:18:01.053Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"01494b56-984e-47cb-ab96-8de03af4c51c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"fake-giwa-mainnet-bridge-scam-impersonation-of-giwa-l2-listed-by-dyorswap","prev_score":0,"reason":"The core facts of the incident (1,335 addresses, 767.65 ETH deposited, 766.25 ETH drained, DYORSWAP's over 200 ETH compensation) were confirmed by multiple outlets (claim_findings[0], [5]). Two of nine claims (22%) could not be verified: a direct CryptoSlate quotation (claim_findings[4]) and the DYORSWAP usage statistics and compensation address (claim_findings[6]). Because an unverified payment address carries a phishing risk, the penalty sits in the upper part of the minor band. Smaller issues also need correcting: one timeline entry gives both 8.5 and 11 hours for the funding-to-launch gap (claim_findings[2]), the Tornado Cash and 589 ETH figures are a point-in-time snapshot attributed to Stablemark (claim_findings[3]), and the page presents the 40% compensation plan as settled when final criteria are pending (minor omission).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}