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 · Marinade Finance
- Sequence
- #2
- Score
- 87 → 87 (0)
- Cluster
- mainnet-beta
- Slot
- 423915095
- Off-chain at
- 2026-06-03T00:08:12.346Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4eqNKgx8jbu7KT1fe8BsDTy8EweR6cv56zHZziwQj5pD
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1110 chars)
{"actor":"reviewer","decided_at":"2026-06-03T00:08:12.263Z","decision":"review","investigation_id":"29c069b0-7532-42eb-94e8-b73d29464d5e","new_score":87,"page_slug":"marinade-finance","prev_score":87,"reason":"The investigation is broadly accurate on Marinade Finance's protocol mechanics, security audit history, mSOL depeg incident, and institutional partnerships. The most significant factual error is the repeated claim that Alameda Research's multisig replacement status is 'uncertain from public sources' — Marinade published a dedicated blog post in November 2022 confirming replacement, and current governance documentation shows a completely updated 6-of-13 multisig; this misrepresentation inflates centralization risk. Secondary concerns include an unverifiable hackathon placement claim (third place/prize confusion), a founder attribution for Simon Gleiser with no corroborating source, and the absence of the November 2025 ETF launch as a timeline event.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}