How You Use Offchain Execution
1
Connect
Your application connects to the Arkade operator through the SDK, much like it would connect to an RPC provider.
2
Board
Send bitcoin to your boarding address, and the next batch turns it into a virtual output. You can also receive virtual outputs directly from another Arkade user (Boarding & Offboarding).
3
Transact
Send transactions through the SDK, and they execute offchain as soon as the operator cosigns them, so you can chain them without waiting for blocks.
4
Settle
When you want Bitcoin finality, settle your outputs in a batch swap. Until then they stay preconfirmed, which means you can already spend them.
5
Offboard
To move funds back to a Bitcoin address, offboard in a batch. If the operator is unavailable, you can still claim your funds onchain alone, through unilateral exit.
The Operator
The Arkade operator is the server your application connects to: it cosigns Arkade transactions and coordinates the batches in which users settle onchain. Because it refuses to cosign a second spend of a virtual output, it blocks double spends. It cannot spend your virtual outputs without your signature, and before it signs a path written in Arkade Script, it runs that script, whether the output is virtual or onchain.How Users Hold Funds
With offchain execution, your balance is a set of virtual outputs, each a Bitcoin output that you own and spend on its own, much like bank notes in a wallet rather than an account balance. In the SDK, a virtual output is called aVtxo, as in getVtxos() and VtxoManager.
A virtual output is the output of a virtual transaction, a complete Bitcoin transaction that nobody has broadcast. Rather than each taking an onchain output, many users’ virtual outputs share one, the batch output, and a tree of virtual transactions splits it among them. Each virtual output then has two spending paths: a collaborative path that the operator cosigns, used by default, and an exit path that the owner can use alone after a delay.
Virtual Outputs & Ownership
Virtual output structure, batch outputs, the virtual transaction tree, and virtual output states.
Execution
Transactions execute offchain in a DAG, where independent transactions run in parallel, so a contract with complex spending conditions doesn’t hold up unrelated transactions. When the operator cosigns a transaction, it is preconfirmed and its outputs can be spent at once, which lets you chain many transactions without waiting for a Bitcoin block.Transactions & Execution
Transaction structure, preconfirmation, chaining, and the offchain transaction DAG.
Settlement
A preconfirmed output relies on the operator not to cosign a conflicting transaction, and settling it in a batch swap removes that reliance. In a batch swap, the operator puts many users’ outputs into one Bitcoin transaction, the commitment transaction. Once it confirms, Bitcoin consensus secures your virtual outputs. You choose when to settle: high-value transfers are worth settling often, while low-value, high-volume activity can usually stay preconfirmed for longer.Settlement & Finality
The commitment transaction, batch swaps, connector outputs, and forfeit transactions.
Lifecycle
Virtual outputs expire with their batch, which lets the operator reclaim the bitcoin it puts into each batch. The SDK renews them in a batch swap before that happens, and you can delegate renewal to a third party for when your app is offline, without giving up custody.Expiry & Renewal
Batch expiry, renewal, delegation, and liveness requirements.
Security
Every virtual output comes with presigned Bitcoin transactions that its owner can broadcast without the operator, and this is the self-custody guarantee. The operator signs from inside an AWS Nitro Enclave, where its cosigning keys and its script engine both run (Nitro Enclaves).Security & Trust Model
Unilateral exit, exit costs, the Arkade Signer, and risks.