UTXOs
Unspent Transaction Outputs
Only Operators can manage UTXOs on Ledger Vault
What are Unspent Transaction Outputs (UTXOs) ?
In Bitcoin and similar blockchains, every transaction consists of inputs and outputs:
An output is the amount of Bitcoin sent to a recipient.
An input is a portion of Bitcoin from your wallet used to fund the transaction — any leftover amount (the "change") is returned to your wallet as a new output, which can be used in future transactions.
Example: If you want to send $8 but only have a $10 bill, you pay with the $10 and receive $2 back as change. Bitcoin transactions work the same way.
UTXOs (Unspent Transaction Outputs) are the individual pieces of Bitcoin that remain unspent in your wallet — essentially, they are your "available change." When added together, they represent your total wallet balance.
UTXO selection strategy for transactions
When creating a Bitcoin transaction, you can choose from different strategies to determine which UTXOs (Unspent Transaction Outputs) to use:
Optimize for Size (Default Strategy): Selects the largest available UTXOs first. This reduces the number of inputs in the transaction, helping to minimize transaction size and, therefore, fees.
Merge Small Outputs: Prioritizes using smaller UTXOs. This strategy helps consolidate many small pieces of Bitcoin into fewer, larger ones, which can reduce wallet fragmentation over time.
Prioritize Deep Outputs: Selects UTXOs that have been confirmed the longest (i.e., have the most confirmations). This can improve transaction reliability and security by using more established funds.
UTXO consolidation
Why Consolidate UTXOs?
UTXO consolidation is the process of reducing the number of small-value unspent outputs in your wallet by sending them to yourself in a single transaction.
By combining multiple small UTXOs into one larger UTXO — similar to exchanging many coins for a single bill — you make your wallet more efficient. This makes it easier to send larger payments in the future and can help lower transaction fees, especially if you consolidate when network fees are low.
Example: If you consolidate 100 UTXOs, each worth 0.01 BTC, you'll end up with one UTXO worth 1 BTC.
Before you start
Only Operators who have the Creator role in the Account can consolidate UTXOs.
Best practices
Consolidate UTXOs only when the account has no pending or incoming transactions.
Approve UTXO consolidation requests immediately after creation.
Create and approve one UTXO consolidation request at a time — avoid creating multiple requests simultaneously.
The consolidation is always performed on the index 0 address of the account, that is the first-ever generated address in your account.
If the selected account uses whitelists only, ensure that address index 0 is either included in an existing whitelist or covered by a dedicated rule. Contact an Administrator to configure this, as it is required to perform UTXO consolidation in the account.
You can consolidate up to 100 UTXOs at a time by creating a transaction to yourself. The smallest UTXOs are selected, but those below 546 satoshis are ignored. If the account holds more than 100 UTXOs, repeat the process as needed.
Consolidation request
Click Accounts on the left panel.
Click the name of the account for which you want to consolidate UTXOs.
Click the UTXOs tab at the top of the page.
Click Consolidate in the top right.
Click Verify on device in the modal.
On your device, verify the information and tap Confirm .
In the transaction dialog, the number of Consolidated UTXOs and the corresponding total Amount are displayed. Note: In rare cases, if the transaction fees are higher than the consolidated amount, you'll need to enter a lower number of UTXOs to allow the transaction to be created.
(optional) Click Add comments and enter a Label and Comments .
Click Create transaction.
On your personal security device, verify the information and tap Confirm .
Approval
Depending on the approval workflow defined for the account, the request might need to be approved by other Operators.
The request must be processed before the 7-day expiry date. If the request expires a new one must be created.
Last updated