Skip to main content
AVOID.NET
← 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.

Sequence
#2
Score
3232 (0)
Cluster
mainnet-beta
Slot
443512799
Off-chain at
2026-08-25T08:23:55.377Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
5nLK8pf2QFtgPWwmU15USPd9ttFcLREg3csVBKfMo8FL
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2030 chars)
{"actor":"reviewer","decided_at":"2026-08-25T08:23:55.233Z","decision":"review","investigation_id":"2b04a3b8-f566-4bd0-9324-52dcd43720db","new_score":32,"page_slug":"letsbonk-fun","prev_score":32,"reason":"The page's core narrative (platform launch, rapid mid-2025 market-share surge and subsequent collapse, March 2026 domain hijack, bundler-tooling mechanics, and third-party Pump.fun litigation) is well corroborated by independent tier-1 and tier-2 reporting, and several specific figures (the July 8-9, 2025 volume/share numbers, the January 2026 $352,793 revenue-surge figure, the 58% fee split, and the Solidus Labs rug-pull statistics) were verified verbatim against their cited sources. However, several individual claims show real problems: a citation for year-end-2025 market-share/revenue figures points to a URL that is actually about an unrelated March 2026 hijack story (and independently returns HTTP 410 Gone); the claim that no financial loss was confirmed from the March 2026 hack is contradicted by independent reporting of a Bubblemaps/team-confirmed ~$23,000-$30,000 loss, and the $50,000/10-second figure cited alongside it is drawn from an unrelated phishing incident in the same source article; and the page's description of the Bonk, Inc. (BNKK) relationship as merely a 'distinct but separate' entity understates that the underlying SEC filing itself labels it a related-party arrangement now entitling Bonk, Inc. to 51% of gross platform revenue in perpetuity. The rebrand-direction question specifically requested for review (LetsBonk.fun to Bonk.fun) is supported by the page's own primary cited hijack source (which explicitly calls it 'formerly known as LetsBONK'), but earlier 2025 reporting explicitly denied a rebrand had occurred at that time, making the overall naming history genuinely ambiguous rather than a clean, confidently one-directional fact.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}