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 · Veil Cash
View on Solana ↗
Sequence
#3
Score
48 → 38 (-10)
Cluster
mainnet-beta
Slot
423943776
Off-chain at
2026-06-03T03:18:31.126Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
6UbtxyB86cqgY2tWMFQaBCmVGroKPTeUkVapaH1iwxZz
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1483 chars)
{"actor":"judge","decided_at":"2026-06-03T03:18:30.955Z","decision":"review_revise","investigation_id":"40f1c3c2-cf2a-4640-9d3a-3f0a5165f29d","new_score":38,"page_slug":"veil-cash","prev_score":48,"reason":"The core narrative — Veil Cash as a Base L2 ZK privacy protocol, the February 2026 Groth16 exploit draining 2.9 ETH from legacy pools, funds returned by the exploiter, and the subsequent $2.26M FoomCash copycat — is well-confirmed by multiple independent Tier 1 sources. However, the review found 18.75% of claims disputed or unverifiable. Two claims are disputed: the Pashov audit completion date (page states January 2025; Pashov's public audit index shows February 12, 2025 per claim_findings[7]) and a conflict with the Halborn source, which attributes $427k to the Veil Cash hack — an apparent error by Halborn that contradicts the consensus 2.9 ETH figure confirmed across four independent sources (claim_findings[15]). Two additional timeline dates (protocol launch January 2024; Coinbase EAS June 2024) are unverifiable and likely inaccurate given GitHub org history (claim_findings[5], [6]). One cited source returns 404 (claim_findings[16]). Two high-priority coverage gaps — on-chain transaction anchors and the protocol launch date — remain unaddressed and should be resolved before the page is considered authoritative.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}