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_approve · Lifinity
- Sequence
- #5
- Score
- 52 → 47 (-5)
- Cluster
- mainnet-beta
- Slot
- 425203350
- Off-chain at
- 2026-06-08T22:42:58.900Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CuaJdn9tMGsKzP4qB2EhMh8VBUrxsF6b3UwawbKeBZXn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1591 chars)
{"actor":"judge","decided_at":"2026-06-08T22:42:58.688Z","decision":"review_approve","investigation_id":"30f3b00f-4dbe-4c67-8079-5c7a44d6d822","new_score":47,"page_slug":"lifinity","prev_score":52,"reason":"The review confirms 22 of 32 claims outright, with one disputed claim and five partially supported claims, placing the disputed rate at 9.4% — just under the 10% threshold for mandatory revision. The single disputed finding (claim_findings[29] / timeline[3]) identifies the veIDO date as stated July 2022 throughout the page when official Lifinity documentation and contemporaneous news articles confirm the event occurred April 23 2022; the raise amount is accurate, making this a factual date error rather than a fabrication. The page's $150 billion lifetime volume figure is modestly overstated relative to DeFiLlama on-chain data showing $139.97 billion (claim_findings[1]). The primary CoinTelegraph citation for the 2023 pool drainage incident returns HTTP 404 link rot (claim_findings[4]), though the underlying facts are fully corroborated by an independent live Cryptopolitan source. Two high-priority coverage gaps remain open — on-chain verification of the $43.4 million treasury distribution and the absence of a published smart contract audit for the core AMM — but open gaps indicate expansion opportunities, not grounds for denial. The page should be corrected on the veIDO date and volume figure before the next review cycle.","score_delta":-5,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}