Audit log

Every state-changing event for Kipseli: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

1. #1publishby system:backfill

   2026-05-29 02:53:09Z
   Score: ? → ? (no score change)
   anchoranchored

   chain

   ●mainnet-betaslot 422,851,212

   sig

   QEwDCG9PxRTB…yDFXa3zKcopyexplorer ↗

   hash

   HEMRM1EMzb37…TvqDk3yWcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (3932 B) ▸

   {"actor":"system:backfill","investigation_id":"b8814fbf-589f-4f7f-a118-9a6aaf9a8b00","kind":"publish","page_slug":"kipseli","published_at":"2026-05-29T02:53:09.353Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Kipseli","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://docs.kipseli.capital/","type":"other","url":""},{"credibility":3,"name":"https://www.kipseli.capital/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rocketreach.co/christos-liatas-email_253384356","type":"other","url":""},{"credibility":3,"name":"https://www.linkedin.com/in/christosliatas/","type":"other","url":""},{"credibility":3,"name":"https://www.linkedin.com/company/kipselicapital","type":"other","url":""},{"credibility":3,"name":"https://vn.linkedin.com/in/tung-nguyen-673a9a1b6","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.livebitcoinnews.com/april-2026-crypto-hacks-hit-620m-as-bridge-failures-and-admin-exploits-dominate-attacks/","type":"other","url":""},{"credibility":3,"name":"https://x.com/ProMint_X/status/2049794641537671581","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://0x.org/post/propamm-shenanigans","type":"other","url":""},{"credibility":3,"name":"https://docs.kipseli.capital/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://docs.kipseli.capital/","type":"other","url":""},{"credibility":3,"name":"https://0x.org/post/propamm-shenanigans","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://x.com/ProMint_X/status/2049794641537671581","type":"other","url":""},{"credibility":3,"name":"https://en.wikipedia.org/wiki/ZachXBT","type":"other","url":""},{"credibility":3,"name":"https://t.me/s/investigations","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.kipseli.capital/","type":"other","url":""}]}],"sources_used":[],"summary":"Kipseli (also styled Kipseli Capital) is a proprietary trading firm and on-chain market-maker founded in early 2018, operating the Kipseli PropAMM on Base Mainnet. The protocol was listed among exploited platforms during the April 2026 wave of DeFi attacks, and the broader PropAMM category to which it belongs was the subject of a March 2026 empirical report by 0x documenting systematic quote-spoofing behavior that caused measurable trader harm. ZachXBT has flagged the entity. No public smart-contract audit or post-incident disclosure has been identified as of May 2026.","timeline":[{"date":"2018-01-01","event":"Kipseli Capital core team begins on-chain market-making operations on Ethereum Mainnet, self-described as early pioneers of the discipline.","source":""},{"date":"2026-03-20","event":"0x publishes 'PropAMM Shenanigans,' empirically documenting systematic quote-spoofing and repricing behaviors by PropAMM operators on Base Mainnet — the same architecture class as Kipseli PropAMM.","source":""},{"date":"2026-04-01","event":"April 2026 wave of DeFi exploits begins with the $285M Drift Protocol breach, initiating the worst month for DeFi security since February 2025.","source":""},{"date":"2026-04-01","event":"Kipseli listed among protocols exploited during the April 2026 DeFi attack wave alongside Giddy, with attackers described as targeting smaller platforms. Specific amount and exploit vector unconfirmed.","source":""},{"date":"2026-05-28","event":"AVOID.NET investigation opened based on ZachXBT flag and protocol logic incident designation. No public post-mortem or official incident disclosure from Kipseli identified as of this date.","source":""}]},"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 6a1d0ee7-6fd9-4a15-bc22-c902f401a513copy
