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 · FEGex
- Sequence
- #3
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464275201
- Off-chain at
- 2026-11-01T23:22:12.867Z
- Anchored at
- 2026-11-01T23:22:31.000Z
- Block time
- 2026-11-01T23:22:31.000Z
Independent verification
- 1. Database (off-chain)
- GL2gVUr3QGKmzPRKwYB84DKFCKEec3EJqYBPBxmAqTBX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1320 chars)
{"actor":"reviewer","artifact_identity":"18d01d06c212fa63494082370c96e200","blocked_count":1,"decided_at":"2026-11-01T23:22:12.801Z","decision":"review","disputed_pct":0.4545,"findings_hash":"94cnzx4i86FbFnsm9gb1PZfchN5f6VMgpgaPpJV3pofL","investigation_id":"371a48cc-77ea-4fda-beae-4efc4fc12f75","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"omissions":{"material":0,"total":1},"page_content_hash":"93916c99382b2e12d1a2e894dccff29c46bd0bfc428a657ca1abf99c84775568","page_slug":"fegex","prev_score":53,"reason":"The incident narratives for May 2022, Team Finance and Dec 2024 match primary analyses from CertiK and BlockSec and reporting from Protos. Errors found: the Dec 2024 loss is overstated at $1.3M (sources say about $1M), the $3.6M cumulative total has no source, and the Team Finance total is understated. The ZachXBT section is unverified, the paused-status claim is stale, and two archive links are wrong. Current status was not determined.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}