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 · Lifinity
- Sequence
- #3
- Score
- 62 → 52 (-10)
- Cluster
- mainnet-beta
- Slot
- 425150724
- Off-chain at
- 2026-06-08T16:53:25.640Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- B6k68YehM58woXi88ePGt7wMvfZS4rtBj2F3cfDeo2wv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1424 chars)
{"actor":"judge","decided_at":"2026-06-08T16:53:25.447Z","decision":"review_revise","investigation_id":"30f3b00f-4dbe-4c67-8079-5c7a44d6d822","new_score":52,"page_slug":"lifinity","prev_score":62,"reason":"21 of 27 claims were confirmed by independent sources; the page is broadly accurate on the shutdown details, treasury distribution, security incident, and market position. Two material factual errors require correction: claim_findings[20] states the LFNTY veIDO starting price was $0.42, but Lifinity's own Tier 1 documentation records 0.839028 USDC — the page appears to have cited a discounted lock-adjusted effective price from a community article rather than the official market opening price. claim_findings[21] places the veIDO in July 2022 in the timeline, but official documentation and multiple independent analyses confirm the event occurred April 23–24, 2022. Both errors originate from the same Tier 3 community research piece used in preference over the project's own documentation. A CoinTelegraph citation for the December 2023 security incident returns HTTP 404 (link rot), though the underlying facts are independently confirmed by a live Cryptopolitan source. These errors are confined to the token-launch section and do not affect the core risk narrative.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}