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 · Berachain
View on Solana ↗
Sequence
#2
Score
42 → 42 (0)
Cluster
mainnet-beta
Slot
426514895
Off-chain at
2026-06-14T23:16:19.874Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
6VDx5JJERGJtmYYZQkY64VVASAYA2sXRvJu1PUiXNmyH
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2059 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:19.812Z","decision":"review","investigation_id":"7fafc44c-1a7b-4394-bb99-d5c4ee2f1de3","new_score":42,"page_slug":"berachain","prev_score":42,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Berachain is a legitimate, actively-developed Layer 1 blockchain with institutional backing ($142M raised from Polychain, Brevan Howard Digital, Framework Ventures), mainnet live since February 6 2025, and continued protocol upgrades (Bectra hard fork June 2025, PoL V2 July 2025). No fraud, Ponzi mechanics, exit scam, or regulatory enforcement action has been identified by any credible source. The incidents driving the WARNING-band score are: (1) a $12.86M BEX exploit caused by an inherited Balancer V2 vulnerability that affected many chains simultaneously — fully recovered via white hat and hard fork, making it a suffered-and-resolved incident rather than negligence; (2) an unconfirmed insider-selling allegation based on wallet attribution that was never acknowledged or confirmed; (3) a preferential investor refund arrangement that is unusual but contested and not illegal. The 97% price decline reflects tokenomics dysfunction and mercenary capital, not user-fund loss. Under the post-policy band semantics, WARNING (20–49) requires \"elevated fraud/loss risk or unresolved severe incident.\" The BEX incident is resolved; the insider allegation is unconfirmed; no fraud is evidenced. The correct band is CAUTIONARY (50–69): legitimate project with material caveats — pseudonymous team, aggressive tokenomics, unresolved governance transparency questions around the Brevan Howard side letter. A score of 55 reflects these real but non-fraudulent concerns while correcting the over-penalization for a recovered third-party exploit and unconfirmed allegations.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}