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 · Radix
View on Solana ↗
Sequence
#3
Score
54 → 54 (0)
Cluster
mainnet-beta
Slot
462278965
Off-chain at
2026-10-28T00:47:47.341Z
Anchored at
2026-10-28T00:47:59.000Z
Block time
2026-10-28T00:47:59.000Z

Independent verification

1. Database (off-chain)
7VzgbRY7kywq8fn1rzTNJmxmvfeU1rDAFiZSN7rB2gTS
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1416 chars)
{"actor":"reviewer","artifact_identity":"5a71b9ac71eb9455abbcdba563c33750","blocked_count":1,"decided_at":"2026-10-28T00:47:47.271Z","decision":"review","disputed_pct":0.2143,"findings_hash":"7hrC51p98FfhUi9U72xP7E6mX35CLuLQe3WqTvQvSnga","investigation_id":"dee50fd0-098b-4e22-8034-37f39cea49cb","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":54,"omissions":{"material":1,"total":2},"page_content_hash":"ecdccea2042141bd13be948ee141db67935e3b10461131edaeb115feb05f21f3","page_slug":"radix","prev_score":54,"reason":"The core incident narrative is well supported by the official report and press: the 26 transactions, the asset amounts, the June 2023 refactor origin, the Zellic 2024 audit miss, the validator-induced halt and the Sept 11 resumption. Problems are in the named post-patch verifiers (Zellic, Hacken and SEAL 911, repeated in three places), the unsupported 40% sell-off attributed to the Hughes memorial post, an unsourced AI-in-workflow commitment, and a stale token price. The page omits the pool-price manipulation that extracted XRD.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":14,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}