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 · Seedify
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464450020
- Off-chain at
- 2026-11-02T09:46:22.203Z
- Anchored at
- 2026-11-02T09:46:31.000Z
- Block time
- 2026-11-02T09:46:31.000Z
Independent verification
- 1. Database (off-chain)
- ExsujGE1Ru2jMGpbr5BaqsydrKDu9ThTwHDUoiTJT9cu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1725 chars)
{"actor":"judge","artifact_identity":"8e489c0a186916f5f0c1c9c4e792853a","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T09:46:21.933Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"e2374c5c-3048-4ecf-bd6f-7431aaa904a3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"seedify","prev_score":53,"reason":"About 46% of checkable claims (6 of 13, leaving out one claim whose source blocked the reviewer) were disputed or could not be verified. The price history is the weakest part: the all-time-high price and date do not match the cited CoinLore page (claim_findings[0], [1]), the $0.089 all-time low is stale (claim_findings[2]), and the Phoenix Raise date is off by a day (claim_findings[6]). The core incident, meaning the September 2025 bridge exploit, the compromised developer key, the DPRK attribution and the HTX freeze, is well supported (claim_findings[4]). The reviewer's confidence is moderate and many sections were not checked, so the penalty sits in the middle of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (the token now trades near $0.0015, so the stated $0.089 all-time low is badly out of date) and says the subject status contradicts the page. The percentage band is already significant, so the page is judged in the significant band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}