Skip to main content
AVOID.NET
← 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 · Pons (PONS)
View on Solana ↗
Sequence
#4
Score
60 → 60 (0)
Cluster
mainnet-beta
Slot
462169363
Off-chain at
2026-10-27T18:18:26.576Z
Anchored at
2026-10-27T18:18:49.000Z
Block time
2026-10-27T18:18:49.000Z

Independent verification

1. Database (off-chain)
BThe655Y1qsdbX5JGFTtjPN6JNVUNxabqg6MD7MUqnx2
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1923 chars)
{"actor":"judge","artifact_identity":"e857b82a5dcbe9f1ae9f76b80849b5a0","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:18:26.279Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"c39bbd1f-3f16-42f6-be16-72f32162e802","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"pons","prev_score":60,"reason":"Counting claim findings, 2 of 10 (20%) were unverifiable (the 1% fee and 70/30 split, and the supply figures), and one finding was left out because its source blocked the reviewer. That would normally mean minor issues. But the stated $400-500M market cap is now about $173M (claim_findings[0], [1]), the Phoenix 'closed private beta' description is outdated (claim_findings[2]), and the page omits both the reported $18M rug-pull activity on the Pons V2 launchpad and the fall from the September high. These material omissions mean the page gives a misleadingly favorable picture, so it is judged as significant issues. Core price history and the contract address were confirmed, so the page is revised rather than denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"Claim findings alone give 2 of 10 counted findings disputed or unverifiable (20%, minor band; one source_blocked finding excluded). However omission_findings[0] (documented $18M rug-pull activity on the Pons V2 launchpad) and omission_findings[2] (about 73% fall from the September high) are material, and subject_status.contradicts_page is true. The page also states a market cap that is stale by more than half (claim_findings[0], [1])."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}