Skip to main content
Advanced feature. Native ramps require onchain transactions, confirmation waits, and minimum amounts that account for Bitcoin fees.
Ramps connect confirmed Bitcoin outputs with Arkade transaction paths. The SDK exposes two main processes:
  1. Onboarding (Boarding) - Commit a confirmed Bitcoin output to a Batch Output and create an Arkade wallet position.
  2. Offboarding (Exiting) - Create a conventional Bitcoin output through collaborative withdrawal or an available unilateral path.

Onboarding (Boarding)

Boarding spends a confirmed Bitcoin output into the batch process and creates a wallet output rooted in a Bitcoin-confirmed Batch Output. The SDK represents that output as a Vtxo object.

Boarding Address

A boarding address is a 2-of-2 Taproot address that prevents the funding output from being double-spent during onboarding.

The Boarding Process

1

Generate a boarding address

Get a boarding address from your wallet:
2

Send Bitcoin onchain

Fund the address from a Bitcoin wallet and wait for confirmation.
This is your first onchain transaction. Standard network fees apply.
3

Initiate the boarding settlement

Once confirmed, settle the boarding UTXO to your Arkade wallet:
4

Arkade Server processes

The operator includes the output in a Commitment Transaction.
This is the second onchain transaction.
5

Receive the Arkade output

After confirmation, the SDK exposes the resulting output for cooperative transactions.
Boarding requires at least two onchain transactions plus confirmation waits.

Offboarding (Collaborative Exit)

Collaborative offboarding uses eligible Arkade outputs as inputs and creates a conventional Bitcoin output at the requested destination. This is the preferred native withdrawal path while the operator is available.

The Offboarding Process

1

Specify your destination

Set the Bitcoin address and amount:
2

Request the offboard

Request the output; the SDK selects eligible inputs:
3

Server processes

The operator includes the request in a Commitment Transaction.
4

Receive onchain Bitcoin

Wait for the destination output to confirm.
Collaborative withdrawal batches multiple requests into one transaction, which generally reduces confirmation steps and per-user Bitcoin fees while the operator is available.

Unilateral Exit

An eligible output can provide a unilateral Bitcoin path that does not require operator cooperation after its script conditions are met. This workflow can be substantially more expensive and complex than collaborative withdrawal.
Consider unilateral recovery when:
  • The operator is permanently unavailable
  • You cannot reach the server for collaborative exit
  • The selected output exposes a valid unilateral path
Verify the output state before starting. Recoverable, expired, swept, and sub-dust positions can require a cooperative batch process. An available unilateral path can require multiple sequential Bitcoin transactions and substantial fees.

The Unilateral Exit Process

1

Create and fund an onchain wallet

Unilateral exit requires unrolling virtual transactions onchain. Each transaction needs miner fees paid via P2A outputs.
Send Bitcoin to this address to cover transaction fees for the unroll process.
2

Publish the transaction path

Unrolling publishes the applicable presigned Bitcoin transactions in sequence, with confirmation waits between the required steps.
3

Wait for CSV locktime

After unrolling, wait for the CHECKSEQUENCEVERIFY (CSV) relative timelock before spending the final output.
4

Complete the exit

Once the locktime is reached, claim your Bitcoin:
See Unilateral Exit for path requirements, timelocks, fees, and recovery qualifications.
Related: VTXO management, Lightning payments, and settlement.