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 · Rainberry Inc
- Sequence
- #3
- Score
- 25 → 13 (-12)
- Cluster
- mainnet-beta
- Slot
- 443514679
- Off-chain at
- 2026-08-25T13:41:23.988Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4FRjUPgRnAyeRdmr3wF91C8dVeQuSQZ98JzxmgwoAMsW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2569 chars)
{"actor":"judge","decided_at":"2026-08-25T13:41:23.558Z","decision":"review_revise","investigation_id":"ddc1afee-2423-49f7-bee7-0f9cee732ccc","new_score":13,"page_slug":"rainberry-inc","prev_score":25,"reason":"The page's core narrative -- the 2023 SEC complaint, the March 2026 $10 million settlement, dismissal with prejudice, no admission of wrongdoing, and the correct separation of Rainberry's corporate penalty from Justin Sun's lack of any personal penalty -- is confirmed against primary SEC litigation releases (claim_findings[1]-[4], [15]-[20]). Disputed and unverifiable claims come to 20% of the total (claim_findings[22], [23], [24], [25], [26], [31], [34]), placing this in the minor-to-moderate revision range, but two of those errors both overstate named individuals' legal exposure in the same direction: the page states six celebrity co-defendants each paid roughly $400,000, when the SEC's own release gives that as a combined total across all six (claim_findings[22], [34]), and it describes Austin Mahone as an active defendant through the March 2026 resolution when his case was actually concluded by final judgment in August 2023 (claim_findings[23], [24]). A same-direction pattern like this is more concerning on a risk-intelligence page about real people than the same count of errors split between over- and understating exposure, since it reads as a consistent bias rather than noise, and the raw disputed-claim percentage does not distinguish the two. The page also contains a chronologically impossible date -- a celebrity settlement timeline entry dated January 1, 2023, before the March 22, 2023 complaint that created the underlying claims (claim_findings[34]) -- plus a mismatched citation on the BTT launch date and a shaky sourcing basis for a claimed 2025 class action (claim_findings[25], [26]). The reviewer also flagged a high-priority gap: the summary and 'Company Background' section describe Rainberry as the 'developer' and 'operator' of the open BitTorrent protocol, conflating the company with technology it doesn't control, though the page does correctly keep Rainberry's corporate liability separate from Sun's personal exposure. No link rot or stale citations were found. Taken together, this supports a revision rather than approval or denial, with a penalty toward the higher end of the applicable range given the person-specific errors and the internally inconsistent date.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}