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_revise · Flare
View on Solana ↗
Sequence
#3
Score
58 → 53 (-5)
Cluster
mainnet-beta
Slot
425203268
Off-chain at
2026-06-08T22:42:23.763Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
2AdU9kWr5coUEgaSFenRXtRGSyRv7w2p3Zapn5niHXz4
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1457 chars)
{"actor":"judge","decided_at":"2026-06-08T22:42:23.568Z","decision":"review_revise","investigation_id":"9fe0ee4e-99e2-414c-884c-b4e2e334b274","new_score":53,"page_slug":"flare","prev_score":58,"reason":"The review confirmed 12 of 17 claims via independent sources, with zero claims factually disputed by credible evidence. The reviewer's computed disputed_pct of 0.12 reflects three partially-supported claims and two unverifiable self-reported metrics rather than outright contradictions. The most meaningful issue is claim_findings[10]: the page attributes '80 new users per day' to Flare's overall network, while the Protos article (March 2026) specifically measures the FXRP DeFi product launched September 2025 — this is a material framing error that overstates adoption concern for the whole network. Two unverifiable claims (claim_findings[12] stablecoin cap, claim_findings[16] partner count) rely solely on Flare's own promotional content with no independent corroboration. A high-priority coverage gap flags that key network metrics (860K addresses, 500K daily transactions) are self-reported with no on-chain data source cited. A minor revision correcting the Protos attribution and flagging self-reported metrics as such would resolve the principal issues; no structural removal or delist is warranted.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}