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 · Gigachad (GIGA)
- Sequence
- #4
- Score
- 70 → 70 (0)
- Cluster
- mainnet-beta
- Slot
- 462169353
- Off-chain at
- 2026-10-27T18:18:16.863Z
- Anchored at
- 2026-10-27T18:18:47.000Z
- Block time
- 2026-10-27T18:18:47.000Z
Independent verification
- 1. Database (off-chain)
- A5NfxLcY28kdCQr2mMpNbyeLo5WDBeUUZSZuC9ZmDAZT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1207 chars)
{"actor":"judge","artifact_identity":"33905ed7af29ec94bad6eec80cb36aa8","band_override":null,"decided_at":"2026-10-27T18:18:16.622Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"51fdbbe5-66a9-470f-b80a-98d067ef3223","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":70,"page_slug":"gigachad-giga","prev_score":70,"reason":"Two of ten checked claims (20%) could not be verified and none were disputed, which falls in the minor-issues band. claim_findings[2] (the July 8, 2024 consent judgment date) and claim_findings[8] (the CoinDesk statement about Gigachad LLC, cited to a price page) were not found in the cited sources. The core SEC, DOJ and phishing-theft claims were confirmed, and the one omission (a later Binance.US listing) is minor. A high-priority coverage gap on on-chain data (holder concentration, mint authority) means the no-founder-allocation claim is still unaudited.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}