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 · VeChain
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425414183
- Off-chain at
- 2026-06-09T22:00:44.070Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- u6eph1XbtgPrnvg8dgh9ieaTa6zBtr6yhdes99CJ99x
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (995 chars)
{"actor":"reviewer","decided_at":"2026-06-09T22:00:43.681Z","decision":"review","investigation_id":"3b4cc853-28e7-4cd6-8d2d-9da13011cc26","new_score":52,"page_slug":"vechain","prev_score":52,"reason":"The page's core factual claims — the 2019 hack, the 2024 X account compromise, the enterprise partnerships, and the dual-token model — are well-supported by credible sources. The two most significant issues are: (1) the AtoZMarkets URL used to support Foundation token concentration is a 404, and the 27.3% figure conflates non-circulating supply with Foundation-controlled supply; (2) the CoinTelegraph URL for the hack is also a 404. Several partially-supported claims involve the page making slightly stronger assertions than sources warrant (e.g., 'before significant spread' when victims existed, 'among the first' for MiCAR with no ranking data).","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}