Wallet Dust Sweeping Destroys Runes Tokens

introduction

UTXO MANAGEMENT FAILURE MODE

The Conflict Between Wallet Hygiene and Runes Asset Integrity

How automated wallet functions designed to consolidate dust UTXOs can inadvertently destroy Runes token balances, creating a direct conflict between standard Bitcoin wallet hygiene and the asset management requirements of the Runes protocol.

The Runes protocol binds fungible token balances to Bitcoin UTXOs, making every unspent output a potential container for digital assets. This design creates a fundamental operational conflict with a common Bitcoin wallet feature: the automated consolidation or sweeping of small-value UTXOs, often called dust management. When a wallet sweeps a UTXO that holds a Runes balance—treating it as negligible bitcoin dust—the Runes tokens are permanently destroyed as the UTXO is consumed in a transaction that does not preserve the Runes data in a new output. This is not a protocol bug but an integration failure where wallet logic designed for bitcoin accounting is unaware of the meta-protocol state layered on top.

The risk is amplified by the fact that Runes balances can exist on UTXOs with zero or near-zero bitcoin value. A UTXO containing 1,000 units of a Runes token might be worth significant market value while holding only 546 satoshis—the dust limit in many wallet implementations. Standard wallet hygiene features, including automatic coin selection algorithms that prioritize small UTXOs as fee inputs, can select these Runes-bearing outputs for spending without any warning to the user. The loss is often discovered only when the user attempts to transfer the tokens and finds the balance missing. This failure mode has been observed across multiple wallet implementations and exchange hot wallets, where automated UTXO consolidation scripts have inadvertently destroyed user or customer Runes holdings.

Wallet developers, exchange operators, and custody providers must implement Runes-aware UTXO management to prevent this class of incident. This requires coin selection algorithms that query an Ordinals and Runes indexer before selecting any UTXO as a transaction input, flagging outputs that contain inscriptions or Runes balances for exclusion from automated sweeping. For exchanges operating hot wallets at scale, the operational challenge is significant: consolidation logic that was previously a simple bitcoin-value threshold must now incorporate an external state lookup, introducing latency and a dependency on indexer availability. Teams should conduct a UTXO management review to identify all automated spending paths—including fee bumping, consolidation, and dust sweeping—and verify that each path preserves Runes-bearing outputs. Chainscore Labs can assist with integration architecture review and indexer dependency analysis to prevent asset loss from this operational mismatch.

WALLET DUST LIMIT MISMANAGEMENT AND RUNES TOKEN SWEEPING

Incident Snapshot

Operational impact matrix for wallet teams, exchanges, and custody providers evaluating the risk of automated UTXO consolidation logic destroying Runes token balances.

Area	What changes	Who is affected	Action
UTXO Selection Logic	Standard wallet dust-sweeping algorithms treat small-value UTXOs as uneconomical and consolidate them into a single output, ignoring Runes token data attached to the satoshis.	Wallet developers, exchange hot wallet operators, custody providers	Audit coin-selection algorithms to identify and exclude UTXOs carrying Runes tokens from automated consolidation flows.
Fee Estimation	Automated fee-bumping or CPFP logic may select a Runes-bearing UTXO as an additional input to cover a fee shortfall, burning the token in the process.	Wallet infrastructure teams, Lightning Network node operators	Implement UTXO tagging to mark Runes-carrying outputs as ineligible for automatic fee-payment selection.
Balance Display	Users and operators see a small BTC dust balance but no indication that the UTXO contains a Runes token, leading to unintentional spending.	End users, exchange operations teams, treasury managers	Integrate Runes-aware balance indexing to surface token holdings alongside BTC balances and warn before spending.
Batch Payouts	Exchange or custodian batch-sweep transactions consolidate many small deposits, inadvertently including Runes deposits from users.	Exchange wallet engineers, OTC desks, payment processors	Isolate incoming UTXOs with Runes data before they enter the main hot-wallet sweep path.
Recovery Procedures	Once a Runes UTXO is spent as a fee or consolidated, the token is permanently destroyed with no on-chain recovery mechanism.	Incident response teams, custody operations	Develop a pre-spend validation checkpoint that requires explicit human approval for any UTXO flagged as carrying a non-BTC asset.
Indexer Dependency	Detection of Runes-bearing UTXOs depends on accurate and timely indexer data; a lagging or divergent indexer can cause false negatives.	Infrastructure teams, indexer operators	Cross-reference at least two independent indexer implementations before classifying a UTXO as safe to sweep.
Multi-Sig and MPC	Co-signing devices or MPC nodes may not parse Runes data, approving a sweep transaction that destroys tokens without any signer awareness.	Institutional custody providers, multi-sig wallet teams	Ensure all signing participants in a quorum can decode and display Runes token metadata before signing consolidation transactions.
Protocol Migration	Future Runes protocol upgrades or indexer changes could alter how tokens are attached to UTXOs, invalidating existing exclusion lists.	Protocol integration teams, wallet SDK maintainers	Monitor Runes standards and indexer release notes for changes to UTXO binding semantics and update exclusion logic accordingly.

