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 · Astroport
- Sequence
- #12
- Score
- 37 → 37 (0)
- Cluster
- mainnet-beta
- Slot
- 464341147
- Off-chain at
- 2026-11-02T03:17:44.070Z
- Anchored at
- 2026-11-02T03:18:00.000Z
- Block time
- 2026-11-02T03:18:00.000Z
Independent verification
- 1. Database (off-chain)
- AZzkJUTf7hwuB3nsGJNhf14qvWuW5PPhxLsorpCBLSY6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1937 chars)
{"actor":"judge","artifact_identity":"f024e7508f3efe8a9a112e397190ce81","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T03:17:43.793Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"960aad20-b4eb-472f-aa41-d2a11da02d25","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":37,"page_slug":"astroport","prev_score":37,"reason":"Of the 9 claim findings that could be read (1 was blocked by a 403 and is excluded), none were disputed and 2 could not be verified (claim_findings[4] and claim_findings[9]), giving about 22%, which would normally mean minor issues. The core narrative of the 2024 Terra exploit, the 2026 Neutron governance attack and the October 8 governance shutdown matches the cited sources. However, the page omits Astroport's advisory to withdraw liquidity on all chains and its disconnection from Neutron (omission_findings[0], material), and it implies a full clawback of bridged ASTRO where the source says only some was recovered (claim_findings[1]). The 81.88% vote share and the expedited voting track are not in the cited sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":12,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"The review reports a material omission (omission_findings[0]): after the September 2026 Neutron attack Astroport advised users to withdraw liquidity on all chains and later severed its connection to Neutron, and the page mentions neither. This is user-relevant safety information about a currently exploited subject, and a high-priority coverage gap on user fund outcomes is open, so the 22% claim-based band (minor) understates the problem."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}