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
- 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. - 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.
- 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 · Veil Cash
- Sequence
- #2
- Score
- 48 → 48 (0)
- Cluster
- mainnet-beta
- Slot
- 423943770
- Off-chain at
- 2026-06-03T03:18:31.025Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 848Fxaa1iBMTjdcSyHJDKTrSjmazjTobdeNUZ3qfmqCt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1210 chars)
{"actor":"reviewer","decided_at":"2026-06-03T03:18:30.955Z","decision":"review","investigation_id":"40f1c3c2-cf2a-4640-9d3a-3f0a5165f29d","new_score":48,"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 of legacy pools draining 2.9 ETH, and the $2.26M FoomCash copycat — is well-supported across multiple independent sources. However, the investigation contains several unverified or incorrect specific details: the Pashov audit is dated January 2025 but the actual report date is February 12, 2025; the protocol launch date (January 2024) and Coinbase EAS integration date (June 2024) have no evidentiary basis; the CryptoTimes and Halborn publication dates in the timeline are wrong (February 26 and March 2 respectively, not March 1); one cited source (dev.to) returns 404; and the specific 22:05 UTC timestamp for fund return is unverifiable. The Halborn source contains a likely-erroneous $427k figure for the Veil Cash loss that contradicts the 2.9 ETH consensus.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}