technical-context

UTXO-BOUND ASSETS AND WALLET HYGIENE CONFLICTS

How Runes Tokens Are Stored and How Sweeping Destroys Them

Runes tokens exist as data on Bitcoin UTXOs, making them vulnerable to automated wallet functions that consolidate small-value outputs.

Runes tokens are not stored in a separate smart contract or account balance. They are encoded as data within Bitcoin UTXOs using the OP_RETURN output and witness data conventions defined by the Runes protocol. A user's Runes balance is the sum of token amounts held across a set of UTXOs controlled by their wallet. This design means that any operation that spends a UTXO—whether for a payment, a consolidation, or a fee—also destroys the Runes tokens it carries, unless the transaction is explicitly constructed to preserve and transfer them to a new output.

The conflict arises from standard Bitcoin wallet hygiene. Many wallets implement a 'dust sweeping' or UTXO consolidation feature that automatically gathers small-value UTXOs into a single larger output to simplify future spending and reduce fee overhead. When a wallet is not Runes-aware, it treats a UTXO holding a valuable Runes token as just another dust-sized Bitcoin output. The sweep transaction spends the UTXO, paying its minuscule Bitcoin value to fees or a consolidation address, and the Runes tokens are permanently destroyed because the transaction does not include the necessary Runes transfer instructions. This is not a protocol bug; it is an operational mismatch between Bitcoin's UTXO management model and the asset-bearing properties of those UTXOs.

Exchange operators, custody providers, and wallet teams must review their UTXO selection and consolidation logic to prevent accidental Runes destruction. A Runes-aware coin selection algorithm must identify UTXOs that carry Runes balances and exclude them from automated sweeping, or ensure that any consolidation transaction correctly re-encodes the Runes transfer. Chainscore Labs can conduct a UTXO management review for wallet and custody implementations, verifying that coin selection, fee bumping, and consolidation flows are safe for Runes-bearing UTXOs.

IMPACT ANALYSIS

Affected Systems and Stakeholders

Wallet Developers

This is the primary affected group. Standard Bitcoin wallet hygiene—specifically dust consolidation and UTXO sweeping—is directly incompatible with Runes asset management.

Immediate actions:

Audit coin selection algorithms to identify and exclude UTXOs containing Runes tokens from automated sweep transactions.
Implement Runes-aware UTXO management that treats token-bearing outputs as non-dust regardless of their BTC value.
Add user-facing warnings when a proposed transaction would spend a Runes-bearing UTXO.
Review the handling of change outputs to ensure Runes tokens are not accidentally burned when creating change addresses.

Long-term considerations:

Integrate with Runes indexer APIs to maintain an accurate, real-time view of which UTXOs carry token balances.
Design explicit Runes transfer flows separate from BTC spending flows to prevent accidental commingling.

Chainscore Labs can conduct a UTXO management review of your wallet's coin selection and consolidation logic to prevent Runes token loss.

implementation-impact

UTXO MANAGEMENT AND TOKEN PRESERVATION

Operational Impact and Required Changes

The conflict between standard Bitcoin wallet hygiene and Runes asset management requires immediate operational changes. Wallet teams and exchange operators must review and redesign their UTXO consolidation logic to prevent the permanent destruction of Runes tokens during automated dust-sweeping operations.

Redesign Coin Selection Logic

