Skip to main content
AVOID.NET
← Kipselireviewed 2026-10-27 · 13 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Kipseli against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #1[disputed][awaiting moderator]in section: April 2026 Security Incident
    “which collectively caused approximately $620 million in losses across more than 20 protocols in a single month”
    reviewerApril 2026 exploits affected more than 20 protocols in a single monthThe cited article gives 12 incidents over 20 days, not 20+ protocols in a month. The $620M figure matches.
    Proposed correction (not yet applied)
    which collectively caused approximately $620 million in losses across 12 separate incidents in 20 days
  2. #3[disputed][awaiting moderator]in section: Protocol Logic and Quote-Spoofing Concerns (PropAMM Category)
    “0x estimated that a single PropAMM source operating at approximately $1 billion in monthly volume was delivering $500,000 per month less to traders than the quoted price.”
    reviewer0x estimated one PropAMM at ~$1B monthly volume delivered $500,000/month less to tradersThe page presents an illustration as an observed measurement.
    Proposed correction (not yet applied)
    0x illustrated that a single PropAMM source operating at $1 billion in monthly volume and overquoting by 5 basis points would deliver about $500,000 per month less to traders than the quoted price.

unverifiable

3 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #8[unverifiable][awaiting moderator]in section: Background and Overview
    “launching operations in early 2018”
    reviewerFounded / operations began in early 2018Founding year not found in the docs I fetched. It may be on the main site, which I did not check.
  2. #9[unverifiable][awaiting moderator]in section: April 2026 Security Incident
    “Kipseli appeared in a community-sourced list of hacked protocols in 2026 that also included Drift Protocol, KelpDAO, Rhea Lend, Volo Vault, Juicebox, Thetanuts Finance, and others.”
    reviewerKipseli appeared in a community hack list including Drift, KelpDAO etc.X post is not readable without login and was not fetched.
  3. #10[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Signals
    “According to AVOID.NET's intake data, ZachXBT — the pseudonymous blockchain investigator and Paradigm incident response advisor — has flagged Kipseli.”
    reviewerZachXBT has flagged KipseliThe page itself says this is unverified. The summary states 'ZachXBT has flagged the entity' flatly, which is stronger than the body.

partially supported

6 claims

The cited evidence supports part of the claim but not all of it.

  1. #2[partially supported][awaiting moderator]in section: April 2026 Security Incident
    “A contemporaneous report by Live Bitcoin News noted: 'Further exploits hit Kipseli and Giddy, showing attackers continued targeting smaller platforms.'”
    reviewerLive Bitcoin News quote about Kipseli and GiddyKipseli is named in the article, but only in one passing mention with no detail. No independent source corroborates an exploit of Kipseli.
  2. #5[partially supported][awaiting moderator]in section: Protocol Logic and Quote-Spoofing Concerns (PropAMM Category)
    “The 0x report constitutes the protocol logic incident most consistent with the 'protocol logic incident' flag associated with this entity.”
    reviewerThe 0x report is the 'protocol logic incident' for this entity; summary says the category was documented as causing measurable harmThe linkage to Kipseli is inferential only. The page does state that Kipseli's involvement is unconfirmed, which is appropriate.
  3. #6[partially supported][awaiting moderator]in section: Protocol Logic and Quote-Spoofing Concerns (PropAMM Category)
    “A third behavior documented as 'phantom liquidity' involves providers depositing liquidity in the final Flashblock, collecting block rewards, and immediately withdrawing before trades execute.”
    reviewerPhantom liquidity is a third PropAMM behaviorBehavior is real in the report but is not PropAMM-specific, so attributing it to PropAMM operators overstates.
  4. #11[partially supported][awaiting moderator]in the summary
    “ZachXBT has flagged the entity.”
    reviewerSummary states ZachXBT flag as factBody hedges the flag as low confidence and unverified; the summary does not.
  5. #12[partially supported][awaiting moderator]in the summary
    “The protocol was listed among exploited platforms during the April 2026 wave of DeFi attacks”
    reviewerSummary states Kipseli was listed among exploited platforms, while the exploit itself is unconfirmedAccurate as 'listed', but rests on one low-tier mention. My own search found no other Kipseli exploit coverage.
  6. #13[partially supported][awaiting moderator]in the timeline
    “April 2026 wave of DeFi exploits begins with the $285M Drift Protocol breach, initiating the worst month for DeFi security since February 2025.”
    reviewerDrift Protocol $285M breach began April 2026 waveDollar figure confirmed; ordering and comparison not checked. Timeline entry has no source.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #4[confirmed][no action needed]in section: Protocol Logic and Quote-Spoofing Concerns (PropAMM Category)
    “On March 20, 2026, 0x published an empirical research report titled 'PropAMM Shenanigans'”
    reviewer0x report published March 20, 2026 and did not name KipseliDate and non-naming of Kipseli are correct.
  2. #7[confirmed][no action needed]in section: Background and Overview
    “Smart-contract deployments identified on Base Mainnet include the Router (PropAmm) at 0x71c2ed90cc288229be59f26b8b3eef3c07d7ab99”
    reviewerKipseli PropAMM is on Base Mainnet, quotes in USDC, whitelist-gated, with the listed contract addresses and 10-second EIP-712 windowAddresses, USDC quoting and whitelist match docs. The page's Base-only framing omits other chains.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.