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

Independent verification

1. Database (off-chain)
GAWgPSdVWm6V8fJ5dHSBnQUs3njjVZ7GQYypn7GW6AJ6
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (951 chars)
{"actor":"reviewer","decided_at":"2026-06-09T21:42:56.149Z","decision":"review","investigation_id":"da19cc17-dd96-47a4-a5de-9fd11102f484","new_score":52,"page_slug":"ambient","prev_score":52,"reason":"The core factual claims about Ambient Finance's identity, architecture, funding round, and the October 2024 DNS hijacking incident are well-supported by multiple credible sources. The single significant red flag is the unverified assertion that ZachXBT flagged the entity — no evidence of this was found, and the DNS attack was identified by Blockaid. A material coverage gap exists: a $110K smart contract exploit occurred on June 8, 2026 (the day before this review), contradicting the implication that smart contract risk is absent. The tokeninsight.com cited URL returns HTTP 403 and is effectively dead.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}