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 · CrediX Protocol Exit Scam
- Sequence
- #3
- Score
- 2 → 0 (-14)
- Cluster
- mainnet-beta
- Slot
- 443521651
- Off-chain at
- 2026-08-26T16:05:22.459Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AEX8uFtCvboYzb7LY1PKafysEbxvHqYzmcpnnRRkzWSw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1666 chars)
{"actor":"judge","decided_at":"2026-08-26T16:05:22.047Z","decision":"review_revise","investigation_id":"17bbcf97-bc64-48ce-b4df-ec30114a0548","new_score":0,"page_slug":"credix-protocol-exit-scam","prev_score":2,"reason":"The core factual chain of this incident — a $4.5M privilege-escalation exploit of a month-old lending protocol, a broken 24-48 hour repayment promise, and the team's subsequent disappearance — is well corroborated across multiple independent, credible outlets (claim_findings[0], [1], [12]). However, the review found that the page's slug and title state 'exit scam' as an established fact, while every source it cites, and every other source the reviewer checked, describes the outcome only as suspected, alleged, or unconfirmed, with no regulator, court, or law-enforcement finding of fraud to date (claim_findings[3]). The review also found a security-audit citation that appears to document an unrelated, years-older project of a similar name rather than the entity under investigation (claim_findings[18]), a misspelled partner-protocol name (claim_findings[14]), a statistic correctly reported but attributed to the wrong outlet (claim_findings[21]), and an absence of a competing technical analysis that reads the same evidence as an external hack rather than an inside job (coverage_gaps[1]). None of these issues call the underlying event into question, but together they show a pattern of the page stating more certainty than its sourcing supports and require correction rather than removal.","score_delta":-14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}