The system is built on a single data line. On August 18, Kalshi filed with the CFTC to launch a perpetual futures contract on the US500 index, tracking the MerQube US Large Cap Index. The filing itself is unremarkable—another product extension from a regulated exchange. But the dependency is what catches my attention. One index provider. One data feed. One point of failure.
Silence before the breach.
Kalshi has already proven its execution capability: crypto perpetuals went live in June 2025, and within a week, the platform reported over $1 billion in notional volume. That is a stress test passed. But the crypto product trades on a different set of data—crypto spot indices are aggregated from multiple exchanges, decentralized by nature. The stock index perpetual, however, relies entirely on MerQube. This is not a technical detail. It is a systemic risk.
Let me step back. Kalshi started as a prediction market platform—binary event contracts on political outcomes, economic data, and weather. It was a niche but compliant business under the CFTC's jurisdiction. Then, in May 2025, it received approval to list crypto perpetual futures. By June, the product was live. By August, it had filed for gold, silver, copper, and stock index perpetuals. The trajectory is clear: Kalshi is migrating from a prediction market operator to a multi-asset derivatives exchange, directly competing with CME and Cboe.
The core mechanism of a perpetual futures contract is the funding rate. It is a periodic payment between long and short positions that keeps the contract price anchored to the underlying index. In crypto, funding rates are calculated from a time-weighted average of premium or discount between the perpetual and the spot index, often using a multi-source oracle. Kalshi's funding rate algorithm is not publicly documented, but the index source is: MerQube. This is a single third-party provider.
Verification > Reputation.
From my experience auditing institutional custody solutions, I have seen how a single data dependency can cascade into a full system failure. In 2022, a major derivatives platform suffered a liquidation cascade because their oracle update lagged by 200 milliseconds. Here, the risk is not milliseconds but minutes. If MerQube's data feed is interrupted—due to technical failure, licensing dispute, or even a cyberattack—the entire stock index perpetual product would be forced to halt or switch to manual pricing. The CFTC would likely require a contingency plan, but the technical reality is that no backup index provider can match the same composition and methodology without introducing basis risk.
Let me dissect the funding rate mechanism. In a perpetual, the funding rate is designed to be a function of the gap between the contract price and the index price. If the gap widens, the rate increases, incentivizing arbitrageurs to trade and bring the price back. The formula is typically:
funding_rate = clamp((contract_price - index_price) / index_price, -0.1%, 0.1%)But this assumes the index price is always available and accurate. If the index feed freezes, the funding rate becomes a function of a stale price. In a volatile market, this can lead to a feedback loop: the contract price diverges, the funding rate fails to correct it, and the divergence amplifies until the system triggers emergency liquidation. The code is simple, but the dependency is brittle.
Code is law, until it isn't.
Kalshi's crypto perpetuals have already demonstrated that the system can handle high volume—$1 billion in notional in the first week. But the crypto product uses a different data infrastructure. Crypto indices are typically derived from multiple exchanges (Binance, Coinbase, Kraken) and are inherently more robust against single-point failure. The stock index perpetual, by contrast, is a single point of failure. The CFTC will likely require Kalshi to demonstrate a backup data source or a fallback mechanism. But the real question is: what happens when the backup is also MerQube, just a different feed?
Now, the contrarian angle. The market is focused on the product innovation and the regulatory battle between CME and the CFTC. CME has sued the CFTC over the approval of Kalshi's crypto perpetuals, arguing that the CFTC exceeded its authority. The lawsuit is currently pending. If the court rules in favor of CME, it could invalidate not only the crypto perpetuals but also the entire application for stock index perpetuals. This is a binary legal risk, not a technical one.
One unchecked loop, one drained vault.
But the deeper risk is not the legal outcome. It is the assumption that a centralized, regulated exchange is inherently safer than a decentralized protocol. In DeFi, we audit the code for vulnerabilities. Here, the code is the funding rate algorithm, and the vulnerability is the dependence on a single index provider. The market is pricing Kalshi's product as a disruptive innovation, but the technical architecture is a traditional client-server model with a single point of failure. The volume numbers are impressive, but they are not a measure of resilience.
From a forensic perspective, I would want to see the following: the exact funding rate formula, the backup index provider agreement, the maximum allowed deviation between contract and index before a circuit breaker triggers, and the historical performance of the index feed under stress. Without these, the product is a black box. The CFTC may have approved the crypto perpetuals, but the stock index perpetual will face a higher bar. The index is a regulated benchmark, and any manipulation or error could have systemic consequences.
Let me connect this to the broader market. The global perpetual futures market is projected to exceed $90 trillion in 2025, according to an industry report Kalshi cited. Even a small share would be significant. But the competition is not just from CME and Cboe. It is from the entire traditional derivatives ecosystem, which has decades of experience in managing index-based products. Kalshi's advantage is regulatory speed and lower fees, but its disadvantage is the lack of a diversified data infrastructure.
Silence before the breach.
I have seen this pattern before. In 2020, during the DeFi summer, I audited a lending protocol that claimed to be decentralized but relied on a single price oracle. The protocol was audited, the code was clean, but the oracle was a single point of failure. When the oracle price diverged due to a flash loan attack, the entire protocol was drained. The lesson is the same: verification starts with the dependencies, not the code.
Kalshi's stock index perpetual is not a DeFi protocol. It is a regulated product with a legal entity behind it. But the technical risk is identical. The funding rate mechanism is a closed-loop system that depends on an external input. If that input fails, the loop breaks. The market may not see this yet, but the first real test will come when the product goes live and faces a period of high volatility. If the index feed lags, the funding rate will be wrong, and the liquidation engine will cascade.
So, what is the forward-looking judgment? The product will likely be approved, because the CFTC has shown a willingness to expand the range of permissible derivatives. But the real risk is not the approval. It is the operational stability after launch. The CME lawsuit adds a layer of legal uncertainty, but even if it is resolved in Kalshi's favor, the technical dependency on MerQube remains. The real vulnerability is not the regulatory battle—it is the single data feed.
Will the market learn this lesson before the first incident? Or will we wait for the breach to confirm the theory?