Six steps for moving a DAO treasury into Bitcoin

A DAO moves treasury funds into native bitcoin by approving an allocation, converting the authorized assets, and sending the proceeds to a Bitcoin custody address under defined controls. The work spans governance, execution, custody and accounting; a vote that says only “buy BTC” leaves material decisions unresolved. The proposal should specify the asset amount or limit, the conversion route, who may execute it, and how the DAO will verify the final balance.

What should a DAO approve before buying bitcoin?

Approve the exposure and the transaction authority separately. The exposure defines the amount, source assets and treasury objective. The authority defines the accounts or contracts that may move funds, the permitted counterparties and the destination custody setup. Keep these terms specific enough that delegates or signers can reject a transaction that exceeds the mandate.

Step 1: Set the allocation. State the maximum amount to spend, the assets that may be used, and whether the amount is fixed or capped in a reference currency. Specify whether the resulting holding must be native bitcoin on the Bitcoin network. Wrapped bitcoin on another chain represents a claim managed by that chain’s contract and issuer; it is not a UTXO controlled on Bitcoin. The distinction changes custody, redemption and counterparty risk.

Step 2: Approve the execution path. Identify who can initiate the trade and transfer, which treasury wallet or governance executor will authorize it, and what approvals are required. If the DAO uses a timelock or multisig, the proposal should account for its actual execution flow. A governance vote may authorize an action without executing it automatically. Record the approved destination policy, including whether a custodian or a DAO-controlled wallet will hold the bitcoin.

A useful proposal also defines how the DAO will handle a partial fill, a failed trade or a transaction that exceeds the approved cost limit. Separate the conversion price from network and service fees where the route makes that possible. This gives signers and reviewers a concrete basis for checking execution against the vote.

How can a DAO convert treasury assets into bitcoin?

The conversion route depends on what the treasury already holds and where those assets can be traded. Step 3: Choose and document the route. A treasury that holds bitcoin needs only a custody transfer; one holding stablecoins or other crypto must convert them through an available market or swap mechanism. The route may involve an exchange account, a broker or an on-chain protocol, each with different settlement, liquidity and counterparty assumptions.

For a cross-chain swap, map each leg: the source network and token, the swap mechanism, the Bitcoin output address, and the point at which the recipient considers settlement complete. A swap does not make two blockchains share a transaction or consensus process. The route coordinates actions across networks, so a delayed, failed or refunded leg can leave the DAO with a different asset than intended. For teams assessing that route, this explainer on Thor Swap integration mechanics describes how the swap path works for integrators. The proposal should still set its own limits for price impact, fees and failed execution.

Compare routes by the actual tradeoffs: execution price, slippage, liquidity, custody exposure during settlement, operational access and the ability to verify each leg. A quoted rate is not necessarily the final rate. On-chain swaps can expose the trade to pool depth and transaction ordering; centralized services add account and withdrawal dependencies. The better route for most DAOs is the one the treasury can operate and independently reconcile within its approved limits, not the one with the fewest visible steps.

How should the DAO custody and verify the bitcoin?

Bitcoin uses the UTXO model: each spend consumes one or more unspent transaction outputs and creates new outputs, including any change returned to the sender. Step 4: Validate custody before funding. Create or confirm the receiving setup, identify who controls its signing keys, and check that the address format and network match the chosen route. For multisig custody, verify the descriptor or policy, signer threshold, backup process and recovery path. The DAO should retain enough information to recognize its wallet’s outputs without relying on a single operator.

Step 5: Test and execute. Confirm the destination through an independent channel, then use a small test transfer when the route and custody process permit it. Have reviewers check the address, amount, fee and transaction details before signing. Bitcoin transactions are generally irreversible after confirmation, and a valid signature does not establish that the recipient address was correct. For exchange withdrawals, distinguish the exchange’s withdrawal status from the Bitcoin transaction and its confirmations.

Step 6: Reconcile the result. Match the approved amount to the trade receipt, fees, withdrawal record and Bitcoin transaction outputs. Confirm that the expected UTXOs appear in the DAO’s custody wallet and satisfy the recipient’s settlement policy. Then update treasury records and report any difference, including residual source assets or a partial execution.

Keep the core checks in the execution record:

• The approved allocation, source assets and spending limit.
• The trade route, execution price and itemized fees.
• The Bitcoin destination and custody policy.
• The transaction identifier, received outputs and reconciliation result.

Moving a DAO treasury into bitcoin is complete only when governance authority, conversion records and control of the resulting UTXOs agree. The transaction may settle on-chain while the accounting or custody record remains incomplete; treat those as separate checks before reporting the allocation as held.