Standard Bitcoin wallets use dust limits to identify and consolidate small-value UTXOs, but this logic is blind to Runes token balances. A UTXO with a 546 satoshi dust value could hold a Runes token worth significantly more. Wallet teams must implement Runes-aware coin selection that queries an indexer or parses OP_RETURN data to identify token-bearing UTXOs before any automated sweep, consolidation, or fee-selection process executes. Failure to do so will result in permanent, irreversible token loss for users.

Implement Pre-Sweep Indexer Verification

Before any automated transaction that selects UTXOs as inputs, the wallet backend must perform a real-time check against a Runes indexer to determine if the UTXO holds a token balance. This verification step should be a hard gate in the transaction construction pipeline. Exchange and custody teams should integrate this check into their hot-wallet sweep logic, withdrawal processing, and internal consolidation routines. Relying solely on satoshi value is insufficient and has already led to documented token destruction events.

Audit and Halt Automated Consolidation Scripts

Many exchanges and custodians run periodic scripts to consolidate dust UTXOs for operational efficiency. These scripts are the highest-risk vector for accidental Runes destruction. Operations teams must immediately audit all automated consolidation jobs, halt any that do not include Runes-aware checks, and implement a manual review step for UTXOs flagged by an indexer. A single unmodified cron job can destroy thousands of dollars in Runes tokens across multiple user accounts in one transaction.

Update Fee-Selection and CPFP Logic

Child-Pays-For-Parent (CPFP) fee bumping and automated fee-selection algorithms often pull from the smallest available UTXOs. If a Runes-bearing UTXO is selected as a fee input, the token is burned to miners. Wallet developers must extend fee-bumping and coin-selection algorithms to exclude UTXOs with active Runes balances. This requires integration with a Runes indexer at the point of UTXO selection, not just at the time of user-facing balance display.

Establish Operational Runbooks for Token Recovery

Once a Runes token is spent to a miner or consolidated into an unspendable output, recovery is cryptographically impossible. Operations teams need incident response runbooks that cover: immediate pausing of all automated sweep jobs upon detection of a loss event, forensic tracing of the affected UTXOs using an indexer, user communication protocols, and a post-incident review of the coin-selection code path that caused the loss. Proactive preparation is the only mitigation.

Conduct a Chainscore Labs UTXO Management Review

Chainscore Labs can perform a targeted review of your wallet or exchange infrastructure to identify coin-selection paths that risk Runes token destruction. Our assessment covers automated consolidation scripts, fee-selection logic, CPFP implementations, and withdrawal processing pipelines. We deliver a prioritized remediation plan and can assist with implementing Runes-aware UTXO management controls to prevent asset loss before it occurs.

WALLET DUST LIMIT MISMANAGEMENT AND RUNES TOKEN SWEEPING

Risk Assessment Matrix

Evaluates the operational risks and failure modes when automated wallet functions designed for Bitcoin hygiene interact with UTXOs carrying Runes token balances, leading to permanent asset loss.

Risk	Failure mode	Severity	Mitigation
Automated dust consolidation	Wallet logic identifies a Runes-bearing UTXO as 'dust' based on its BTC value alone and consolidates it with other small UTXOs, destroying the Runes token balance in the process.	Critical - Permanent loss	Implement Runes-aware UTXO selection that checks for token balances before classifying a UTXO as dust. Exclude token-carrying UTXOs from automated consolidation.
Fee bumping with Runes UTXOs	A wallet's dynamic fee management or Child-Pays-For-Parent (CPFP) logic selects a Runes UTXO as an additional input to boost a transaction's fee rate, inadvertently spending the token.	High - Permanent loss	Configure fee bumping algorithms to use a whitelist of safe UTXOs. Flag and require explicit user confirmation before spending any UTXO with a non-zero Runes balance.
Batch sweeping during key rotation	A custodial or exchange wallet performs a 'sweep all' operation to migrate funds to a new key set, treating all UTXOs as fungible BTC and destroying attached Runes balances.	Critical - Mass loss event	Integrate a pre-sweep inventory step that queries an indexer for Runes balances on all UTXOs. Segregate token-bearing UTXOs for manual or programmatic transfer before sweeping.
Privacy-focused coinjoin or mixing	A wallet's integrated coinjoin or mixing service includes a Runes UTXO in a collaborative transaction, either destroying the token or leaking its ownership to other participants.	High - Permanent loss or privacy leak	Automatically exclude any UTXO with a non-zero Runes balance from coinjoin rounds. Maintain a strict separation between privacy-enhancing BTC transactions and Runes asset management.
Lightning channel opens with Runes UTXOs	A Lightning node's autopilot or manual funding logic selects a Runes UTXO as a channel funding input, permanently burning the token in the 2-of-2 multisig output.	Critical - Permanent loss	Modify Lightning node funding logic to check for Runes balances via an indexer API before UTXO selection. Require manual override for any token-bearing UTXO used in channel opens.
Third-party wallet recovery services	A user imports a seed into a new wallet that does not recognize Runes and triggers a 'recovery sweep' that consolidates all UTXOs, destroying tokens.	High - Permanent loss	Wallet recovery flows should include a pre-sweep scan for all recognized meta-protocols. Display a clear warning listing any non-BTC assets that will be destroyed before proceeding.
UTXO defragmentation routines	A wallet periodically defragments UTXOs to reduce future transaction size, consolidating many small UTXOs including those with Runes, destroying the tokens.	Medium - Gradual loss	Disable automatic defragmentation for wallets that hold Runes. If defragmentation is required, implement a Runes-aware filter and require explicit user approval for each token-bearing UTXO.
Incomplete indexer synchronization	A wallet queries an indexer that is behind or has incomplete state, failing to detect a Runes balance on a UTXO and treating it as a safe-to-spend BTC-only output.	High - Conditional loss	Implement a confirmation threshold requiring multiple indexer sources or a minimum block depth before classifying a UTXO as safe. Alert users if indexer state is stale.

