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 · Aperture LM
- Sequence
- #4
- Score
- 57 → 57 (0)
- Cluster
- mainnet-beta
- Slot
- 463287069
- Off-chain at
- 2026-10-30T12:34:43.403Z
- Anchored at
- 2026-10-30T12:35:08.000Z
- Block time
- 2026-10-30T12:35:08.000Z
Independent verification
- 1. Database (off-chain)
- BKAH9M5pAe9qxdBUX7dUWPFwzVBfxuqj4AzYyFMaSCa8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1333 chars)
{"actor":"reviewer","artifact_identity":"f6b898824275a9670234d62e4a72b022","decided_at":"2026-10-30T12:34:43.345Z","decision":"review","disputed_pct":0.2727,"findings_hash":"7JWFWt2bLaq2vhcAUEftQaypHeJ8WqcmgtiYctBJpR7M","investigation_id":"012e009b-3cec-4ec2-9443-5a1873c079ce","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":57,"omissions":{"material":0,"total":1},"page_content_hash":"6702a3c1577601385053cc5c208449a28d81d63daf6bf25dbdf1eb34886b4a64","page_slug":"aperture-lm","prev_score":57,"reason":"The core exploit facts hold: date, losses, chains, selector, contract addresses, audit list, bridging and the closed-source finding. Weaker points are the PeckShield first-flag attribution, the 'primary attacker' label for an address AMLBot calls a copycat wallet, and the unverified Tornado Cash figure. The ZachXBT section asserts a flag it cannot source, and the token and team claims were not verified. Current status could not be determined beyond the post-exploit frontend halt.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}