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 · Scallop Lend
- Sequence
- #3
- Score
- 52 → 32 (-20)
- Cluster
- mainnet-beta
- Slot
- 425563588
- Off-chain at
- 2026-06-10T14:27:03.059Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9zqqMqahfHu5HgVpJmDW2Tn99xqVwM7ZQ8obQAJXoem1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1343 chars)
{"actor":"judge","decided_at":"2026-06-10T14:27:02.805Z","decision":"review_revise","investigation_id":"36f1c665-fe89-475f-9df0-0788b6519bd0","new_score":32,"page_slug":"scallop-lend","prev_score":52,"reason":"The reviewer found 37.5% of claims disputed or partially supported across 16 checked claims, placing this in the significant-issues band. The most material error is claim_findings[12]: the March 29, 2026 TVL entry contains a year error — the cited press release is dated March 29, 2025 — and DefiLlama (Tier 1) shows current TVL at approximately $15 million, directly contradicting the stated $130 million figure and leadership claim. Secondary issues include claim_findings[6] and claim_findings[14], where the 'two-hour restoration' timeline is contradicted by the KuCoin deep-dive (Tier 2) stating 72 hours, and claim_findings[10], where the February 2025 audit is attributed to 'the Sui Foundation' when it was conducted by Asymptotic, a partner firm. The core exploit narrative (date, mechanism, loss amount, 100% coverage) is well-supported. The page requires correction of the TVL year error and several partially-supported timeline details before the investigation can be approved.","score_delta":-20,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}