WALLET DUST LIMIT MISMANAGEMENT AND RUNES TOKEN SWEEPING

Remediation and Prevention Checklist

A structured checklist for wallet developers, exchange operators, and custody teams to audit their UTXO management logic and prevent the accidental destruction of Runes tokens during automated wallet hygiene operations.

What to check: Review all automated wallet functions that select UTXOs for consolidation, dust sweeping, or fee bumping. Identify any logic that selects inputs based solely on their BTC value without inspecting the UTXO for Runes data.

Why it matters: Standard Bitcoin wallet hygiene treats small-value UTXOs as uneconomical 'dust' and consolidates or sweeps them. If a UTXO contains Runes tokens, this operation permanently destroys the tokens by spending them as miner fees or consolidating them into a standard payment output.

What signal confirms readiness: The coin selection algorithm explicitly checks each candidate UTXO for Runes data (via an indexer API or local index) and excludes any UTXO holding a non-zero Runes balance from automated sweeping. Logging confirms that Runes-bearing UTXOs are skipped with a clear audit trail.

resource-links

CANONICAL SPECIFICATIONS AND OPERATOR REFERENCES

Source Resources and Further Reading

Use these resources to verify Runes allocation behavior, distinguish Bitcoin dust policy from asset ownership, and design safer sweeping and signing controls. Teams investigating a loss should reproduce the transaction with a pinned indexer version before concluding that Runes were burned or reassigned.

Runes Protocol Specification

The Ordinals Handbook defines how runestones, edicts, output assignments, cenotaphs, and burns are interpreted. Wallet and exchange teams should use these rules to model every Runes-bearing input before approving consolidation. Do not infer asset value from the UTXO's bitcoin amount: an output near a wallet's dust threshold may hold a material Runes balance. Test sweep construction against valid transfers, malformed runestones, omitted allocations, output-index changes, and transactions that spend several Runes-bearing inputs. Because Runes interpretation is performed above Bitcoin consensus, teams should also verify behavior against the indexer implementation and version used by their production systems.

EXPLORE

ord Reference Implementation and Release History

The ord repository is the primary implementation reference for Ordinals and Runes indexing behavior. Operators should pin the exact release used to classify UTXOs, retain its configuration and indexed block height, and regression-test upgrades before enabling automated sweeps. For incident analysis, replay the suspected transaction and compare input balances, decoded runestone instructions, assigned outputs, and any burn or cenotaph result. Wallet teams should monitor repository releases and issues for interpretation changes that could alter spendability checks. Avoid silently mixing results from different ord versions or third-party APIs; disagreement should place the affected UTXO into quarantine rather than trigger consolidation.

EXPLORE

Bitcoin Core Dust Policy Implementation

