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 · Ambient Finance
- Sequence
- #5
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 456641892
- Off-chain at
- 2026-10-14T00:36:19.746Z
- Anchored at
- 2026-10-14T00:36:37.921Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- F7VqQQWGJ5VNwvy3UgiFeUtSnK41b1CxMWW9E5BZxFxt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1190 chars)
{"actor":"reviewer","artifact_identity":"e7d84d762d8374cd27c32f2147b5bb86","decided_at":"2026-10-14T00:36:19.485Z","decision":"review","disputed_pct":0.3333,"findings_hash":"GsJF5K1YLZAmTSju83yWgsFuWbpvHD4iURSKgWCoX94C","investigation_id":"15c90e9f-a964-4aa4-8358-196a48fbbd4d","mode":"findings_only","new_score":59,"page_content_hash":"9f23acc0f997838ec1fe4d87bfc29be94a691e28e404e19433c8631f95297bbe","page_slug":"ambient-finance","prev_score":59,"reason":"The October 2024 DNS hijack facts, the 2023 seed round and the TVL figures are well supported. The main defect is the June 2026 exploit arithmetic: the page's own figures (50 ETH in, 83.72 ETH out) give a net of about $56,700, not $110,600, so the TenArmor loss figure is presented as a net gain it does not match. The claims that the domain was recovered to a hardened registrar and that users were reimbursed are not supported by the cited articles I could read. Several secondary sources were not read in full, including the Medium page (403), CryptoNews, Mitrade, CertiK and SoSoValue.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}