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 · Spectral Labs
- Sequence
- #4
- Score
- 65 → 65 (0)
- Cluster
- mainnet-beta
- Slot
- 464260284
- Off-chain at
- 2026-11-01T22:28:48.627Z
- Anchored at
- 2026-11-01T22:29:13.000Z
- Block time
- 2026-11-01T22:29:13.000Z
Independent verification
- 1. Database (off-chain)
- 7jUsh845bH68RWK1Vwd3GcESqq9qfPfbCfv69DfEbXQ6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1946 chars)
{"actor":"judge","artifact_identity":"e21d630b013c0f7aee78035e3be98fb9","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T22:28:48.350Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"437394da-c16b-4b30-ae63-075783cab595","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":65,"page_slug":"spectral-labs","prev_score":65,"reason":"Of the 5 claims that could be checked (1 was excluded because the source blocked the reviewer), 2 could not be verified (claim_findings[2] and [3]: the Bybit perpetual-futures delisting on October 1, 2025 was not found, and the only perpetual delisting located was on MEXC on October 6, 2025), giving 40% disputed or unverifiable. In addition, the SPEC price and market cap figures are stale (claim_findings[1]: about $0.0055 and $290K now, against $0.075 and $1.55M on the page). The page also omits the December 2024 Syntax exploit (omission_findings[0], material), and a high-priority coverage gap asks for it to be added. The funding claims were confirmed against TechCrunch (claim_findings[0]), and the reviewer's confidence is only 0.5 with a partial check, so the penalty stays in the middle of the band and the page is revised, not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (the December 2024 Syntax bonding-curve exploit, about $200K lost, contracts paused) and subject_status.contradicts_page is true because the page never mentions it. This matches the significant band implied by the claim percentage, so the band is held at significant and not softened."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}