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 · Antier Solutions
- Sequence
- #3
- Score
- 62 → 47 (-15)
- Cluster
- mainnet-beta
- Slot
- 443524252
- Off-chain at
- 2026-08-27T06:08:36.642Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 83NitUrKyPzjHRN1rqFdaNetabYnLd6zstFzAvMPvKL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1811 chars)
{"actor":"judge","decided_at":"2026-08-27T06:08:36.403Z","decision":"review_revise","investigation_id":"267d153e-70a8-4b9d-9d10-4c100539b9f4","new_score":47,"page_slug":"antier-solutions","prev_score":62,"reason":"The reviewer's own math checks out: 6 of 33 claims are disputed and none are unverifiable, putting disputed content at 18.2% of the page — solidly in the range where a page needs correction, not removal. The most serious problem is that the page's Regulatory and Legal Status and Fraud and Scam Allegations sections flatly state no SEC/CFTC/DOJ action was found as of June 2026 (claim_findings[28], claim_findings[29]), when DOJ publicly announced in March 2026 — months before that stated cutoff — a wire-fraud indictment naming an employee of the exact registered legal entity this page profiles (claim_findings[26]). The reviewer is careful to note this does not implicate the three named executives personally, which limits the harm to a factual-omission problem rather than a defamation problem. Two smaller but real problems compound this: the page presents a directory site's generic template heading as if it were an actual fraud report, when the underlying listing appears to describe an unrelated, similarly named company (claim_findings[27]), and the stated 2005 incorporation date is contradicted by consistent official-registry records showing 2011 (claim_findings[1], claim_findings[2]). The bulk of the page — leadership names and titles, the GVFL funding round, the NIELIT partnership, and review-platform statistics — held up under independent verification, which is why this warrants required revisions rather than denial or delisting.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}