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 · Aquifer AMM
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 464271460
- Off-chain at
- 2026-11-01T23:08:55.489Z
- Anchored at
- 2026-11-01T23:09:11.000Z
- Block time
- 2026-11-01T23:09:11.000Z
Independent verification
- 1. Database (off-chain)
- CQb6aHRuJXLzNXNobpxGS4pb7Ejxtuk3uU5xPwWwsBFw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1389 chars)
{"actor":"reviewer","artifact_identity":"1079504f1118bb2f4601abc89c3f05ca","decided_at":"2026-11-01T23:08:55.415Z","decision":"review","disputed_pct":0.1,"findings_hash":"EA8zyDaMDo5DgrTeNgoYvH5YUGkkErwnzrFVM5TsPLGC","investigation_id":"08cd862e-8f35-46e7-b1ce-3a7c78538fc9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":28,"omissions":{"material":0,"total":1},"page_content_hash":"c97ce005d891c07166e6d7f9bb99ee9bc98d2ba8b2a08a3ecc73a911ed191c90","page_slug":"aquifer-amm","prev_score":28,"reason":"The core facts (loss of about $2.47-2.5M, 18 of 45 vaults, whitehat bounty terms, disputed root cause, PeckShield context) are supported by the cited sources. Problems are attribution slips: the $70 vault figure is credited to Capwolf but comes from Bitquery, the Defimon wallet-compromise framing is crypto.news's own, the Coinpaper top-ten listing could not be verified (Yahoo does confirm it), and a few details are stated more firmly than the sources allow. The subject is correctly presented as exploited. I found no confirmed shutdown.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}