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_revise · Fake Uniswap V4 Airdrop Phishing Network (2026)
- Sequence
- #3
- Score
- 2 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 425400745
- Off-chain at
- 2026-06-09T20:31:57.806Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DTpJ2J4EnatWcDUx2QQrbfe436qUo2DBb4MTKDJyYyZR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1424 chars)
{"actor":"judge","decided_at":"2026-06-09T20:31:57.612Z","decision":"review_revise","investigation_id":"693196ec-705e-492f-a85f-567c036bc4f2","new_score":0,"page_slug":"fake-uniswap-v4-airdrop-phishing-network-2026","prev_score":2,"reason":"The page is substantively well-sourced, with 22 of 27 reviewed claims fully confirmed against Tier 1 or Tier 2 sources. No claims were directly disputed. The minor penalty reflects three unverifiable findings: claim_findings[26] cites a Blockaid X post (status/1942790637113508266) whose Twitter snowflake ID corresponds to approximately July 2026, after the review date, indicating a potentially inaccurate or fabricated citation — though the underlying technical claim is corroborated by the Blockaid blog post; claim_findings[27] asserts Scam Sniffer database integrations with Binance, Rabby, Phantom, and Bybit without a supporting citation; and claim_findings[28] states MetaMask added the 2022 phishing domain to its warning list without a cited source. Both partially-supported findings (claim_findings[2] and claim_findings[23]) are minor imprecisions already appropriately caveated on the page. The revision recommended is to replace or confirm the suspect X post citation and add citations for the two uncited partnership claims.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}