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
- 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. - 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.
- 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_approve · Dexodus Finance
- Sequence
- #13
- Score
- 48 → 48 (0)
- Cluster
- mainnet-beta
- Slot
- 470683887
- Off-chain at
- 2026-11-17T21:26:26.810Z
- Anchored at
- 2026-11-17T21:26:55.000Z
- Block time
- 2026-11-17T21:26:55.000Z
Independent verification
- 1. Database (off-chain)
- 4bXKZsDTbvtNsxxejmNYrYaTdViVo9RJtRCNtrHLkycc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1368 chars)
{"actor":"judge","artifact_identity":"3cf818a05a575f6b4960c5e8ef1a7deb","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:26:26.510Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"303d6dc0-64f2-4fd3-b0f2-6049f92eef1b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":48,"page_slug":"dexodus-finance","prev_score":48,"reason":"Of 7 claim findings, 1 (Halborn audit dates, claim_findings[6]) was unverifiable because the source blocked the reviewer and is excluded from the rate; of the remaining 6, none were disputed or unverifiable, giving 0%. The core exploit facts (claim_findings[0-3]) were confirmed against two Tier 2 analyses, and the two partial findings (claim_findings[4-5]) rest on DeFiLlama pages that returned 403, not on contradicting evidence. The high-priority coverage gap on refund verification is already disclosed on the page as an open, unconfirmed recovery claim, so it calls for expansion, not a penalty. The review found no omissions and no shutdown or sanction that contradicts the page.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":6,"sequence_num":13,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}