Skip to main content
Arkade enforces the spending conditions your application sets on Bitcoin outputs. Your application connects to the Arkade operator through the TypeScript SDK, and uses it to build payments, assets, contracts, swaps, and price feeds. Every Arkade transaction is a Bitcoin transaction, and Arkade works on Bitcoin today without any consensus changes.

Wallets

Send and receive bitcoin and assets from a self-custodial wallet.

Assets

Issue assets on Bitcoin, set their metadata, and control their supply.

Vaults

Hold funds in contracts that release them only under your rules.

Intents

Pay over Lightning and exchange assets at a quoted price.

Oracles

Give your contracts signed prices to settle against.

How Arkade Works

Arkade uses Bitcoin’s own transactions, outputs, scripts, and confirmations, so it adds no chain, native token, federation, or consensus system. Every Arkade output is a Bitcoin output with spending paths, and the Arkade operator cosigns a spend only when it satisfies the path it uses. If that path is written in Arkade Script, the operator runs the script first. Should the operator ever be unavailable, the owner can still spend through the exit path that every output keeps. For speed and a lower cost per transaction, applications can also execute transactions offchain. A transaction then executes as soon as the operator cosigns it, and its virtual outputs settle on Bitcoin later, in batches. How Applications Use Arkade explains what this means for the application you build.

Where to Start