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_deny · Frontier (FRONT)
- Sequence
- #4
- Score
- 34 → 34 (0)
- Cluster
- mainnet-beta
- Slot
- 462174735
- Off-chain at
- 2026-10-27T18:37:22.505Z
- Anchored at
- 2026-10-27T18:37:51.000Z
- Block time
- 2026-10-27T18:37:51.000Z
Independent verification
- 1. Database (off-chain)
- Eu9adj3mWYB5YPz9oXhTRuUzmfGxmEcDgavNwvrR5CJ8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1922 chars)
{"actor":"judge","artifact_identity":"74bfdfe108c25309443f0782de13e32b","band_override":null,"decided_at":"2026-10-27T18:37:22.218Z","decision":"review_deny","delist_requested":true,"disputed_pct":0.7273,"investigation_id":"703f75f4-8b90-4141-be0f-aff684dd4ef4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_slug":"frontier-front","prev_score":34,"reason":"Of 11 claim findings, 4 were disputed and 4 could not be verified (none source_blocked), giving a disputed share of about 73%. The disputed items include the SLF peak price stated as $0.94 instead of about $0.82 (claim_findings[1], [2]) and the current-status claims that SLF still trades with about $47,900 daily volume, when CoinGecko shows trading stopped and $0 volume (claim_findings[3], [4]). The page also leaves out the November 2025 SLF network outage and suspended withdrawals (omission_findings[0], critical), which contradicts its account of the project's current state. The core account of the June 2025 CEO termination, his denial, and the Binance delisting is well sourced and was confirmed. The reviewer's confidence is moderate, and several of the unverifiable findings come from a second DL News article that was not fetched, so the penalty is set at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"deny","from_band":"deny","reason":"subject_status.contradicts_page is true and a critical omission is reported: Binance said the SLF network was down and withdrawals suspended in November 2025, while the page says the project continued operating and the token is still traded. This confirms the deny band implied by the claim percentage."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}