2. #2rescoreby systemsystem

   2026-10-10 18:47:02Z
   Score: 38 → 57 (+19)
   Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 57. Problems weighed by who is responsible: concerns that are not fraud −12.8, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6; legitimacy credit long-running +10.
   anchoranchored

   chain

   ●mainnet-betaslot 455,367,073

   sig

   61FTPTeUYV5s…S5LW5KWQcopyexplorer ↗

   hash

   CAoM5Xr4RmpM…qy933TTncopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (640 B) ▸

   {"actor":"system","decided_at":"2026-10-10T18:47:02.863Z","decision":"rescore","investigation_id":"b8814fbf-589f-4f7f-a118-9a6aaf9a8b00","new_score":57,"page_slug":"kipseli","prev_score":38,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 57. Problems weighed by who is responsible: concerns that are not fraud −12.8, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6; legitimacy credit long-running +10.","score_delta":19,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision e9b14fe6-ac43-4bd3-aaf0-9661587e7eedcopy
3. #3reviewby reviewerreviewer

   2026-10-27 18:49:03Z
   Score: 57 → 57 (no score change)
   Technical claims about the Kipseli docs (addresses, USDC, whitelist, EIP-712 window) are accurate, and the 0x report date and non-naming of Kipseli are correct. Two claims are wrong: the hack count (12 incidents over 20 days, not 20+ protocols in a month) and the $500,000 figure, which is a hypothetical in the 0x report. The exploit allegation against Kipseli rests on a single passing media mention, and the ZachXBT flag is unverified yet stated flatly in the summary. The 0x report does not name Kipseli, so its use as the entity's incident is inference.
   anchoranchored

   chain

   ●mainnet-betaslot 462,177,971

   sig

   J1eebDF2Syhh…6UA4tbYmcopyexplorer ↗

   hash

   5dcu76cPdAuQ…usmG6bxmcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1440 B) ▸

   {"actor":"reviewer","artifact_identity":"73a1c6f292f57497afb5964df83aa377","blocked_count":1,"decided_at":"2026-10-27T18:49:03.228Z","decision":"review","disputed_pct":0.3333,"findings_hash":"6qzXR4bmAMSti9pDBGkfekxzNHzviKZJXREWXejTKkVq","investigation_id":"b8814fbf-589f-4f7f-a118-9a6aaf9a8b00","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":57,"omissions":{"material":0,"total":1},"page_content_hash":"7fabbc4a2a679720040f35a11b04defa1a455283b1f7d6b087064a194a0e9690","page_slug":"kipseli","prev_score":57,"reason":"Technical claims about the Kipseli docs (addresses, USDC, whitelist, EIP-712 window) are accurate, and the 0x report date and non-naming of Kipseli are correct. Two claims are wrong: the hack count (12 incidents over 20 days, not 20+ protocols in a month) and the $500,000 figure, which is a hypothetical in the 0x report. The exploit allegation against Kipseli rests on a single passing media mention, and the ZachXBT flag is unverified yet stated flatly in the summary. The 0x report does not name Kipseli, so its use as the entity's incident is inference.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 2c24cb99-8a3b-4705-a313-19492f653279copy
4. #4review reviseby judgejudge

   2026-10-27 18:49:03Z
   Score: 57 → 57 (no score change)
   Of 12 countable claim findings (one more was excluded because its source blocked the reviewer), 4 were disputed or unverifiable (33%), which falls in the significant-issues band. claim_findings[0] overstates the April 2026 hack count (the source reports 12 incidents over 20 days, not 20+ protocols), and claim_findings[2] presents a 0x hypothetical calculation as a measured estimate. The central allegation that Kipseli was exploited rests on a single passing media mention (claim_findings[1], claim_findings[11]), and the ZachXBT flag is unverified yet stated flatly in the summary (claim_findings[9], claim_findings[10]). Technical claims about the contracts and docs were confirmed, the omission found is minor, and reviewer confidence is moderate, so the penalty sits in the lower part of the band.
   anchoranchored

   chain

   ●mainnet-betaslot 462,177,977

   sig

   hCAxxU7DCHjQ…mEB1byFtcopyexplorer ↗

   hash

   DtjJVdQMgAw8…HBfVPaaocopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1482 B) ▸

   {"actor":"judge","artifact_identity":"73a1c6f292f57497afb5964df83aa377","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:49:03.228Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"b8814fbf-589f-4f7f-a118-9a6aaf9a8b00","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":57,"page_slug":"kipseli","prev_score":57,"reason":"Of 12 countable claim findings (one more was excluded because its source blocked the reviewer), 4 were disputed or unverifiable (33%), which falls in the significant-issues band. claim_findings[0] overstates the April 2026 hack count (the source reports 12 incidents over 20 days, not 20+ protocols), and claim_findings[2] presents a 0x hypothetical calculation as a measured estimate. The central allegation that Kipseli was exploited rests on a single passing media mention (claim_findings[1], claim_findings[11]), and the ZachXBT flag is unverified yet stated flatly in the summary (claim_findings[9], claim_findings[10]). Technical claims about the contracts and docs were confirmed, the omission found is minor, and reviewer confidence is moderate, so the penalty sits in the lower part of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 601a3b06-b5f3-4de0-bfe7-232c4a5ad9c7copy