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 · dTRINITY dLEND
- Sequence
- #11
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 470688680
- Off-chain at
- 2026-11-17T21:43:52.539Z
- Anchored at
- 2026-11-17T21:44:08.000Z
- Block time
- 2026-11-17T21:44:08.000Z
Independent verification
- 1. Database (off-chain)
- Eaot4YFuZQi9tKVqcVj3GgHLR2YMLmrhbiiaYakwZi55
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1211 chars)
{"actor":"reviewer","artifact_identity":"2e44e467346d297f7d9371a0c9ff3d68","blocked_count":2,"decided_at":"2026-11-17T21:43:52.398Z","decision":"review","disputed_pct":0,"findings_hash":"43Ygrz4w68eSrbGz6DWVZNSvLt8EAFis7jdoyS7tbsm5","investigation_id":"32a844a0-4b60-4c3c-9c8c-06ae37b7387e","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":42,"page_content_hash":"884c82977a8bfa6b481b2baf8522ce5a9bcc9d2fb2f22700fd5b4b2d807d1028","page_slug":"dtrinity-dlend","prev_score":42,"reason":"The incident details (September 2025 approval abuse, March 2026 deposit inflation), the audit discrepancy and the sector TVL context all match the sources I could read. The page hedges where evidence is thin. The DefiLlama TVL figures and the official X posts could not be read, so those claims are unscored. The subject's current operating status remains unclear.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":7,"sequence_num":11,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}