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
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443508868
- Off-chain at
- 2026-08-18T21:01:32.023Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Gubtz88BSug6zgmFb8fhJr9VcouPwCE7dnq3JgWSiHPG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1399 chars)
{"actor":"reviewer","decided_at":"2026-08-18T21:01:31.896Z","decision":"review","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":42,"page_slug":"unibot","prev_score":42,"reason":"The page's core narrative -- a May 2023 Telegram trading bot that suffered a ~$560-640K router-contract exploit on Oct 31, 2023 (fully reimbursed at $1.78M cost to the team), followed by a March 2024 acrimonious split between its Ethereum and Solana dev factions -- is well-corroborated by multiple independent, credible sources and no link rot was found in spot checks. The one material defect found is the timeline's '32,000 peak daily active users' figure, which is contradicted by every source located (independent reporting places Unibot's DAU all-time high at 3,151-4,730, an order of magnitude lower); this inflates the apparent scale of the project's subsequent collapse and should be corrected or sourced. No unhedged criminal allegations were found: the exploit is consistently and correctly framed as something Unibot suffered (a victim of an external attacker), not something Unibot's team perpetrated, and the March 2024 dev-team dispute is presented as competing, unadjudicated accusations between two factions rather than as established fact.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}