Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Curve LlamaLend
View on Solana ↗
Sequence
#2
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
425432765
Off-chain at
2026-06-10T00:03:12.199Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
64JTukUT8ANCGr1NzU4zcWWcwBJRyB5twcfCU74icD6G
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1021 chars)
{"actor":"reviewer","decided_at":"2026-06-10T00:03:12.128Z","decision":"review","investigation_id":"b20a5ebe-152f-4198-9df6-0987e1950faf","new_score":52,"page_slug":"curve-llamalend","prev_score":52,"reason":"The investigation page's factual claims are largely accurate and well-grounded: all major incident dates, dollar figures, and mechanism descriptions are corroborated by tier-1 sources or contemporaneous reporting. The one unverifiable claim — a specific flag by ZachXBT directed at Curve LlamaLend — has no corroborating source across multiple searches. The one partially-supported claim (June 15 repayment date) has the core facts confirmed but the specific date could not be independently verified due to a 404 on the cited CoinTelegraph URL. A significant structural gap exists in that all section content fields are empty, leaving the full page structure unreviewed.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}