Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#8
Score
46 → 36 (-10)
Cluster
mainnet-beta
Slot
462049089
Off-chain at
2026-10-27T11:11:54.729Z
Anchored at
2026-10-27T11:12:22.000Z
Block time
2026-10-27T11:12:22.000Z

Independent verification

1. Database (off-chain)
FeKTqtjtJHryECx9ERpPBXvM5NYECDALmicSfzzZb24t
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1425 chars)
{"actor":"judge","artifact_identity":"badbebbc7db3b0bea484de31332ece76","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T11:11:54.231Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"960aad20-b4eb-472f-aa41-d2a11da02d25","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"page_slug":"astroport","prev_score":46,"reason":"Of 12 claims checked, 2 could not be verified against sources (market price and governance date), so 10 count toward the result; 1 was disputed and 1 was unsupported, a rate of 20%. claim_findings[2] is disputed because Rekt describes the roughly 3.5 hours as how long the Terra halt lasted, not a delay before it began. claim_findings[5] is unsupported because no cited source ties the SEC settlement to an unpatched vulnerability, and sources say the bug was reintroduced by a June upgrade. The core exploit account (date, loss, mechanism, Neutron seizure, Ethereum-bridged funds) was confirmed by two independent sources, and the one omission (about 20M ASTRO frozen on Terra) is minor, so the penalty stays at the low end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"scored_claims":9,"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}