Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · YLDS
View on Solana ↗
Sequence
#2
Score
68 → 68 (0)
Cluster
mainnet-beta
Slot
443525006
Off-chain at
2026-08-27T09:13:06.719Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
BDNuSidysi4U6x1F8jGg15tkUbUZQVAH783aXWYR5Bxg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1200 chars)
{"actor":"reviewer","decided_at":"2026-08-27T09:13:06.482Z","decision":"review","investigation_id":"c9a7dafa-e8b7-4f9f-876e-a9516ccf7572","new_score":68,"page_slug":"ylds","prev_score":68,"reason":"The page's core regulatory characterization of YLDS (SEC-registered face-amount certificate/debt security, not a money market fund, SOFR-35bps yield, issuer identity, data breach details, and short-seller allegations) is well-supported by primary SEC filings and independent reporting, with no accepted community submissions to separately audit. The main weaknesses found are internal date/arithmetic inconsistencies in the timeline (an IPO 'completion' date, a Solana launch date, and a secondary-offering pricing date that each conflict with the issuer's own specific dated press releases, plus a market-cap figure described as 'up from' a larger prior figure), a stale pairing of a current loan total with an outdated partner count, and a summary-level 'stablecoin' label that sits in tension with the page's own more careful 'security' framing in the body.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}