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
#2
Score
62 → 62 (0)
Cluster
mainnet-beta
Slot
462055354
Off-chain at
2026-10-27T11:34:18.760Z
Anchored at
2026-10-27T11:34:38.000Z
Block time
2026-10-27T11:34:38.000Z

Independent verification

1. Database (off-chain)
HLhpAF4LJ3nzFQgKyRq4gzCTzb66FHH4WJtonkfJSrSh
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1454 chars)
{"actor":"reviewer","artifact_identity":"c6552cfbf4141e97b4c11fc5351ca235","decided_at":"2026-10-27T11:34:18.350Z","decision":"review","disputed_pct":0.2667,"findings_hash":"C2VQycRTRwKBekBhzvpxcrP1P2eSeymioRPkacLV4LR5","investigation_id":"247c355e-1ef8-4e1d-abb9-8f99f961ab83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":62,"omissions":{"material":0,"total":2},"page_content_hash":"117022b2297569566d42673bccb55373ad750b80ba03119c7476c0ff531d0984","page_slug":"vesu-protocol-pragma-oracle-malfunction-september-2026","prev_score":62,"reason":"The core incident narrative and most figures match Pragma's post-mortem and Vesu's refund post. Errors found: the 95% recovery is dated to September 13 prices when both sources say September 11. The multisig migration and Foundation publisher activation are misdated to September 15 (actual 22 and 16 September). The borrower refund description omits the required Discord ticket. The Aave comparison mislabels an internal CAPO misconfiguration as an upstream failure. One archive link points to an unrelated OrionX article. The Nostra section was not verified.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}