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
publish · Kame Aggregator
- Sequence
- #1
- Score
- →
- Cluster
- mainnet-beta
- Slot
- 422338843
- Off-chain at
- 2026-05-26T18:30:27.517Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BLtpgafuVgTLumRW5TbHDB7apBaW2YWfxsnjMyfBpFiM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (5126 chars)
{"actor":"system:backfill","investigation_id":"fc3166bc-cdac-442b-a51b-eae4fce81fe4","kind":"publish","page_slug":"kame-aggregator","published_at":"2026-05-26T18:30:27.431Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Kame Aggregator","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://kameagg.substack.com/p/post-mortem-kame-aggregator-exploit","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/kame","type":"other","url":""},{"credibility":3,"name":"https://quadrigainitiative.com/casestudy/kameaggregatorswapfunctionarbitraryexecutorcallbug.php","type":"other","url":""},{"credibility":3,"name":"https://blockonomi.com/kame-aggregator-on-sei-hit-by-1m-exploit-hacker-returns-185-eth","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://kameagg.substack.com/p/post-mortem-kame-aggregator-exploit","type":"other","url":""},{"credibility":3,"name":"https://quadrigainitiative.com/casestudy/kameaggregatorswapfunctionarbitraryexecutorcallbug.php","type":"other","url":""},{"credibility":3,"name":"https://blog.verichains.io/p/the-hidden-danger-of-unlimited-token","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.cryptopolitan.com/kame-aggregator-recovers-185-eth/","type":"other","url":""},{"credibility":3,"name":"https://coinedition.com/kame-aggregator-185eth-recovery-sei-hack/","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/kame","type":"other","url":""},{"credibility":3,"name":"https://www.mexc.com/news/95334","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.mexc.com/news/95334","type":"other","url":""},{"credibility":3,"name":"https://phemex.com/news/article/kame-aggregator-recovers-185-eth-posthack-plans-user-compensation-18436","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/kame","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://stouy.com/kame-dex-aggregator-on-sei-guide/","type":"other","url":""},{"credibility":3,"name":"https://web3.bitget.com/en/dapp/kame-aggregator-31324","type":"other","url":""},{"credibility":3,"name":"https://tracxn.com/d/companies/kame/__8YJXssv554ck8xcBPEZIFCjFYJLEEmiehR6l3qua8rU/founders-and-board-of-directors","type":"other","url":""},{"credibility":3,"name":"https://alphagrowth.io/kame-aggregator","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://revoke.cash/exploits/kame","type":"other","url":""},{"credibility":3,"name":"https://kameagg.substack.com/p/post-mortem-kame-aggregator-exploit","type":"other","url":""}]}],"sources_used":[],"summary":"Kame Aggregator is a decentralized exchange (DEX) aggregator protocol built on the Sei blockchain, launched in late May 2025, designed to route token swaps across multiple liquidity sources for optimal pricing. On September 13, 2025, the protocol suffered a critical smart contract exploit in which approximately $1.325 million was drained from 830 user wallets via an arbitrary external call vulnerability in its swap() function. The primary exploiter returned approximately $946,000 after negotiations, while secondary exploiters retained approximately $357,000; the team initiated a compensation program that reached over $1 million USDC in distributions by November 2025.","timeline":[{"date":"2025-05-01","event":"Kame Aggregator launches on the Sei blockchain as the network's first native DEX aggregator, aggregating liquidity from 12+ sources.","source":""},{"date":"2025-09-13","event":"Critical exploit in the AggregationRouter swap() function; attackers abuse arbitrary external call vulnerability and unlimited token approvals to drain approximately $1.325 million from 830 user wallets.","source":""},{"date":"2025-09-13","event":"Kame team detects exploit and immediately alerts users across X, Telegram, and Discord to revoke token approvals. Platform temporarily closes.","source":""},{"date":"2025-09-13","event":"Kame team establishes direct contact with primary exploiter and begins negotiation.","source":""},{"date":"2025-09-14","event":"Primary exploiter accepts 20% bounty offer and transfers 185 ETH (~$946,195) to Kame's recovery wallet via on-chain Ethereum transaction.","source":""},{"date":"2025-09-14","event":"White hat hackers recover an additional approximately $21,900 from the exploit.","source":""},{"date":"2025-09-14","event":"Kame publishes post-mortem detailing the vulnerability, affected contracts, and five-point remediation plan.","source":""},{"date":"2025-10-01","event":"Kame begins rolling out compensation distributions to affected users in multiple stages.","source":""},{"date":"2025-11-01","event":"Cumulative compensation distributions exceed $1,031,115 USDC across all stages; team states commitment to 100% reimbursement.","source":""}]},"v":1}