> ## Content Index
> Fetch the complete content index at: https://blog.dhorse.fun/llms.txt
> Use this file to discover other available public pages before exploring further.

# Sending BTC, Burning Assets? DarkHorse Wallet Adds UTXO Protection
- URL: https://blog.dhorse.fun/utxo/
- Published: 2026-11-09T15:57:27.000Z
- Updated: 2026-11-09T15:57:27.000Z
- Author: Julian Weber
- Tags: Wallet

Have you ever sent BTC and unintentionally transferred or even burned other Bitcoin-based assets in your wallet?

The risk may lie in the UTXOs your wallet automatically selects.

A UTXO contains BTC, but it may also be associated with RGB assets, inscriptions, Runes, or Alkanes. If a wallet selects transaction inputs based only on their BTC value without correctly handling the associated assets, an ordinary payment can result in asset loss.

**Keeping asset-bearing UTXOs out of ordinary BTC payments is a problem wallets need to address.**

DarkHorse Wallet has implemented three safeguards: RGB asset isolation, indexer-based detection and wallet-level freezing of imported asset UTXOs, and checks before relevant operations.

Together, these safeguards help the wallet distinguish between different uses of UTXOs and reduce the risk of accidental spending and asset burning.

## 1\. What Is a UTXO, and Why Does It Matter?

UTXO stands for *Unspent Transaction Output*. Think of it as an unspent receipt of BTC, specifying an amount and the conditions required to spend it.

Your wallet displays a BTC balance, but underneath, it manages individual UTXOs.

When you send BTC, the wallet selects one or more UTXOs as transaction inputs. Each selected output is consumed in full. The transaction creates new outputs, typically a payment to the recipient and change returned to you. The difference between the total input and output values becomes the transaction fee. The [Bitcoin Developer Guide](https://developer.bitcoin.org/devguide/transactions.html?ref=blog.dhorse.fun) explains this structure.

For wallets managing other assets, however, BTC value alone is not enough to guide input selection.

A UTXO containing a small amount of BTC may also be associated with assets the user wants to keep. Different protocols handle these associations differently, but the wallet must consider the same question: what happens to those assets if this output is spent?

**A small BTC amount does not mean a UTXO is safe to use for an ordinary payment.**

![](https://storage.ghost.io/c/ee/a0/eea02910-e480-431e-a20b-1cfe38a58752/content/images/2026/11/image-10.png)

## 2\. How Can an Ordinary Transfer Cause Asset Loss?

Spending a UTXO is not inherently dangerous. A legitimate asset transfer may require spending the associated UTXO.

The risk arises when a wallet uses an asset-bearing UTXO for an ordinary BTC payment without following the asset protocol’s transfer rules.

The consequences vary by protocol. An asset may be transferred unintentionally or become unusable. Spending a UTXO does not automatically mean the associated asset is burned.

For RGB, ownership of an asset state is associated with a Bitcoin UTXO. A valid transfer requires the corresponding RGB state transition, not merely a valid Bitcoin transaction. The [RGB team’s ownership explanation](https://rgb.info/rgb-ownership/?ref=blog.dhorse.fun) describes this relationship.

**A successful Bitcoin transaction does not automatically mean the associated assets were handled correctly.**

The wallet needs to account for this distinction when constructing transactions.

## 3\. Safeguard One: RGB Asset Isolation

DarkHorse Wallet manages RGB asset UTXOs separately from the UTXOs used for ordinary BTC payments, using separate addresses.

When sending BTC, the wallet selects inputs only from the ordinary BTC area. The RGB asset area is excluded.

This protection also covers UTXOs reserved for future RGB asset allocations. Even before assets are assigned to them, they are excluded from ordinary BTC payments.

If the available ordinary BTC funds are insufficient, the wallet does not draw from the asset area to complete the payment.

**Protection begins during coin selection: the RGB asset area is excluded from ordinary BTC payments.**

Users do not need to manually lock these UTXOs before every payment. Intentional RGB transfers are handled through the corresponding asset-transfer flow.

## 4\. Safeguard Two: Detecting and Freezing Imported Asset UTXOs

When importing a wallet, the original addresses may already hold inscriptions, including BRC-20, as well as Runes or Alkanes.

Their associated UTXOs also require protection.

DarkHorse Wallet uses indexers to identify these assets and freezes the detected UTXOs within the wallet, preventing them from being automatically selected as ordinary BTC.

Here, “freezing” means a wallet-level spending restriction. It does not freeze assets on-chain or change their ownership.

When users select the “UniSat or other Bitcoin wallet” import source, DarkHorse Wallet uses a new address for its ordinary BTC payments while leaving assets at the original address. The original address continues to be used for login.

**RGB assets are protected through isolation. Imported inscriptions, BRC-20, Runes, and Alkanes are protected through indexer-based detection and wallet-level freezing.**

The wallet applies different safeguards according to how the assets are managed.

## 5\. Safeguard Three: Checking UTXOs Before Use

Protection needs to extend beyond the “Send BTC” screen.

Creating an RGB receive invoice and topping up fees can also involve selecting or using UTXOs. Without corresponding checks, these operations could use outputs that should remain protected.

DarkHorse Wallet checks relevant UTXOs before asset sends and applies protection across three operations:

- **Sending BTC:** keeping protected asset UTXOs out of ordinary payments.
- **Creating RGB receive invoices:** checking the relevant outputs to avoid using protected UTXOs incorrectly.
- **Fee top-ups:** checking the UTXOs involved to reduce the risk of accidentally spending associated assets.

Creating an invoice does not necessarily spend a UTXO immediately. It can still involve selecting or assigning an output for use, which requires appropriate checks.

**Authorizing one operation does not mean authorizing the unintended use of other assets associated with its inputs.**

![](https://storage.ghost.io/c/ee/a0/eea02910-e480-431e-a20b-1cfe38a58752/content/images/2026/11/image-11.png)

## 6\. Website Payment Requests Are Checked Before Signing

For website-initiated payments, the wallet also needs to verify that the transaction matches the request presented to the user.

DarkHorse Wallet does not expose an arbitrary transaction-signing interface to websites. For payment requests, it displays the full recipient address and total amount, then independently checks before signing:

- Whether the payment goes only to the specified recipient.
- Whether the amount matches the confirmed request.
- Whether any asset UTXOs are being used.

Neither websites nor users are given an input-selection interface that would bypass the wallet’s UTXO selection rules.

Asset protection extends from input selection during transaction construction to the final checks before signing.

![](https://storage.ghost.io/c/ee/a0/eea02910-e480-431e-a20b-1cfe38a58752/content/images/2026/11/image-12.png)

## 7\. Making UTXO Protection Part of the Wallet

Leaving all these decisions to users would mean asking them to identify assets, inspect UTXOs, and manually select transaction inputs before every operation.

As assets are received and sent, the UTXO set changes. Even technically experienced users can miss something.

DarkHorse Wallet incorporates these safeguards into its everyday workflows:

**Isolate RGB assets. Detect and freeze imported asset UTXOs. Check relevant outputs before use.**

These mechanisms reduce reliance on users remembering which outputs need protection.

Their scope also matters. Indexer-based detection depends on indexer coverage and synchronization. Wallet-level restrictions cannot control transactions created by other software. If a user imports their keys into another wallet, protection depends on that wallet’s implementation.

UTXOs are fundamental to Bitcoin transactions. For a wallet managing multiple assets, understanding the purpose of each output and protecting its associated assets should be fundamental too.

**DarkHorse Wallet turns “don’t spend asset UTXOs as ordinary BTC” into rules the wallet actually enforces.**