For the complete documentation index, see llms.txt. This page is also available as Markdown.

Unlock Bitcoin

Request and follow an owner-signed Bitcoin unlock from reservation through completion.

Only the account owner can request an unlock. A trading agent cannot perform this action.

Funds return only to the same full bc1q Sidepit ID that owns the account. There is no destination field to enter or change.

Submit an unlock

  1. Connect the owner Sidepit ID at app.sidepit.com.

  2. Under Sidepit Account, choose Unlock funds.

  3. Enter a positive whole number of sats or choose MAX.

  4. Confirm the complete connected Sidepit ID and amount.

  5. Sign inside UniSat.

Placeholder for the production Unlock funds dialog and lifecycle history
Screenshot slot: show explicit/MAX controls, the full Sidepit ID, lifecycle statuses, and a complete Bitcoin transaction ID.

The server validates available margin and duplicate requests. Open positions and working orders can reduce the amount available to unlock. Cancel unwanted orders and reduce exposure deliberately before requesting a larger amount.

Lifecycle

Status
Meaning
What to do

PENDING

The signed request was received. It has not yet passed the engine's account and margin rules.

Wait for the same operation ID to advance or reject.

RESERVED

The amount passed validation and has been reserved from the account's available balance and margin exactly once.

This is irrevocable. There is no cancel-unlock operation. Do not resubmit.

PROCESSING

The custodian payout is in progress and the lifecycle record carries the Bitcoin transaction ID when available.

Inspect the complete transaction ID shown by the web app. Do not infer timing.

COMPLETED

The on-chain outflow has been folded into account state and the reservation has been retired or reconciled.

Confirm the wallet receipt and final account state.

REJECTED

The request did not pass signature, identity, duplicate, or margin checks.

Read the named reject reason before making a new request.

These display states and their operation IDs survive exchange restart. The public protocol exposes them through AccountOperations.unlock_records, with reserved value also reflected in AccountMarginState.pending_unlock.

Sidepit does not promise a completion time. Refresh the same history row and never create a duplicate because a status has not changed yet.

If the owner wallet is unavailable

Restore the seed privately in a compatible wallet and verify that it produces the exact same full Sidepit ID. Then reconnect and sign from that address.

If no valid account key or recovery seed remains, there is no documented alternate signing path. Support should receive only public account, operation, and Bitcoin transaction IDs—never seed words, WIFs, or private keys.

Last updated

Was this helpful?