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 · Sharwa.Finance
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 464358376
- Off-chain at
- 2026-11-02T04:19:19.672Z
- Anchored at
- 2026-11-02T04:19:31.000Z
- Block time
- 2026-11-02T04:19:31.000Z
Independent verification
- 1. Database (off-chain)
- 8VNaQVwmTy6vBtsdTssvRTP8tXkihokZE7kYQdYCWGoG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1389 chars)
{"actor":"reviewer","artifact_identity":"cf129dd8c5a8f32ccf00d82416ceddd4","decided_at":"2026-11-02T04:19:19.606Z","decision":"review","disputed_pct":0.3636,"findings_hash":"8zrHRm25E2zupvR9d5YLRSBSy9SXsE5ytCsSYN6m9pLw","investigation_id":"833401a1-ffcb-4c74-95d6-404dedd094a9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":0,"total":1},"page_content_hash":"719a3ad23a9e718dadb0817e1da6f2c02b95808962de899b4824758a65f466f7","page_slug":"sharwafinance","prev_score":38,"reason":"The core October 2025 exploit facts hold up: date, amount, pools, attacker addresses, Morpho flash loan, the 18-day-old deployment, the FailSafe attacker split and the Pashov findings. Weak points are the unsourced ZachXBT-associated flag (summary and sections[4]), the unsourced $40,000 recovery, an overstated claim that the fix was dropped (Verichains says the finding was marked resolved), and a stale DefiLlama rank and TVL. I could not read DefiLlama directly, so the May 2026 incident and current status rest on a search summary.","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}