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 · VeChain
View on Solana ↗
Sequence
#4
Score
4242 (0)
Cluster
mainnet-beta
Slot
426514442
Off-chain at
2026-06-14T23:15:57.014Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
BmW3dQZtondRUmoHF5VCfGnNsGZDBADgNJK4t2QNHhfY
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1666 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:15:56.959Z","decision":"review","investigation_id":"3b4cc853-28e7-4cd6-8d2d-9da13011cc26","new_score":42,"page_slug":"vechain","prev_score":42,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. VeChain is a long-running, actively developed enterprise blockchain founded in 2015 by Sunny Lu (former CIO of Louis Vuitton China), with a verified mainnet since June 2018, confirmed enterprise partnerships (Walmart China, BMW, UFC), and full MiCAR regulatory compliance achieved in March 2025. The two incidents driving the WARNING band — a 2019 internal employee wallet hack and a 2024 external Twitter account compromise — were both suffered by the entity, not perpetrated by it. The 2019 hack resulted from employee negligence (not leadership fraud), and VeChain actively recovered the majority of funds. Neither incident involved user deception, Ponzi mechanics, exit-scam behavior, or regulatory enforcement. There is no credible allegation of fraud against VeChain as an entity. Scoring 42/WARNING conflates being a victim of security incidents with being a fraudulent operator, which contradicts the band semantics. A score of 65/CAUTIONARY is appropriate: legitimate operator with material historical security caveats (internal control weakness demonstrated in 2019, social media security lapse in 2024) but no unresolved fraud or loss events that endanger current users.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}