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 · Dexodus Finance
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443509073
- Off-chain at
- 2026-08-19T01:41:35.868Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2PLFf1t2S1NSs47Amc3rsiuQMt6ZLSfLwRLJA4mKgyUR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1321 chars)
{"actor":"reviewer","decided_at":"2026-08-19T01:41:35.772Z","decision":"review","investigation_id":"303d6dc0-64f2-4fd3-b0f2-6049f92eef1b","new_score":42,"page_slug":"dexodus-finance","prev_score":42,"reason":"The core incident narrative (May 26, 2025 signature-replay exploit, mechanism, root cause, and tx hash) is well corroborated by three independent security-research firms and is presented with appropriate hedging (no unhedged fraud allegations against the team). However, the page contains two clear factual errors: the current TVL figure ($1.28M) contradicts its own cited source, which shows the protocol at near-zero TVL with a deadUrl flag; and the post-mortem publication date (June 1, 2025) is off by 1.5–3.5 months against the actual publication dates of the cited pieces. The '100% recovery' claim is correctly framed as an unverified team claim, and independent security researchers describe the recovery as partial/unspecified rather than complete — this gap between team messaging and independent assessment is real and the page's hedging language is appropriate, though it should more explicitly flag that independent sources describe the recovery as partial.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}