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
- #5
- Score
- 42 → 55 (+13)
- Cluster
- mainnet-beta
- Slot
- 443508860
- Off-chain at
- 2026-08-18T20:40:49.470Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 74dj5BLA4opsepdSGtrBcywxABqeGogZYTezwDbvR1Cd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1604 chars)
{"actor":"judge","decided_at":"2026-08-18T20:40:49.271Z","decision":"review_revise","investigation_id":"960aad20-b4eb-472f-aa41-d2a11da02d25","new_score":55,"page_slug":"astroport","prev_score":42,"reason":"This is a calibration-only adjudication; content accuracy was not in dispute (0% disputed_pct across 15 claim_findings, 0 unhedged_allegation findings, reviewer confidence 0.75). The reviewer's calibration_assessment attributes both major loss events — the May 2022 Terra/Luna ecosystem collapse and the July 2024 IBC hooks reentrancy exploit — as 'suffered' (attribution b), not own-fraud or negligence, and classifies the Terraform Labs SEC fraud liability as third-party/guilt-by-association risk (attribution c) that Astroport's own governance does not control. Per the scoring rubric, an entity whose primary incidents are suffered hacks/ecosystem contagion should not sit in WARNING (20-49); nothing in the review supports an own-fraud finding that would justify the current WARNING/42. I agree with the reviewer's recommendation to move the entity to CAUTIONARY/55 — the lower-middle of the band rather than its top — reflecting genuine non-fraud risk signals the reviewer surfaced (two near-total-value-destruction incidents in three years, thin post-collapse recovery to ~$29M TVL, an operational-hygiene lapse — an outdated ibc-go dependency — behind the 2024 exploit, and an unresolved coverage gap on whether exploit victims were made whole).","score_delta":13,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}