US CFTC Backs Kalshi in Ohio Prediction Market Clash

TheNewsCryptoPubblicato 2026-05-13Pubblicato ultima volta 2026-05-13

Introduzione

The U.S. Commodity Futures Trading Commission (CFTC) has filed an amicus brief supporting prediction market platform Kalshi in its legal battle with Ohio. The CFTC argues that an Ohio district court took an "improperly narrow view" of the federal agency's jurisdiction when it allowed the state to order Kalshi to stop offering event contracts, which Ohio deemed unauthorized sports gambling. CFTC Chairman Mike Selig stated the agency will not allow state overreach to undermine its authority over these markets. The case, now before the Sixth Circuit Court of Appeals, could set a significant precedent for federally authorized prediction markets like Kalshi and Polymarket facing state-level restrictions. This marks the second recent instance of the CFTC backing a prediction market against state authorities.

In Kalshi’s legal battle with Ohio, the US Commodity Futures Trading Commission has lent its support, requesting that an appeals court confirm that the commission has authority over prediction markets.

On Tuesday, the CFTC submitted an amicus brief to the Sixth Circuit Court of Appeals, accusing Ohio of engaging in “jurisdictional overreach” when it ordered Kalshi to cease providing sports event contracts in the state last year, citing them as instances of unauthorized sports gambling.

Improperly Narrow View

Following a denial of its motion in March, Kalshi decided to appeal the decision. In October, it sued Ohio authorities, requesting that a federal court prevent the Ohio Casino Control Commission and the state attorney general from acting.

CFTC Chairman Mike Selig said in a statement:

“The federal district court in Ohio took an improperly narrow view of the Commission’s jurisdiction, and we are asking the Court of Appeals to correct that error. As I’ve said repeatedly, the CFTC will not allow overzealous state governments to undermine the agency’s longstanding authority over these markets.”

This case has consequences for big prediction market platforms like Kalshi and Polymarket, and it’s one of several like it that are trying to decide whether states may limit prediction markets that are authorized by the federal government.

This is the second time the CFTC has backed a prediction market; in February, it backed Crypto.com in its legal fight against Nevada authorities in an amicus brief it had submitted with the Ninth Circuit Appeals Court.

The CFTC said in its brief that the agency’s oversight of event contracts traded as swaps or binary options on designated contract markets (DCMs) “threatens regulatory upheaval” due to Ohio’s jurisdictional overreach into the Commission’s realm.

Highlighted Crypto News Today:

eToro Reports Strong Q1 Profit Growth Despite Crypto Trading Slump

TagsBlockchainKalshi

Domande pertinenti

QWhat is the main issue in the legal battle between Kalshi and the state of Ohio?

AThe main issue is whether the state of Ohio has the authority to order Kalshi to stop offering sports event contracts, which Ohio considers unauthorized sports gambling, or if the US Commodity Futures Trading Commission (CFTC) has exclusive federal authority over these prediction markets.

QWhat action did the CFTC take in support of Kalshi, and what was their argument?

AThe CFTC submitted an amicus brief to the Sixth Circuit Court of Appeals. They argued that Ohio is engaging in 'jurisdictional overreach' and that the federal district court in Ohio took an 'improperly narrow view' of the Commission's jurisdiction. The CFTC asserts its longstanding authority over prediction markets traded as swaps or binary options on designated contract markets (DCMs).

QWhat was Kalshi's initial legal action after the motion denial in March?

AFollowing the denial of its motion in March, Kalshi appealed the decision and, in October, sued Ohio authorities. The lawsuit requested that a federal court prevent the Ohio Casino Control Commission and the state attorney general from taking action against Kalshi.

QAccording to the article, what broader consequence does this case have?

AThe case has consequences for major prediction market platforms like Kalshi and Polymarket. It is one of several cases that will help determine whether individual states can limit or regulate prediction markets that are authorized by the federal government.

QIs this the first time the CFTC has supported a prediction market in a legal dispute?

ANo, this is the second time. In February, the CFTC also backed Crypto.com in its legal fight against Nevada authorities by submitting an amicus brief to the Ninth Circuit Court of Appeals.

Letture associate

It Took Me a Year to See the Bitter Truth About Agent Payments

