# Creator Pulse: Phantom's Kalshi rollout makes the wallet's legal boundary concrete Creator Pulse, edition 1. Published 2026-10-24. 6 min read. Canonical page: https://www.w3match.com/reports/creators-2026-10-24 Phantom's US prediction-market rollout offers a concrete story about where wallet software ends and a regulated trading account begins. Initia's security incident raises a separate question about backing: newly minted tokens and assets actually extracted are different loss measures. Both stories reward an explanation of the user journey, rather than treating an app or blockchain as one uniform service. ## In one minute - Phantom's US prediction-market rollout offers a concrete story about where wallet software ends and a regulated trading account begins. - Initia's security incident raises a separate question about backing: newly minted tokens and assets actually extracted are different loss measures. - Both stories reward an explanation of the user journey, rather than treating an app or blockchain as one uniform service. ## The lead story ### One interface connects two different responsibilities Phantom said on 23 October it was [beginning a US rollout of prediction markets through Kalshi](https://phantom.com/learn/blog/phantom-puts-its-cftc-no-action-relief-to-work-bringing-prediction-markets-to-us-users), with access expanding over several weeks. Users complete identity verification within the app, a third party handles identity information, and Kalshi approves and holds trading accounts and executes submitted trades. Availability remains jurisdiction-dependent. **Why now:** The rollout turns an earlier regulatory position into a visible product journey. A user can encounter a regulated event contract inside an app associated with self-custody. That makes the handoff between software, identity services and an exchange a timely subject for explanation. The announcement establishes a rollout, without measuring how many people have traded. **An angle worth explaining:** Follow the order from the user's screen to the entity responsible for execution. A common interface can simplify discovery and navigation while leaving the underlying account relationship with a separate business. A creator can show that distinction through the approval and execution steps, giving readers a practical way to understand who does what. In [CFTC Staff Letter 26-09, dated 17 March 2026](https://www.cftc.gov/csl/26-09/download), staff provided conditional no-action relief concerning introducing-broker registration and related personnel registration for Phantom's proposed activities. The arrangement described limits Phantom to passively providing software, without discretion over routing or execution or generating express buy or sell signals. Conditions include disclosures about relationships and conflicts, including fees, and relevant risk disclosures. This creates a product-design question: how much functionality can an interface add while retaining the role described in the relief? Showing markets, transmitting a user's instruction and deciding how an order should be executed are meaningfully different functions. The document supplies an actual boundary to examine, rather than a general claim that wallets have become exchanges. The commercial attraction is understandable. A familiar interface can reduce the work of finding a product and navigating to it. The counterargument is that familiarity can obscure a change in responsibility. Users may assume the same custody and support arrangements apply throughout an app, even where a separate account and provider take over. **What remains uncertain:** Actual uptake and availability of individual market categories need evidence beyond the launch announcement. The conditional staff position does not settle every jurisdictional question about prediction markets. A fair account should keep the rollout, the letter's scope and commercial results separate. ## More stories worth covering ### Initia's incident puts the backing of bridged assets under scrutiny Initia halted its base chain and rollups following a security incident on 23 October, according to [The Block's contemporaneous reporting](https://www.theblock.co/news/defi/2026-10-23-initia-halts-network-after-security-incident-attacker-reportedly-mints-tokens-427755). The outlet attributed preliminary findings to co-founder Ezaan Mangalji: an issue in the MoveVM implementation allowed unauthorized minting, with approximately $2.7 million of AUSD, ETH and USDC bridged out before the pause. These remain attributed preliminary findings, rather than a final incident accounting. **Why now:** The event is recent and affects a basic promise of bridged assets: that a token accepted on one network corresponds to backing or a valid claim elsewhere. It gives creators a concrete incident through which to explain that promise. A chain's ability to issue or transfer a token and its economic validity are separate properties. **An angle worth explaining:** Use a balance-sheet diagram. Show the asset held in reserve, its representation on another chain and the redemption process connecting them. If representations can be created without expected backing, redeeming them can transfer the deficit to the reserve or other holders. This explains the general failure mechanism under investigation, rather than asserting which component ultimately bears responsibility. [Bitquery's on-chain investigation, checked on 23 October](https://bitquery.io/investigations/initia-hack), distinguishes approximately $7.48 million of unauthorized tokens at face value from about $2.73 million in assets it traces to Ethereum. Its account says the balance could not all be realized at nominal prices. These are the investigator's measurements at its stated check, without establishing eventual recovery or customer shortfall. The discrepancy offers a stronger angle than selecting the largest damage number. Face value assumes a token can be exchanged at its reference price. Extracted value measures assets obtained through available routes. Final losses can differ again after recovery, reserve reconciliation and decisions about affected claims. Readers need those quantities labeled before they can compare reports responsibly. A halt introduces a further trade-off. Stopping activity may limit additional damage while preventing legitimate users from moving assets. That makes the restart process material: operators need confidence in the corrected system and in the balances it will recognize. Speed alone is an incomplete recovery measure if underlying claims remain disputed. **What remains uncertain:** Final root cause, reconciled user impact and recovery outcome require a postmortem and subsequent evidence. Preliminary attribution to a minting issue does not itself prove that the bridge protocol failed. Avoid assigning blame to a transport system merely because it carried affected assets. ## What could enter the conversation next Phantom's announced expansion over the coming weeks provides an observable rollout window, rather than a deadline for universal access. Useful follow-up reporting would document an eligible user's account approval, disclosures before trading and the division of responsibilities after an order. Adoption claims should wait for actual usage evidence with a defined period. For Initia, the next meaningful developments are a technical explanation, an account of affected backing and a documented recovery or restart process. These are conditions to watch, without an assumed completion date. An update should distinguish a corrected estimate from a new loss, and a proposed restart from a completed one. The subjects invite different forms of evidence. A product demonstration establishes which steps a user sees; legal documents establish stated responsibilities behind them. An incident timeline needs transactions and operational notices, followed by reconciliation. Matching evidence to each question will produce a more useful follow-up than treating every announcement as proof that an entire system works. ## Sources - [beginning a US rollout of prediction markets through Kalshi](https://phantom.com/learn/blog/phantom-puts-its-cftc-no-action-relief-to-work-bringing-prediction-markets-to-us-users), phantom.com, Publication date not specified - [CFTC Staff Letter 26-09, dated 17 March 2026](https://www.cftc.gov/csl/26-09/download), www.cftc.gov, Publication date not specified - [The Block's contemporaneous reporting](https://www.theblock.co/news/defi/2026-10-23-initia-halts-network-after-security-incident-attacker-reportedly-mints-tokens-427755), www.theblock.co, Publication date not specified - [Bitquery's on-chain investigation, checked on 23 October](https://bitquery.io/investigations/initia-hack), bitquery.io, Publication date not specified Every number names its provider and date. Not financial advice.