Technology

Polymarket Enables Instant Bitcoin Lightning Deposits via Spark

Polymarket has switched on instant Bitcoin Lightning deposits powered by Spark, crediting funds in under a second with no confirmation wait. The integration is self-custodial and requires no Lightning node management from Polymarket.

4 min read
Close-up of a smartphone screen displaying a financial transaction confirmation over a dark background with abstract circuit patterns, no text or logos visible
Share

Spark's zero-conf infrastructure collapses the on-ramp wait from up to an hour to under a second, and keeps the user in control of their keys.

Key takeaways

  • Polymarket now accepts Bitcoin deposits via the Lightning Network, powered by Spark, with funds credited in under a second using zero-conf validation.
  • The integration is self-custodial: each deposit wallet ties to the user's own keys, and Polymarket runs no Lightning nodes. Spark's single SDK handles on-chain, Lightning, and stablecoin rails.
  • Spark is not fully trustless on day one. Spark Operators co-sign transfers, though unilateral exit to Bitcoin L1 is always available, making it a meaningful upgrade over custodial on-ramps rather than a replacement for pure Lightning.

Polymarket, the crypto-native prediction market, has enabled instant Bitcoin deposits over the Lightning Network using infrastructure from Spark, per a post by @spark on X and Spark's own instant deposits documentation. The move cuts the on-ramp from a 10-to-60-minute confirmation window down to sub-second settlement, and it does it without requiring users to surrender custody.

Polymarket added standard on-chain Bitcoin deposits in October 2025. Those deposits required three to six confirmations before the platform credited an account, carried a higher minimum due to bridging costs, and set a $9 BTC floor per Polymarket's own deposit documentation. For a trader looking to enter a live market, both the delay and the cost are friction. Lightning via Spark eliminates both.

How Spark's Zero-Conf Rails Work

Spark validates a Bitcoin transaction at broadcast time, checking for double-spend risk, fee adequacy, and replace-by-fee flags before crediting the deposit. The protocol absorbs the confirmation risk rather than passing the wait to the user. Polymarket does not manage Lightning nodes or confirmation thresholds. A single Spark SDK handles on-chain, Lightning, and stablecoin rails, and each deposit wallet is tied to the user's own keys, not Polymarket's.

Spark runs on statechain-based architecture with Lightning interoperability. No channels, no liquidity management, no node required on the user side. Wallet providers including Breez, Xverse, and Cake are already building on the same rails. Spark's beta mainnet went live in April 2025.

One caveat Bitcoiners will want flagged: Spark is not equivalent to a pure Lightning channel on the trust model. Spark Operators co-sign transfers. The risk is time-bound and dissipates after the transaction settles, and unilateral exit to L1 is always available, but that co-signing assumption is a real difference from native Lightning. The Lightning and Ark scaling discussion is worth reading alongside this for context on where these trust tradeoffs sit in Bitcoin's broader second-layer stack.

The On-Ramp Problem Just Got Smaller

The single biggest UX friction keeping Bitcoin holders out of Lightning-native apps has been the on-ramp itself: a custodial exchange, a KYC step, a wait, and a bridge. Spark plus Lightning collapses that to a sub-second self-custodial deposit straight from a hardware or mobile wallet. A Bitcoiner holding keys can now move from cold storage to an active position on a high-volume prediction market in one step.

That has direct competitive consequences. Polymarket, founded in 2020, reached prominence during the 2024 U.S. presidential election when its markets exceeded $3.3 billion in wagered volume. It competes directly with regulated rival Kalshi, which operates on custodial fiat rails requiring ACH or wire. Polymarket now has a Bitcoin-native, self-custodial, instant on-ramp that Kalshi cannot match on those terms. The race to capture Bitcoin-native trading flow just got a new data point.

There is a second layer of significance here. Polymarket has operated in a grey legal zone, including a DOJ investigation and an FBI raid on CEO Shayne Coplan over allegations involving U.S. user access. A Lightning on-ramp that is harder to block and operates without custodial KYC at the deposit layer is not just a UX feature. It is a censorship-resistance move.

The falsifiable claim in all of this: if Spark and Lightning can handle Polymarket's deposit volume over the next 90 days without notable zero-conf failures, double-spend incidents, or a quiet raise of the Lightning minimum deposit, the "Bitcoin payments aren't ready for real apps" objection is functionally dead. If Spark Operator co-signing surfaces as a real-world attack vector, or deposit failures accumulate, the thesis collapses.

What to Watch

The 90-day operational track record matters more than the announcement. Watch for any change to the Lightning deposit minimum, any reported zero-conf failures at scale, and whether other prediction markets or financial applications move to integrate Spark's SDK on the same rails. Lightspark has described Spark's mission as making Bitcoin the standard open protocol for money on the internet. Polymarket is the first high-profile test of that claim against real trading volume.

Sources

Frequently Asked Questions

Deposits are self-custodial: each wallet ties to the user's own keys, not Polymarket's. However, Spark Operators co-sign transactions during settlement. The co-signing risk is time-bound and dissipates after the transaction completes, and unilateral exit to Bitcoin L1 is always available. It is a stronger trust model than a custodial on-ramp, but not equivalent to a direct Lightning channel.

Spark is built on statechain technology. There are no channels to open, no inbound liquidity to source, and no node to run. It interoperates with Lightning natively and accepts Lightning payments, but the underlying mechanism is statechains, not payment channels. The tradeoff is the Spark Operator co-signing assumption that pure Lightning channels do not carry.

The previous on-chain Bitcoin minimum was $9, driven by bridging costs. A Lightning-specific minimum for Spark deposits has not been confirmed in available documentation. Spark-to-Spark transfers are fee-free; users pay standard network fees on deposit and withdrawal. Check Polymarket's deposit documentation for the current figure before transacting.

News and analysis, not financial, investment, legal, or tax advice. Figures and quotes are verified against primary sources where possible. See our editorial and financial disclosures.

Keep reading

All of TFTC

The Bitcoin Brief

Bitcoin, markets, energy, and the tech reshaping all three.

A daily brief on the freedom tech building a parallel economy, written for the curious and the convicted alike. Signal, not noise. Truth for the Commoner.

Free, daily. Unsubscribe anytime.