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 · Meerkat Finance
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464292298
- Off-chain at
- 2026-11-02T00:23:15.042Z
- Anchored at
- 2026-11-02T00:23:29.000Z
- Block time
- 2026-11-02T00:23:29.000Z
Independent verification
- 1. Database (off-chain)
- FrVqAUdcz67kGHxvXwjPiEYsAsmZk6XMy3RQP1SpQc7c
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1377 chars)
{"actor":"reviewer","artifact_identity":"d4a46b67786a726cf465473519e9ef6a","decided_at":"2026-11-02T00:23:14.973Z","decision":"review","disputed_pct":0.4444,"findings_hash":"3SCkxzsXS4dz3RU2JmLkGNCmNRTdwQ1spxxcETFzqDEE","investigation_id":"57f937cd-6a46-42f9-aa5f-c9b25dcd1cbc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_content_hash":"ea14d6388b8d59b6eb57286c870002ec3d1f14aee557e768707e883fb735c9b9","page_slug":"meerkat-finance","prev_score":0,"reason":"The core incident narrative (launch on March 3, 2021, deployer-executed vault upgrades on March 4, about $31M drained, the Jamboo 'trial' claim, refund program, about 95% recovery) is supported by the sources checked. Problems are the Jamboo post date (March 5 on the page, March 6 in sources), a dead Binance blog URL, timeline dates for the refund contract and recovery that appear unsupported, and Binance bridge suspension and security-firm claims not found in the cited article. Timeline entries have no source fields. Only a subset of sources was fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}