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 · Flare
View on Solana ↗
Sequence
#2
Score
58 → 58 (0)
Cluster
mainnet-beta
Slot
425203263
Off-chain at
2026-06-08T22:42:23.667Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
HhDwjQjePZwTztsxYYUPFJpX8ZKpKoFC9ZDvW7drgJdY
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1112 chars)
{"actor":"reviewer","decided_at":"2026-06-08T22:42:23.568Z","decision":"review","investigation_id":"9fe0ee4e-99e2-414c-884c-b4e2e334b274","new_score":58,"page_slug":"flare","prev_score":58,"reason":"The Flare investigation page is broadly accurate on verifiable historical claims — airdrop date, token amounts, price crash figures, burn program, and FIP.16 are all confirmed by independent sources. Three claims are partially supported due to the page relying on self-reported Flare metrics without independent corroboration (active addresses, daily transactions, stablecoin cap), and because the Protos '80 new users' article is mischaracterized as a network-wide metric when it specifically measures FXRP DeFi product adoption. Two primary cited URLs (BeInCrypto, BitcoinEthereumNews) returned HTTP 403, which may reflect geo-blocking or access restrictions rather than confirmed link rot. No claims were found to be factually disputed by independent credible sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}