Skip to main content
Sign in
← 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_approve · VeChain
View on Solana ↗
Sequence
#5
Score
42 → 65 (+23)
Cluster
mainnet-beta
Slot
426514447
Off-chain at
2026-06-14T23:15:57.062Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
4E4RE2S2WBukrL7PkeR1CBR7d3PqMCSAb6RYyhdJUZbk
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1359 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:56.959Z","decision":"review_approve","investigation_id":"3b4cc853-28e7-4cd6-8d2d-9da13011cc26","new_score":65,"page_slug":"vechain","prev_score":42,"reason":"All six claim findings (claim_findings[0–5]) are fully supported with no disputed claims at 0% disputed_pct. The reviewer correctly identifies that the two incidents driving the current WARNING band — the 2019 buyback wallet hack (employee negligence, majority of funds recovered via stakeholder vote, claim_findings[0]) and the 2024 Twitter account compromise (external attacker, promptly remediated, claim_findings[1]) — are both suffered-by-entity events rather than entity-perpetrated fraud. The page content is accurate and stands as published. The current score of 42 demonstrably miscalibrates VeChain against the band semantics: no enforcement actions exist (claim_findings[4]), MiCAR compliance was achieved in March 2025 (claim_findings[2]), and the project remains actively developed with verified enterprise partners (claim_findings[3], [5]). A score of 65 (CAUTIONARY) correctly reflects a legitimate operator with material historical security caveats but no unresolved fraud or ongoing user risk.","score_delta":23,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}