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 · dTRINITY dLEND
- Sequence
- #12
- Score
- 42 → 52 (+10)
- Cluster
- mainnet-beta
- Slot
- 470688686
- Off-chain at
- 2026-11-17T21:43:52.727Z
- Anchored at
- 2026-11-17T21:44:09.000Z
- Block time
- 2026-11-17T21:44:09.000Z
Independent verification
- 1. Database (off-chain)
- ADDbmVLWp3WdoQ3qQuhM4pAgcm2jeMQb8qbiC2pM4WoA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1579 chars)
{"actor":"judge","artifact_identity":"2e44e467346d297f7d9371a0c9ff3d68","band_override":null,"blocked_count":2,"decided_at":"2026-11-17T21:43:52.398Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"32a844a0-4b60-4c3c-9c8c-06ae37b7387e","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":52,"page_slug":"dtrinity-dlend","prev_score":42,"reason":"Of 9 claim findings, 2 were unreadable because the source blocked the reviewer (claim_findings[1], claim_findings[5]) and are left out of the count; of the remaining 7, none were disputed or unverifiable, giving a disputed rate of 0%. The incident details, audit discrepancy and sector TVL context matched the sources the reviewer could read (claim_findings[0], [2], [3], [4], [6], [7]), and the one partially supported item (claim_findings[8], Katana) is already hedged on the page. The high-priority gap on post-incident status is stated openly on the page as unconfirmed and no omission or status contradiction was reported, so it calls for expansion rather than a penalty. About 22% of findings were blocked, including the official X posts and live DefiLlama figures, which is a coverage limit rather than a defect of the page.","replaces_fact_checks":{"score_before_fact_checks":52,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":10,"scored_claims":7,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}