A scan of Bitcoin’s UTXO set has identified roughly 96,000 outputs that appear to carry fake or non-spendable addresses, a finding that speaks to how arbitrary data is being embedded in Bitcoin rather than to any flaw in the network itself.
A scan of Bitcoin’s UTXO set has identified roughly 96,000 outputs that appear to carry fake or non-spendable addresses, a finding that speaks to how arbitrary data is being embedded in Bitcoin rather than to any flaw in the network itself.
The count comes from an investigation into data embeddings on Bitcoin, which examined outputs that look like ordinary payment destinations but were never intended to be spent. According to the analysis of embeddings in Bitcoin, these entries sit inside the unspent transaction output set, the running ledger of coins the network considers spendable. For related coverage, see Best Bitcoin Hardware Wallets in 2026.
The UTXO set is the collection of every unspent output across Bitcoin’s history. Full nodes keep it in memory to validate new transactions quickly, so anything recorded there, spendable or not, consumes resources. A “fake-address output” in this context is an output whose address field encodes data instead of pointing to a real key a wallet could later use to spend the coins. For related coverage, see Best Bitcoin Lightning Wallet for Merchants.
WHAT TO KNOW
- A scan attributes about 96,000 outputs in the UTXO set to fake or non-spendable addresses used to embed data.
- The finding concerns data quality and UTXO bloat, not a break in Bitcoin’s consensus rules or security.
Why fake-address outputs matter for Bitcoin analysis
Because the UTXO set is foundational to transaction accounting, outputs recorded in it shape how analysts interpret on-chain activity. When outputs carry fabricated addresses, they can distort assumptions about how many distinct addresses are genuinely in use. For related coverage, see Bitcoin Faces $77,000 Resistance as Fed Pressure Builds on September 2, 2026.
The technique itself is well documented. Bitcoin’s scripting system allows outputs to hold arbitrary bytes, and community discussion of a bloated UTXO set has long flagged that storing data this way leaves unspendable entries nodes must retain. The relevant mechanics are described in Bitcoin’s Script documentation.
This is a data-quality concern rather than a direct network risk. The 96,000 figure points to noise in address-level datasets, not a protocol failure; consensus rules still treat these outputs exactly as encoded. Tooling that tracks how outputs are handled, such as guidance on UTXO safety for wallets that hold inscriptions, reflects how carefully individual outputs now need to be interpreted. For related coverage, see BitGo to Migrate $7.4 Billion in Wrapped Bitcoin From LayerZero to Chainlink CCIP.
What observers should watch next
Given the weak public detail behind the scan, analysts will likely want to verify how these outputs were created and whether the pattern is isolated or persistent across recent blocks. Confirming the methodology behind the count is the first step before drawing broader conclusions.
A key open question is whether the outputs look operational, accidental, or experimental in origin. Continued work on node behavior, including changes shipped in Bitcoin Core 30.0, is relevant to how such data-carrying outputs are relayed and stored going forward.
For now, the practical takeaway sits with data interpretation. The 96,000-output finding is a reminder that address counts and UTXO-set size can be inflated by embedded data, a nuance that matters most to researchers reading Bitcoin’s on-chain metrics rather than to the network’s underlying monetary properties.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
