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 · Velocore DEX
- Sequence
- #3
- Score
- 41 → 41 (0)
- Cluster
- mainnet-beta
- Slot
- 464348013
- Off-chain at
- 2026-11-02T03:42:06.716Z
- Anchored at
- 2026-11-02T03:42:28.000Z
- Block time
- 2026-11-02T03:42:28.000Z
Independent verification
- 1. Database (off-chain)
- Hch7MzGVCRt9cnvG3f9TZ9JwNj631hRtpuYPazo7sJvT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1400 chars)
{"actor":"reviewer","artifact_identity":"bb79f82738911cbc3fa1574c9647bcec","blocked_count":1,"decided_at":"2026-11-02T03:42:06.657Z","decision":"review","disputed_pct":0.3,"findings_hash":"AkMKcmr1NxhyZmhmuGYXkrFVbrvTK9N1F6YR2aLPdnEq","investigation_id":"97fb395d-ef2e-4331-a3fa-e006da5418c2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":41,"omissions":{"material":0,"total":1},"page_content_hash":"0a918db0aaf47f74a3fc1df987cc5d8f41330ccf08faec9545e5e054a75fe142","page_slug":"velocore","prev_score":41,"reason":"The core narrative holds: the June 2, 2024 exploit, the ~$6.8M loss, the addresses, the fund flow and Tornado Cash laundering, and the Linea halt details match the sources fetched. Issues found: the post-mortem timeline date (06-03) conflicts with The Block's June 2 publication, the 'prior to launch' audit claim contradicts the page's own timeline, and the 'training wheels' quote was not found in CryptoSlate. Several first-party sources returned 403, and the governance and anonymity analysis is uncited inference.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}