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 · Tropykus RSK
- Sequence
- #3
- Score
- 44 → 32 (-12)
- Cluster
- mainnet-beta
- Slot
- 443525965
- Off-chain at
- 2026-08-27T12:07:23.363Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2u1jeMWZoXiHTHds8pkQMEmUjd6yxdMm7epAspMtdwVz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1903 chars)
{"actor":"judge","decided_at":"2026-08-27T12:07:23.196Z","decision":"review_revise","investigation_id":"db07f732-3a6a-48a9-9450-a59c52c3e302","new_score":32,"page_slug":"tropykus-rsk","prev_score":44,"reason":"None of the page's 15 checked claims came back false or unverifiable -- the account of the June 2023 rBTC micro-market exploit, its roughly $150,000 / 10%-of-deposits scale, the reimbursement pledge, and the revert to Compound's codebase are all confirmed, including by an independent pull of DefiLlama's raw TVL and hacks data. However, the review surfaced two high-priority gaps that a 0% disputed rate does not capture: the page's six sections carry sources and severity ratings but contain no written analysis at all, and the page never mentions that Tropykus announced a full wind-down of the protocol in April 2026, shut its web interface on 27 July 2026, and ends technical support on 1 September 2026 -- the single most important fact a reader would need right now. Because a page can omit its subject's current shutdown while still having zero factually disputed claims, and because this platform's purpose is to warn users about risk, that omission is treated as disqualifying for outright approval even though it does not move the disputed-claim math. The page is sent back for revision rather than denied outright, since its existing factual content holds up well and the reviewer's confidence (0.72) was moderate, not low. Also flagged: three timeline dates that follow an unverified first-of-month placeholder pattern rather than sourced dates, and two mismatched or rotted citations (a HackenProof bug-bounty link that no longer lists Tropykus, and an unexplained ZachXBT Wikipedia citation with no discoverable link to the protocol).","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}