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
- Sequence
- #2
- Score
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 443520903
- Off-chain at
- 2026-08-26T12:10:13.854Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 32YwJGDLbRK1Y5XaGCXwiEtYxSs93NBM4v2Lznq3Mxkp
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1541 chars)
{"actor":"reviewer","decided_at":"2026-08-26T12:10:13.632Z","decision":"review","investigation_id":"ab0f6bf4-0424-45be-a184-3257859bdf43","new_score":22,"page_slug":"loopring-dex-trustless-exit-disabled-at-shutdown","prev_score":22,"reason":"The page's central, load-bearing allegation — that Loopring's trustless Merkle-proof exit mechanism was deliberately disabled via a team-executed contract upgrade at shutdown, replacing it with a custodial whitelist-only process that excludes sub-$10 balances entirely — is precisely and strongly supported by L2Beat's independent technical documentation and the team's own acknowledged quotes, with no evidence found that the mechanism was merely unused, never implemented, or left intact. The bulk of the page's other claims (financial figures, delisting dates, hack details, leadership history) are independently confirmed, though the review found one internal arithmetic contradiction (a stated LRC price 'further decline' that is actually numerically an increase from the page's own prior figure), one instance where L2Beat's own page contradicts the page's count of 'two' Stage-1 blockers (L2Beat lists three), one community quote split and mischaracterized as two separate comments, and several inferential claims about exactly which administrative mechanism executed the shutdown upgrade that are plausible but not directly documented by any source.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}