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_approve · BlackRock USD Institutional Digital Liquidity Fund (BUIDL)
- Sequence
- #3
- Score
- 82 → 82 (0)
- Cluster
- mainnet-beta
- Slot
- 443523623
- Off-chain at
- 2026-08-27T04:14:14.969Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ans3WYo3ikq4pzfQqLCtEisPqSsS5y6VJiFeQCRc3EHD
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2443 chars)
{"actor":"judge","decided_at":"2026-08-27T04:14:14.668Z","decision":"review_approve","investigation_id":"9683fd9b-8608-4fba-9b24-0c1e301c6211","new_score":82,"page_slug":"blackrock-usd-institutional-digital-liquidity-fund","prev_score":82,"reason":"Of 23 checkable claims on this page, 16 were confirmed, 4 partially supported, 1 was stale, and 2 were disputed, with zero unverifiable claims or dead links. That works out to a disputed rate of 8.7% (2 of 23), which falls within the approval range. The two disputed items (claim_findings[9] and claim_findings[16]) are timeline dates for the multi-chain expansion and the $1 billion AUM milestone; both are contradicted by the page's own cited sources by several weeks in a different month, so they are real date errors rather than a known 'default to the first of the month' artifact. However, the underlying events they describe are independently confirmed elsewhere on the page (claim_findings[8] and claim_findings[15]), so these are narrow timeline-precision errors, not disputes over whether something happened or who was involved. No claim alleging wrongdoing was found to be false, and no core allegation is in dispute. The review also raised a high-priority note that the page contains no adverse allegation against BlackRock, Securitize, or BNY Mellon at all -- its own Controversies section states no enforcement actions, lawsuits, hacks, or exploits were found. That note does not identify any inaccuracy or gap in the page's content; it raises a separate editorial question about whether a page like this belongs in the index, which this review process is not positioned to resolve and which is treated here as context rather than a penalty trigger. Two secondary issues are noted for future revision without changing the outcome: the Regulatory Status section omits the Investment Company Act Section 3(c)(7) exemption that explains the fund's qualified-purchaser minimum (claim_findings[4]), and the claimed rise in minimum investment from $100,000 to $5 million (claim_findings[6]) is contradicted by BlackRock's own launch-day materials, which cite a $5 million minimum from inception -- a firmer objection than its 'partially supported' label conveys, though not one that changes the disputed-rate calculation or the banding outcome.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}