Offchain Execution
Transactions & Execution
Every Arkade transaction is a Bitcoin transaction that the operator checks before it cosigns.
Every Arkade transaction is a Bitcoin transaction that spends outputs whose spending paths the operator enforces. Before it cosigns, the operator checks the transaction against each path it spends and runs the Arkade Script of any path written in it. At the base, the transaction spends ordinary Taproot outputs, and Bitcoin confirms it like any other.
With offchain execution, the transaction spends virtual outputs instead. It is a virtual transaction: complete and signed, but never broadcast. It executes as soon as the operator cosigns it, and a batch later settles its outputs on Bitcoin. The rest of this page covers virtual transactions.
The SDK builds one checkpoint transaction, because Alice spends one virtual output, and one virtual transaction:
Bob’s output uses the standard script of his address: a collaborative path for Bob and the operator, and an exit path that Bob can use alone after the operator’s exit delay. Alice’s change gets the same script with her key, and either output can be spent again as soon as the operator cosigns.