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 · FOOM Cash
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 464356727
- Off-chain at
- 2026-11-02T04:13:21.630Z
- Anchored at
- 2026-11-02T04:13:38.000Z
- Block time
- 2026-11-02T04:13:38.000Z
Independent verification
- 1. Database (off-chain)
- AykXcmVQodLSkQiBsu51to7R7kVgyEFo37oDATW56GPn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1380 chars)
{"actor":"reviewer","artifact_identity":"20e9408c9bafd93ff6f58bd4be8184b4","blocked_count":1,"decided_at":"2026-11-02T04:13:21.577Z","decision":"review","disputed_pct":0.5,"findings_hash":"AvjyX8Rs8ntZXoJVyJorwrfkT3XTDzsjRsA2nJdMzBF","investigation_id":"b5522c6d-d69b-486c-b4c0-05b0c589ea9c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":28,"omissions":{"material":0,"total":1},"page_content_hash":"4bb8b043dde34c85cee13995b332d592f92c542842e064cb679c4ef475dbf2d1","page_slug":"foom-cash","prev_score":28,"reason":"The core narrative holds: the Feb 26 2026 exploit, $2.26M loss, root cause, bounty dispute, 81% recovery and the three-month silence all match rekt.news and Cointelegraph. Two errors were found: the Base transaction is given as $427K where rekt.news says about $320K, and the $420K is called unrecovered when it was the bounty plus fee. The price data in the timeline is internally inconsistent and could not be checked. The Veil Cash date and the BlockSec/NomosLabs attribution were not confirmed.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}