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 · FOOM Cash
- Sequence
- #3
- Score
- 28 → 8 (-20)
- Cluster
- mainnet-beta
- Slot
- 464356732
- Off-chain at
- 2026-11-02T04:13:21.782Z
- Anchored at
- 2026-11-02T04:13:39.000Z
- Block time
- 2026-11-02T04:13:39.000Z
Independent verification
- 1. Database (off-chain)
- 4nu3ZA9F4B9Vtr7uixRL3k4WS35xSBx6dh8etf1rqQLf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1549 chars)
{"actor":"judge","artifact_identity":"20e9408c9bafd93ff6f58bd4be8184b4","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T04:13:21.577Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"b5522c6d-d69b-486c-b4c0-05b0c589ea9c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":8,"page_slug":"foom-cash","prev_score":28,"reason":"Of 10 checkable claims (one excluded because its source could not be read), 3 were disputed and 2 could not be verified, giving a 50% disputed rate. claim_findings[0] and [1] give the Base transaction as $427,000 where the cited rekt.news article says about $320,000, and claim_findings[2] describes $420,000 as unrecovered when it was the bounty plus recovery fee. The core account (the Feb 26, 2026 exploit, the $2.26M loss, the root cause, the 81% recovery and the team's silence) was confirmed, and the one omission found is minor, so the penalty sits in the lower part of the band. The Veil Cash date and the BlockSec/NomosLabs attribution (claim_findings[8], [9]) were not confirmed, and the price figures could not be checked and look internally inconsistent.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-20,"score_limit":{"applied":-20,"limited":false,"proposed":-20,"rule":"second_opinion_agreed","second":-20},"scored_claims":10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}