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 · Ostium Protocol
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 443522372
- Off-chain at
- 2026-08-26T23:07:30.217Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 86gqAqFHsf7oRutG6tsbXj1cKGKvS3sXm7sW9Hbiqsqh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1156 chars)
{"actor":"reviewer","decided_at":"2026-08-26T23:07:30.004Z","decision":"review","investigation_id":"5723df5c-838e-43a2-a208-bda815ccd91c","new_score":28,"page_slug":"ostium-protocol","prev_score":28,"reason":"The page is well-sourced and largely accurate on background, funding, and technical exploit mechanics, with strong corroboration from independent outlets for most figures. Its central causal claim, however, states as unqualified fact that a signer private key specifically was compromised, which overstates both Ostium's own post-mortem ('off-chain infrastructure') and the hedged conclusions of independent investigators rekt.news and DeFi Prime — the latter being one of the page's own cited sources for that very claim. The page also predates or omits Ostium's July 29-30 post-mortem and its documented remediation steps despite having later-dated sources in its own bibliography, and it reports a different pre-exploit balance figure than its sibling incident page without reconciling the discrepancy.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}