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_revise · Voltage Finance
View on Solana ↗
Sequence
#3
Score
3225 (-7)
Cluster
mainnet-beta
Slot
423874228
Off-chain at
2026-06-02T19:36:56.883Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
BMU4CwLp2orxdbmZFtmmrG5Wpg5DFef641vKsC5jod6a
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1267 chars)
{"actor":"judge","decided_at":"2026-06-02T19:36:56.733Z","decision":"review_revise","investigation_id":"a0f97084-611a-43c6-bef3-3b6e998f63a6","new_score":25,"page_slug":"voltage-finance","prev_score":32,"reason":"The page is substantially accurate across 30 reviewed claims, with 24 confirmed and 4 partially supported by strong primary sources. One claim is directly disputed (claim_findings[29]): the assertion that Voltage Finance has not announced any formal security audit is contradicted by the protocol's own documentation, which lists multiple Quillhash/QuillAudits reports. This error overstates risk in a minor direction but is a concrete factual inaccuracy that must be corrected. The page should be revised to specify that the exploited SimpleChefStaking contract was not covered by existing audits, rather than implying the protocol has no audit history. Three high-priority coverage gaps — the absence of on-chain transaction evidence, no update on the 2025 exploit recovery or Finland police inquiry, and the audit scope clarification — also warrant editorial expansion before this page can be fully approved.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}