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_revise · uniBTC
- Sequence
- #4
- Score
- 54 → 54 (0)
- Cluster
- mainnet-beta
- Slot
- 465085393
- Off-chain at
- 2026-11-03T23:35:06.387Z
- Anchored at
- 2026-11-03T23:35:15.000Z
- Block time
- 2026-11-03T23:35:15.000Z
Independent verification
- 1. Database (off-chain)
- 9sNDZ794WkYCdSku67WLeBB4CQihyaAFQcYtysm9oLsF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1242 chars)
{"actor":"judge","artifact_identity":"58b339de4fff34071e8963dcbd806265","band_override":null,"decided_at":"2026-11-03T23:35:06.147Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5714,"investigation_id":"23c26d79-a5d9-43f7-900e-e60000503ba6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":54,"page_slug":"unibtc","prev_score":54,"reason":"Of 7 claims checked, 2 were disputed and 2 could not be verified (none were blocked by the source), giving 57%, which falls in the significant-issues band. claim_findings[0] and [1] show the ZachXBT section attributes Truflation findings to the Bedrock exploit, and claim_findings[3] and [6] (Tornado Cash routing, a mismatched archive link) are unverified. The core exploit narrative (Dedaub timeline, about $2M loss, Fuzzland insider attribution) matched sources, and the reviewer's confidence is 0.5 on a small sample, so the penalty is kept in the lower half of the band and the page is not denied.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}