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 · Altura
View on Solana ↗
Sequence
#4
Score
27 → 26 (-1)
Cluster
mainnet-beta
Slot
464245888
Off-chain at
2026-11-01T21:37:36.079Z
Anchored at
2026-11-01T21:37:47.000Z
Block time
2026-11-01T21:37:47.000Z

Independent verification

1. Database (off-chain)
CbCPjhtvZtt8tw6XjLBDJfoXKGy6PDejxpmRKTbNGjv8
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1472 chars)
{"actor":"judge","artifact_identity":"4598403a1ffceaf402c9e8a7f8d19a11","band_override":null,"decided_at":"2026-11-01T21:37:35.825Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2308,"investigation_id":"56cba856-6837-453b-8686-ccc21110fa3f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"altura","prev_score":27,"reason":"Of 13 claims checked, 1 was disputed and 2 could not be verified, so about 23% need correction (claim_findings[2], [6], [7]). The core timeline (msUSD depeg, June 21 wind-down, July bank restriction) is confirmed by The Block, Crypto Economy and Protos, and the October fraud and freezing-order allegations are accurately labeled as unverified. The corrections needed are the AVLT depeg figure (the cited Protos article says about 14%, not 11%), the unsourced July 31 redemption target and AVLT price range, and the summary's wording that allegations appear in 'UK court filings', which the source does not say. The page already discloses the wind-down and the reviewer found only minor omissions, so no escalation applies.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-1,"score_limit":{"applied":-1,"limited":true,"proposed":-10,"rule":"limited_no_second_opinion","second":null},"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}