Build on Top of Spark’s Emerging Ecosystem

Explore how Dynamic enables developers and end-users to make the most out of Spark’s lightning-fast network.

  • Seamlessly onboard new users in seconds

  • Benefit from the security of the Bitcoin network

  • Build apps centered around stablecoin use cases

What is Spark

A payments-focused, high-performance Bitcoin Layer 2

Open-sourced and secured by Bitcoin, Spark is designed to overcome the remaining challenges of Bitcoin and Lightning by scaling self-custody wallets and enabling stablecoins on the Bitcoin network. Purpose-built for payments, Spark empowers developers to build innovative applications on Bitcoin that are natively compatible with Lightning.

Metrics

Spark is worth keeping an eye on…

0

Gas fees on transactions

<1 second

Time to transact

$175M

Funding raised by Lightspark

Use cases

What’s being built on Spark?

A new wave of Bitcoin-powered financial and payment innovations.

Payment Apps

Spark allows end-users to move money faster, cheaper, and smarter.

Trading Apps

Spark is designed to support DeFi at scale with efficient execution, instant settlement, and affordable transactions.

Stablecoins

Spark lets you launch a stablecoin program natively on Bitcoin, the most distributed, widely used, and liquid network in the world.

Start Building on Spark today

Start for free
No items found.
Blog

The Evolution of SVM Chains (Solana Virtual Machine)

Your guide to the Solana Virtual Machine: what it is, why it matters, and innovative projects that are leveraging it.

Read Blog Article
Blog

Blending Innovation with Bear-Themed Culture

Dive into the Berachain ecosystem and how it is forming one of the most active and vibrant communities in crypto.

Read Blog Article

Key terms to know

Statechain

A protocol for transferring ownership of a Bitcoin UTXO off-chain using coordinated signatures, enabling instant, low-fee transfers while preserving L1 security.

Shared Signing Protocol

The Bitcoin-native mechanism Spark uses to delegate control of on-chain funds off-chain.

Spark Operator

A signer within Spark that helps authorize off-chain transfers and then forgets prior keys after a handoff.

Spark Service Provider

An optional service that streamlines deposits/withdrawals between L1, Lightning, and Spark (and may provide Lightning routing).

Leaves & Branches (Spark Tree)

Spark models ownership as a tree of transactions: leaves represent user-owned UTXOs; branches are intermediate nodes.

Timelocks

A security mechanism in Spark where each off-chain transfer sets a relative time delay before an exit transaction can be broadcast to Bitcoin L1.

FAQs

Is Spark live?

Yes, Spark’s beta mainnet is live and ready for developers to build on and transact. Core features like sending/receiving Bitcoin, supporting tokens, and Lightning interoperability are operational. It’s still highly experimental, so expect rapid iteration and breaking changes.

How is Spark different from other Bitcoin scaling solutions?

Spark is built on statechains and a shared signing protocol instead of bridges, rollups, or smart contracts. It’s designed for payments, not general computation, enabling trust-minimized, non-custodial transfers with instant settlement.

What are the fees for Bitcoin payments on Spark?

- A: L1 to Spark: Onchain fee

- Spark to Spark: Free (small flat fee coming soon)

- Spark to Lightning: 0.25% + routing fee

- Lightning to Spark: 0.15%

- Exit to L1: L1 broadcast fee × 2

- Unilateral Exit: Onchain fee

How is Spark different from the Lightning Network?

While both are Bitcoin-native and enable instant payments, Lightning uses payment channels without trusted parties, while Spark uses a shared signing protocol with operators that co-sign transfers. Spark supports direct asset custody, instant L1 exits, and scales differently, enabling massive parallelization.

Set up your BitcoinKit now!

The first and best Bitcoin wallet adapter.

Subscribe to our Newsletter

Stay up to date with our latest product updates & news.

You are registered!
Oops! Something went wrong while submitting the form.