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.
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 462171388
- Off-chain at
- 2026-10-27T18:25:54.367Z
- Anchored at
- 2026-10-27T18:26:00.000Z
- Block time
- 2026-10-27T18:26:00.000Z
Independent verification
- 1. Database (off-chain)
- ABmEPJTPQJrenjitnyHPTUB2auhL5fuC3exPhvEdcget
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1446 chars)
{"actor":"reviewer","artifact_identity":"93d4dc994d5387ccbdb9ccde25fe1f23","decided_at":"2026-10-27T18:25:54.290Z","decision":"review","disputed_pct":0.3333,"findings_hash":"CLTuDC1guEHmpxfhZBSEdbx6BRArozqdBt7Sm3DxCuT7","investigation_id":"b271260c-2ae5-43d8-964e-49fc6569d948","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":28,"omissions":{"material":1,"total":3},"page_content_hash":"7b646bb716cd2612562a2c7dd586f144316bc46d97c91cb5495dc4b772f02f34","page_slug":"kelpdao-vs-layerzero-civil-lawsuit-september-2026","prev_score":28,"reason":"The core lawsuit facts (court, plaintiff, causes of action, damages wording, Pellegrino's response) and the exploit timeline match the sources I could read. Problems are a timeline entry (March 2026 compromise) and an Aave restoration entry with $177M bad debt that the cited sources do not support, an unattributed 'first' claim, a single-source case number, a missing third defendant, and an outdated description of the New York frozen-funds proceedings. I checked a limited sample and did not independently verify the TVL migration or Chainalysis claims.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}