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 · Unibot
- Sequence
- #9
- Score
- 65 → 65 (0)
- Cluster
- mainnet-beta
- Slot
- 464992053
- Off-chain at
- 2026-11-03T18:01:25.321Z
- Anchored at
- 2026-11-03T18:01:48.000Z
- Block time
- 2026-11-03T18:01:48.000Z
Independent verification
- 1. Database (off-chain)
- 4QyKMZqvfru11r4VN6oR6r2b38PDurFDbncEKULTWFT3
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1459 chars)
{"actor":"reviewer","artifact_identity":"ac5d8a98402c799efe54f024c3298892","blocked_count":2,"decided_at":"2026-11-03T18:01:25.175Z","decision":"review","disputed_pct":0.1429,"findings_hash":"9RfhmFbopvRoFWh3pgZVLkdrXXucAcH94diwu15cCATN","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":65,"page_content_hash":"85174713e04d825e8182fda1db58a0731cc68c29d535affe029fecb3ff2a606e","page_slug":"unibot","prev_score":65,"reason":"Core exploit facts (Oct 31, 2023 date, about $560K-$640K loss, compensation pledge) and the cryptonews reimbursement figures check out. The reimbursement section wrongly attributes Cointelegraph's 334 ETH and 610 ETH figures, and the 'funded from Maestro's revenue' framing, to Unibot. Those figures belong to Maestrobots, a separate bot. Unibot's own reported cost was about $1.78M. The 25-32% price drop range omits the 40%+ figure in the cited Cointelegraph article. The March 2024 and token price sections were only partly checked because of time and a fetch failure. No current-status contradiction was found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":7,"sequence_num":9,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}