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 · Degen (DEGEN)
- Sequence
- #3
- Score
- 55 → 45 (-10)
- Cluster
- mainnet-beta
- Slot
- 464259037
- Off-chain at
- 2026-11-01T22:24:14.798Z
- Anchored at
- 2026-11-01T22:24:48.000Z
- Block time
- 2026-11-01T22:24:48.000Z
Independent verification
- 1. Database (off-chain)
- GYXWE4Qb9VV4eiyKuM6vDoCGw1PnTaD7QR16uW158jFJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1986 chars)
{"actor":"judge","artifact_identity":"0e5286f3c28b2a837967d17dfb630622","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T22:24:14.555Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0833,"investigation_id":"9177398d-fc84-4c65-b1f8-822113aa4874","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_slug":"degen-degen","prev_score":55,"reason":"Of 12 countable claims (one CryptoRank finding was excluded because the source blocked the reviewer), none were disputed and one was unverifiable, about 8%, which alone would be an approval. However, omission_findings[0] and subject_status show that Degen Chain, described on the page as the token's gas network, was shut down in August 2026 and the page does not mention it, and coverage_gaps flags this as high priority. The Bitcoinworld refund source is dead (claim_findings[6] and [7]) and the CoinGecko 13 October snapshot could not be reproduced (claim_findings[10]). The page should be revised to add the sunset and the May 2024 outage and to remove or replace the dead link.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"score_limit":{"applied":-10,"limited":false,"proposed":-10,"rule":"second_opinion_agreed","second":-10},"scored_claims":12,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"omission_findings[0] is material and subject_status.contradicts_page is true: Degen Chain was sunset and Alchemy ended support on 2026-08-31, and the page does not say so. The percentage band (about 8%) understates this. Escalated to minor rather than significant because the DEGEN token on Base continues to trade, the stated claims are accurate, and the omission concerns the associated L3 network rather than the token itself."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}