Skip to main content
AVOID.NET
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 · Tropykus RSK
View on Solana ↗
Sequence
#2
Score
44 → 44 (0)
Cluster
mainnet-beta
Slot
443525947
Off-chain at
2026-08-27T12:07:23.290Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
7VJXMQsSpqgH9Un4Wnb8eTHBkefoxEFUHobAXAsfxJbq
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1519 chars)
{"actor":"reviewer","decided_at":"2026-08-27T12:07:23.196Z","decision":"review","investigation_id":"db07f732-3a6a-48a9-9450-a59c52c3e302","new_score":44,"page_slug":"tropykus-rsk","prev_score":44,"reason":"The page's factual core -- the June 14, 2023 rBTC micro-market rounding-error exploit, its ~$150,000 / ~10%-of-TVL scale, the team's reimbursement pledge, and the revert to Compound's codebase -- is well supported, including by an independent pull of DefiLlama's raw hacks/TVL data that corroborates the page's own cited source. However, three dated timeline entries (the two RSK launch dates and the reimbursement-commitment date) use likely first-of-month placeholder dates that don't match the actual reported dates, and a fourth (the funding-round date) is confirmed by most aggregators but conflicts with one Messari data point. More importantly, all six sections are structurally present with sources and severity ratings but contain zero narrative content, one section's sole source (ZachXBT/Wikipedia) has no discoverable connection to Tropykus, one cited bug-bounty source (HackenProof) now appears to be link rot / a mismatched citation given reporting points to an Immunefi bounty instead, and the page nowhere mentions that Tropykus announced a full protocol wind-down in 2026, which is now the most materially relevant fact about the entity's current status.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}