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
#5
Score
4 → 4 (0)
Cluster
mainnet-beta
Slot
464362723
Off-chain at
2026-11-02T04:34:37.636Z
Anchored at
2026-11-02T04:35:03.000Z
Block time
2026-11-02T04:35:03.000Z

Independent verification

1. Database (off-chain)
9u2RftWjkinjwuZj5d5e7CxoVQ6C6tG1SRPnfaCJTGmB
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1371 chars)
{"actor":"reviewer","artifact_identity":"c2d7f589a51cfef7726ee8731a53d5b8","decided_at":"2026-11-02T04:34:37.550Z","decision":"review","disputed_pct":0.1667,"findings_hash":"62kGmyaFGA7CqxzBXdYTq8aDqULqPoUv7cL9Hnyji7Lr","investigation_id":"f7e8927f-c246-405f-843b-763fbb6ec79e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":4,"omissions":{"material":0,"total":1},"page_content_hash":"59b061f29dd6987115b5ea4d4895534a9f597c95b52d4862a50d9719365053b6","page_slug":"balance-coin-blc-oracle-manipulation-42dao","prev_score":4,"reason":"The core narrative (July 22, 2026 oracle-manipulation exploit of 42DAO, ~$912-915K loss, BLC down more than 99%, no official response) is well supported by the sources I read. The main defects are source attribution: the $912K figure is assigned to SlowMist, and the null-address mint to AMBCrypto, but the cited sources do not say so. The page is appropriately hedged about unresolved questions. Current operating status could not be established, and no post-mortem or compensation was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}