Bitcoin Core's policy code is essential for understanding why a wallet may label an output uneconomic or dust-like. Dust is a transaction-relay and fee-economics concept, not evidence that a UTXO is asset-free. Runes balances are not visible to Bitcoin Core's native coin-selection logic unless the surrounding wallet adds protocol-aware classification. Engineering teams should inspect the current policy implementation alongside the exact node release they operate, then separate relay eligibility from sweep eligibility. A safe controller should require both Bitcoin policy checks and an independent Runes or inscription inventory check before an input can enter automatic consolidation.

EXPLORE

PSBT Signing Boundaries

BIP 174 specifies the Partially Signed Bitcoin Transaction container, but standard PSBT fields do not make hardware signers or co-signers inherently aware of Runes semantics. Custody providers should treat Runes allocation validation as a pre-signing control: decode every input, preserve required output ordering, verify the runestone and edicts, and show the expected post-transaction asset allocation to approvers. Unknown or proprietary metadata must not substitute for independently deriving the transaction result. Add a policy that rejects PSBTs when the signer cannot reconcile asset-bearing inputs with intended destination outputs, especially during batch withdrawals, fee bumping, and automated UTXO consolidation.

EXPLORE

ord Wallet and UTXO Isolation Guidance

The Ordinals wallet guide provides operational context for using ord with a Bitcoin Core wallet and keeping protocol-managed outputs separate from ordinary payment funds. Teams should adapt this separation model for Runes custody: maintain explicit UTXO classifications, disable generic sweep jobs on protocol-managed wallets, and require a fresh indexer check immediately before transaction construction. Recovery and migration procedures must preserve the same controls; importing descriptors or keys into a conventional Bitcoin wallet can reintroduce unsafe coin selection. Validate backups, watch-only inventories, and transaction approval tooling in a staging environment containing small Runes balances before moving production assets.

EXPLORE

Chains We Build On

Looking to build on a specific blockchain?

We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.

Learn More

EVM ecosystems

Ethereum
Arbitrum
Optimism
Polygon
Avalanche
Cronos

Non-EVM ecosystems

Solana
Sui
Aptos
Hedera
Stellar
NEAR

Additional ecosystems

Polkadot
Cosmos
TON
Cardano
Algorand
Tempo

Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.

WALLET DUST LIMIT INCIDENT FAQ

Frequently Asked Questions

Operational questions for wallet teams, exchange operators, and asset managers dealing with the conflict between automated UTXO consolidation and Runes token preservation.

Many wallets implement automated 'dust sweeping' or UTXO consolidation routines that identify and spend small-value UTXOs to reduce future transaction costs. These routines typically evaluate UTXOs based solely on their bitcoin value, ignoring any Runes token balances they may carry. When a UTXO containing Runes is selected as an input for a consolidation transaction, the Runes tokens are transferred according to the Runes protocol rules—often to a change address that the wallet does not track as a Runes balance, or they are effectively burned if the transfer logic is not properly handled. The result is permanent token loss, as Runes balances are inseparable from the UTXOs that carry them.

Key failure points:

UTXO selection logic that filters solely on satoshi value thresholds
Lack of Runes-aware balance checks before constructing consolidation transactions
Change address handling that does not preserve Runes token metadata
Automated processes that run without user confirmation or token-aware warnings

Trusted by Industry Leaders

Delivering blockchain solutions for 5+ years.

We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.

Selected Partners & Clients

“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”

Lee Erswell

CEO, Telos Foundation

how to get started

How to get started?

If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.

Exploration & Strategy

Define your product goals and choose the right blockchain architecture for your use case.

Architecture & Design

Design the smart contracts, tokenomics, and security parameters of your system.

Development & Integration

Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.

Security & Launch

Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.

Learn More

Explore More Solutions

Discover our
blockchain development services.

We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.

Book a Call

DeFi Protocol Development

End-to-end development of custom DeFi protocols including core smart contracts and system architecture.

DEX & Exchange Development

Building high-performance decentralized exchanges with optimized liquidity and advanced trading logic.

Lending & Borrowing Platforms

Scalable credit markets and money protocols built for production-grade liquidity and security.

Wallet Dust Limit Mismanagement and Runes Token Sweeping

The Conflict Between Wallet Hygiene and Runes Asset Integrity

Incident Snapshot

How Runes Tokens Are Stored and How Sweeping Destroys Them

Affected Systems and Stakeholders

Wallet Developers