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 · Ambient Finance
View on Solana ↗
Sequence
#3
Score
52 → 42 (-10)
Cluster
mainnet-beta
Slot
425411484
Off-chain at
2026-06-09T21:42:56.451Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CN6HSCEqmmSEWpUqmpao7fpHZerFN6aWbtDGtL55Qbhx
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1313 chars)
{"actor":"judge","decided_at":"2026-06-09T21:42:56.149Z","decision":"review_revise","investigation_id":"da19cc17-dd96-47a4-a5de-9fd11102f484","new_score":42,"page_slug":"ambient","prev_score":52,"reason":"The reviewer confirmed 13 of 16 claims via multiple credible sources, including Tier 1 outlets for the October 2024 DNS hijacking incident. However, claim_findings[8] — the assertion that ZachXBT flagged Ambient Finance — is unverifiable: no source connecting ZachXBT to any investigation of this entity was found, and the DNS attack was identified by Blockaid, not ZachXBT. This claim appears in the public-facing summary and should be removed or sourced before the page is considered accurate. Additionally, the review identified a high-priority coverage gap: a $110K smart contract exploit occurred on June 8, 2026 — one day before this review — which directly contradicts the page's implication that smart contract risk is absent. All six page sections also have empty content and headings, making this page functionally a stub. A score reduction of 10 points is applied pending correction of the unverified ZachXBT claim and addition of the June 2026 exploit.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}