After a year building infrastructure for the Agent economy, engaging with major players like Stripe, Visa, and Coinbase, the author shares a sobering analysis of the current state of Agent payments. The core finding is a stark lack of genuine, immediate demand across most envisioned use cases. The article breaks down four key market segments: 1. **Agent-to-Merchant (Consumer Shopping):** For most product categories (e.g., clothing, electronics), conversational AI shopping is a step backwards from visual e-commerce interfaces. While agents excel at understanding needs, they can't replace side-by-side product comparison. Real merchant interest is defensive "Agent Engine Optimization," not driven by current customer demand. Potential exists for high-frequency, low-decision purchases (like food delivery) or navigating complex store UIs, but these require massive B2C distribution channels dominated by giants like Amazon. 2. **Agent-to-API (Developer Services):** Developers already have subscriptions and billing relationships for APIs (compute, data). Prepaid balances solve micro-payment issues for low transaction volumes. A deeper structural problem is that major SaaS vendors' business models rely on enterprise contracts, resisting granular pay-per-call pricing. While protocols like MPP and x402 serve the long tail of niche services, this market is small and developers are historically low-willingness-to-pay. 3. **Agent-to-Agent:** This remains largely theoretical with minimal transaction volume. While it represents a long-term bet on a fundamentally new transaction infrastructure (sub-second, micro-penny to million-dollar, multi-party settlements), it does not constitute a present market. 4. **Agent-to-Finance:** This is the only category with existing, paying demand. Integrating AI into financial workflows (trading, portfolio management) is a natural evolution and enables new capabilities like autonomous rebalancing. However, competition favors established, regulated institutions. The "real problem" is not moving money between agents, but the broader challenge of **coordination**—orchestrating work between agents and humans, verifying outcomes, and settling results. Payment is just one component of settlement, which is itself part of coordination. Companies that solve the coordination layer will subsume payment, not the other way around. While well-funded incumbents build defensively for a long-term future, startups must find where the market is today—which, for the author's team, lies outside these four categories in an area of real, growing, and underserved activity.

marsbit1 min fa

It Took Me a Year to See the Bitter Truth About Agent Payments

marsbit1 min fa

It Took Me a Year to See the Hard Truth About Agent Payments

**Title: It Took Me a Year to See the Hard Truth About Agent Payments** Over the past year, I've worked on infrastructure for the Agent economy, engaging with major players like Stripe, Visa, Coinbase, and numerous startups. The findings reveal a stark reality: genuine, widespread demand for Agent-based payments does not yet exist. **Key Observations:** * **Agent-to-Merchant (Shopping):** The user experience for AI shopping often falls short, especially for visual product discovery. While AI excels at understanding needs, conversational interfaces can't yet replace browsing and comparing multiple products visually. Current merchant interest is largely defensive ("Agent Engine Optimization") for a future that hasn't arrived. High-frequency, low-friction purchases (like food delivery) are potential fits, but lack open APIs and face high AI inference costs. Simpler, more affordable, or cross-language interactions for complex UIs are a niche opportunity but require massive consumer distribution to scale. * **Agent-to-API (Developer Tools):** Developer payment needs for APIs (computing, data, models) are already met through subscriptions and prepaid credits. The core challenge is not payment friction but supplier economics: most large SaaS providers prefer enterprise contracts over micropayments for API calls. Protocols like MPP and x402 suit the long-tail of smaller services but cater to a developer market historically reluctant to pay for these tools. Major infrastructure needs at the top of the stack are already being addressed. * **Agent-to-Agent (Machine Commerce):** This is a long-term vision with almost no current transaction volume. While a future with high-speed, high-frequency, multi-party machine-to-machine transactions would require novel infrastructure, it remains theoretical. The market is not here yet. * **Agent-to-Finance:** This is the only category with clear, present demand. Financial professionals and DeFi users already pay for tools, and AI augmentation is a natural evolution. Autonomous AI agents can enable entirely new financial strategies. However, competition is fierce from established, regulated incumbents who can more easily layer AI onto their existing products. **The Core Insight:** Companies, especially giants with long time horizons, are building defensively for a potential future of mass machine commerce. For them, early investment is a low-cost hedge. For startups, the current market reality is different. The primary challenge isn't just moving money between agents (payments). The larger, unsolved problem is **orchestration** – coordinating work between agents and humans, verifying outcomes, and then settling. Payment is just a part of settlement, which is just a part of orchestration. Companies that solve the orchestration problem will subsume payments, not the other way around. After a year of building, we see the real, growing, and underserved market opportunity lies in this broader domain of orchestration.

