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 · GeniusAI
- Sequence
- #3
- Score
- 60 → 60 (0)
- Cluster
- mainnet-beta
- Slot
- 464344657
- Off-chain at
- 2026-11-02T03:30:05.629Z
- Anchored at
- 2026-11-02T03:30:28.000Z
- Block time
- 2026-11-02T03:30:28.000Z
Independent verification
- 1. Database (off-chain)
- 6jJg8Za83DT6aycWcYf2n8z5no6XuABYU2sVEzdiCSES
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1318 chars)
{"actor":"reviewer","artifact_identity":"a8dcd5f6a22f7ae5c4f11b01556b71bd","decided_at":"2026-11-02T03:30:05.576Z","decision":"review","disputed_pct":0.4286,"findings_hash":"Fz8kVfv7MqKp1xb5A1uVMvYCqYHNGWK7mpSPxhvUFDDS","investigation_id":"9caf0d23-f3a5-4cfd-8cc2-13b8afe83513","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"omissions":{"material":0,"total":1},"page_content_hash":"0d288c464b8873504c11c87b491541985232674946b191e4c57684c635f8ab18","page_slug":"geniusai","prev_score":60,"reason":"The core exploit facts (May 5 2024, about $1.27M, Discord-derived key, Axelar bridge, 100M counterfeit tokens) are corroborated. The 80% coverage figure is wrongly attributed to CertiK. The bounty, $1 repurchase and buyback-and-burn details were not found in the cited sources I read, and the ZachXBT flag is unsupported by any cited source. Price figures are out of date. Founder background and corporate history claims were not checked. The subject is still operating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}