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
#2
Score
35 → 27 (-8)
Cluster
mainnet-beta
Slot
464114975
Off-chain at
2026-11-01T13:49:30.781Z
Anchored at
2026-11-01T13:49:59.000Z
Block time
2026-11-01T13:49:59.000Z

Independent verification

1. Database (off-chain)
54rNhjPfjHKpT1VKidtXXSdWtNSG2PehFUMbRqTa5Aj4
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1839 chars)
{"actor":"judge","artifact_identity":"ae4c0655aaa5e4b368df290be66e268e","band_override":null,"decided_at":"2026-11-01T13:49:30.530Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"56cba856-6837-453b-8686-ccc21110fa3f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":27,"page_slug":"altura","prev_score":35,"reason":"Seven of eight checked claims match The Block, Protos and CryptoDaily, and promotional claims are hedged on the page. claim_findings[5] is stale. The page says the GBP 16.4M bank restriction is unverified, but July 2026 reporting now confirms it. The page also leaves out that final depositor payouts are delayed as a result (omission_findings[0], material). A small penalty and a minor-issues banner apply until the page is updated. The high-priority gap on post-July 2026 status is also open.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"score_limit":{"applied":-8,"limited":true,"proposed":-10,"rule":"second_opinion_agreed","second":-8},"sequence_num":2,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Computed disputed_pct is 0% (7 of 8 claims confirmed, none disputed or unverifiable), which maps to approve. The review reports a material omission: July 2026 reporting says final depositor payouts are delayed by a bank restriction on over GBP 16.4M, and the page calls that restriction unverified. Escalated to the minor band, not higher, because the omission rests on a single Tier 3 source, the page already discloses the wind-down and withdrawal pause, and the page does not contradict the subject's shut-down status."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}