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_revise · Marinade Finance
- Sequence
- #3
- Score
- 87 → 79 (-8)
- Cluster
- mainnet-beta
- Slot
- 423915098
- Off-chain at
- 2026-06-03T00:08:12.396Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2roCKkfgABpcsUyawfKDkG43xXTD8y9dGatLPMPu27T5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1530 chars)
{"actor":"judge","decided_at":"2026-06-03T00:08:12.263Z","decision":"review_revise","investigation_id":"29c069b0-7532-42eb-94e8-b73d29464d5e","new_score":79,"page_slug":"marinade-finance","prev_score":87,"reason":"The review confirmed 25 of 33 checked claims and found no evidence of fraud, exploits, or material misrepresentation about protocol safety. However, claim_findings[16] and claim_findings[26] are both disputed by Tier 1 sources: the page repeatedly asserts that Alameda Research's upgrade-authority multisig slot status 'has not been publicly confirmed,' when Marinade's own November 2022 blog post and current governance documentation explicitly confirm Alameda was replaced by Staking Facilities, Mango Markets, and Phantom in a now 6-of-13 multisig. This error appears in two separate sections and the timeline (claim_findings[15] is stale for the same root cause), and because it is in the protocol's medium-severity governance risk section it materially overstates centralization risk. The page also contains an unsourced founder attribution for Simon Gleiser (claim_findings[3], partially_supported) and a hackathon prize characterization that conflates a development grant with a placement award (claim_findings[2], partially_supported). These issues are correctable and do not affect the overall accuracy of the security, TVL, or institutional-partnership narrative.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}