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 · United Stables (U)
- Sequence
- #2
- Score
- 48 → 48 (0)
- Cluster
- mainnet-beta
- Slot
- 443525352
- Off-chain at
- 2026-08-27T10:41:39.257Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7xvifkf629hWJYiws9JHFzERHh328FScp5HQoJysaGZB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1159 chars)
{"actor":"reviewer","decided_at":"2026-08-27T10:41:38.833Z","decision":"review","investigation_id":"eb936eda-2c70-449f-8e13-283e5982728e","new_score":48,"page_slug":"united-stables-u","prev_score":48,"reason":"Most of the page's factual claims about United Stables (launch date, entity structure, exchange listings, regulatory self-disclosure, and the two documented liquidity/peg events) were independently confirmed against directly-fetched primary sources. However, the page's central reserve-verification claim -- that the company reported reserves of 1,010,308,683 U matching circulating supply as of June 18, 2026 -- directly contradicts its own cited source, which states no public reserve data is known; the page also omits a 3.18% peg deviation recorded by its own cited CoinGecko source days after launch while asserting a tight 0.05% peg band, and its claim of a Coinbase listing could not be corroborated and appears likely incorrect. No accepted community submissions existed to independently spot-check.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}