链捕手25 min fa

It Took Me a Year to See the Hard Truth About Agent Payments

链捕手25 min fa

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

A researcher discovered a critical "infinite mint" vulnerability in the Zcash cryptocurrency's Orchard protocol using Claude Opus 4.8, leading to a swift fix but also a 50% market drop, erasing billions in value. This incident highlights a new era where powerful, accessible AI models are dramatically lowering the barrier to finding software vulnerabilities. Previously, the security community feared specialized models like Claude Mythos Preview, capable of finding decades-old zero-day exploits. The Zcash case, however, involved a publicly available, general-purpose model. This shift makes advanced security auditing—and attack capabilities—accessible to far more people, not just experts. The mass democratization of vulnerability discovery brings a dual challenge: a flood of low-quality, AI-generated false reports that overwhelm maintainers, and the real, rapid uncovering of deep, dangerous bugs. Open-source projects, often understaffed and unfunded, are particularly vulnerable to this "attention DDoS." The article cites examples like curl shutting down its bug bounty program due to the unsustainable workload. Our perceived digital safety has often been luck, relying on the high cost and effort required to find deeply hidden flaws in complex systems, as seen with historical vulnerabilities like Heartbleed or Baron Samedit. AI changes this cost structure, effectively "mass-producing flashlights" to illuminate every corner of our codebase. While large companies operate extensive security chains involving external white-hat hackers and massive defensive operations, the global cybersecurity workforce faces a severe shortage, especially of experienced personnel capable of analyzing complex threats and coordinating fixes. The core dilemma emerges: AI makes *finding* bugs cheap and scalable, but *fixing* them remains a slow, expensive, and human-intensive process. The article concludes that AI won't destroy the internet but acts as a bright light, revealing that our digital existence is not inherently secure but is precariously maintained by ongoing human effort. The true cost in the AI era may not be discovery, but whether there will be enough people left willing and able to do the hard work of repair.

marsbit58 min fa

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

marsbit58 min fa

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

"Codex Goal Mode: How to Make AI Work Continuously Toward a Specific Goal" OpenAI's Codex "goal mode" (/goal) transforms the AI from a reactive code assistant into a proactive execution agent capable of working autonomously for hours or even days to achieve a defined objective. To maximize its effectiveness, follow these key principles: 1. **Define Clear, Verifiable Exit Criteria:** The goal prompt should be a concise, measurable success condition, not a lengthy specification. Use quantifiable metrics like "reduce build time by 30%" or "achieve 100% test parity." 2. **Provide Initial Guidance and Tools:** Direct Codex toward likely problem areas and specify available tools (e.g., browsers, testing environments) to prevent it from exploring unproductive paths. 3. **Enable Progress Measurement:** Equip Codex with ways to track advancement, such as creating comparison tools for visual tasks or evaluation sets, ensuring it can gauge its own progress. 4. **Use a Realistic Execution Environment:** For tasks like performance optimization, provide access to environments that closely mimic production (e.g., similar configs, databases) to yield valid results. 5. **Be Cautious with Visual Goals:** Avoid vague "pixel-perfect" instructions. Instead, supplement visual references with functional checklists or design system specifications to prevent Codex from obsessing over minor details. 6. **Implement Progress Tracking:** For long-running tasks, have Codex commit code to draft PRs, update progress documents, or send Slack updates to maintain visibility into its work. 7. **Review and Consolidate Results:** Once the goal is met, instruct Codex to review its work, clean up ineffective experimental code, and reflect on what strategies succeeded or failed. Ultimately, using goal mode shifts the developer's role from writing prompts to managing a persistent engineering agent—defining objectives, establishing metrics, configuring environments, and conducting final reviews.

marsbit2 h fa

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

marsbit2 h fa

Trading

Spot
Futures
活动图片