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_approve · Sweat Economy (SWEAT Protocol)
- Sequence
- #12
- Score
- 48 → 55 (+7)
- Cluster
- mainnet-beta
- Slot
- 470683573
- Off-chain at
- 2026-11-17T21:25:05.160Z
- Anchored at
- 2026-11-17T21:25:48.000Z
- Block time
- 2026-11-17T21:25:48.000Z
Independent verification
- 1. Database (off-chain)
- 3yDUheTs5HqzTWAdUdVKLbUxf69B57E468Q96wJMRJSq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1355 chars)
{"actor":"judge","artifact_identity":"9a9e27ed1a50bcf2e989586b639fda80","band_override":null,"decided_at":"2026-11-17T21:25:04.796Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"92e0c575-a6d1-42dd-81e7-240757082fb7","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":55,"page_slug":"sweat-economy-sweat-protocol","prev_score":48,"reason":"All 9 claim_findings were confirmed against their cited sources, with none disputed or unverifiable, so disputed_pct is 0%. The page correctly reflects the scheduled 30 December 2026 wind-down (subject_status does not contradict the page). The only omission is minor (other 2026 exchange delistings not listed, omission_findings[0]), and open coverage gaps are medium or low priority, so they suggest expansion rather than a penalty. The Bitfinex finding (claim_findings[3]) rests on a blocked direct fetch plus search-summary content, and the governance, user-metric, Trustpilot and tokenomics sections were not checked in depth.","replaces_fact_checks":{"score_before_fact_checks":55,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":7,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}