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.

Decision
review · Resolv
View on Solana ↗
Sequence
#4
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
464381826
Off-chain at
2026-11-02T05:42:49.556Z
Anchored at
2026-11-02T05:43:16.000Z
Block time
2026-11-02T05:43:16.000Z

Independent verification

1. Database (off-chain)
9V5unqHRaatTCGeZ28HtgjsFiqeJusGR6nGw1jKpQoUh
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1390 chars)
{"actor":"reviewer","artifact_identity":"348aff7ea5e1174bbc5177589423c607","decided_at":"2026-11-02T05:42:49.503Z","decision":"review","disputed_pct":0.4,"findings_hash":"HLJnnJ79vy5MRQzTp7MHkqwSJhdtvkKsjQx7CEHHaGjp","investigation_id":"7d3916be-be64-4d1c-b1fe-f9509b3dd168","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"omissions":{"material":0,"total":1},"page_content_hash":"d7bf017ef05795dff1fc70996c21791238484a377aba82980ac3b807931fc7ad","page_slug":"resolv","prev_score":52,"reason":"The core exploit narrative (AWS KMS key compromise, 80M USR minted in two transactions, about $25M extracted, pause at 05:16 UTC) matches the official postmortem and Chainalysis. Problems: the $0.0025 depeg low conflicts with other sources, Mandiant and ZeroShadow are described as engaged when the postmortem says planned, the postmortem is dated 2026-03-26 but is dated April 4, and the GitHub contractor chain is not supported by two of the cited sources. The May 2026 status is unsourced and the subject's current status could not be determined.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}