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 · Exactly Protocol
- Sequence
- #5
- Score
- 61 → 61 (0)
- Cluster
- mainnet-beta
- Slot
- 464285939
- Off-chain at
- 2026-11-02T00:00:23.805Z
- Anchored at
- 2026-11-02T00:00:46.000Z
- Block time
- 2026-11-02T00:00:46.000Z
Independent verification
- 1. Database (off-chain)
- 9jm92LfeQ2NXWUMamYYWHnMoSj9KeT7QxqitPeBQ87k6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1382 chars)
{"actor":"judge","artifact_identity":"d2f2fd184c517926552a002e45da07b5","band_override":null,"blocked_count":3,"decided_at":"2026-11-02T00:00:23.554Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"6cabadc3-8ceb-411b-bb9c-4948459cefc0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":61,"page_slug":"exactly","prev_score":61,"reason":"Of seven claims checked, three could not be read because the sources (DefiLlama, CryptoNews) refused access; these are excluded from the calculation and are a coverage limit, not a defect of the page. Of the four claims that could be checked, none were disputed or unverifiable (claim_findings[0], [1] and [4] confirmed; claim_findings[5] partially supported), so the disputed share is 0%. The one omission is minor (the Uphold card appears to have launched in 2026, while the page describes the partnership as proposed), and the subject is still operating, so the percentage band stands. The wrong ForkLog archive link and the unverified TVL and bounty figures are worth fixing but do not change the verdict.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}