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 · Flare
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 457652120
- Off-chain at
- 2026-10-16T13:20:22.205Z
- Anchored at
- 2026-10-16T13:20:53.277Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6zQqKg4jGEqsQhmvSYFgxXfsYWSDWn4bAZctJrgpXY2E
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1736 chars)
{"actor":"reviewer","artifact_identity":"4672e32688a3ece201877769b41c063c","decided_at":"2026-10-16T13:20:21.979Z","decision":"review","disputed_pct":0,"findings_hash":"AJLz1YViuUC29w1hoA5EtDmFoTyqDTVsPn3LACoximnY","investigation_id":"9fe0ee4e-99e2-414c-884c-b4e2e334b274","mode":"findings_only","new_score":53,"page_content_hash":"95626838d85e702062ffb7d00241f6a1e58b126ae304d25b6d9898fa854ecac1","page_slug":"flare","prev_score":53,"reason":"The page's core narrative -- the XRP snapshot/airdrop timeline, the 4.279B FLR distribution, the 15%-upfront drip schedule, the 83-87% launch-day crash, and the Coinbase/Songbird distribution controversy -- is well-supported by the cited CoinDesk and CryptoSlate reporting and corroborated independently. Problems cluster in the Founder/Background section, where the sole citation is a dead domain (bitcoinethereumnews.com) and the page attributes a causal claim to Philion (that Songbird testing was his stated reason for the delay) that the likely-original article does not actually make, and in the Network Metrics section, where two of the more specific and time-sensitive claims (FIP.16, 'Flare 2.0'/Q3 2026 confidential compute) are not actually discussed in the single official source cited for that whole section, and the FIP.16 inflation cut has in fact already passed and taken effect, making the page's present-tense 'proposes' framing stale. The summary also broadens a Protos finding about Flare's niche 'XRP DeFi ecosystem' into a claim about 'the network' as a whole, which the section text states more carefully than the summary does.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}