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_revise · Ambient Finance
- Sequence
- #3
- Score
- 58 → 48 (-10)
- Cluster
- mainnet-beta
- Slot
- 443524512
- Off-chain at
- 2026-08-27T06:09:23.337Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BpKGMxTA6vV3Npngbgz9RVC5oUJWLcWewm7STDUps3Ws
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1979 chars)
{"actor":"judge","decided_at":"2026-08-27T06:09:23.158Z","decision":"review_revise","investigation_id":"15c90e9f-a964-4aa4-8358-196a48fbbd4d","new_score":48,"page_slug":"ambient-finance","prev_score":58,"reason":"Of 24 fact-checked claims, 5 were disputed and 4 partially supported, giving a disputed rate of 20.8% (5/24), which falls in the moderate-minor band. The most notable defect (claim_findings[12]) is that the page's sentence deriving a 'net gain of roughly $110,600' from 50 ETH seeded and 83.72 ETH withdrawn does not follow arithmetically (83.72 - 50 = 33.72 ETH, ~$56,700) -- but the $110,600 total-loss figure itself is independently corroborated elsewhere on the page (claim_findings[11]), so this is a flawed derivation sentence rather than a wrong headline number. Separately, the page understates Ambient's cumulative trading volume by roughly 10x against its own cited DefiLlama source (claim_findings[15]), and three timeline dates around the 2023 mainnet launch and the October 2024 DNS-hijack recovery are off by days to weeks against contemporaneous or primary sources (claim_findings[20], [22], [23]) without changing the substance of what happened. Weighing in the page's favor, it avoided two of the most common defects in this review process: it did not assert the single-contract design as a confirmed cause of the exploits (claim_findings[13]) and it correctly avoided treating an investor relationship (Quantstamp) or an automated scoring tool (CertiK Skynet) as a real audit (claim_findings[16]). No citations were found to be dead or stale. A high-priority coverage gap was flagged: the page never examines who controls admin/upgrade keys on the single contract, which is directly relevant to its own stated risk thesis and should be addressed even though it does not itself constitute a factual error.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}