Lately, when using BTC L1 asset tools, I increasingly feel that there is still an unresolved issue with wallets:

It's not simply about whether the balance display is accurate.
The real trouble is that a single UTXO may carry multiple asset semantics.
For example, BTC itself, inscriptions, Runes, Bitmap, Alkanes, and even some application-specific state interpretations can all be related to the same output.
Bitcoin Core only knows about UTXOs.
But users see "how many assets I have."
There is a dangerous illusion here:
The assets identified by the platform are not equal to all the asset semantics on that UTXO.
Therefore, the real difficulty with tools like multi-send, consolidation, split, and merge is not stitching together the transaction, but answering a question before signing:
What exactly will be spent this time?
I think the ideal solution is for both wallets and markets to add an asset-aware preflight layer:
1. Multi-indexer cross-identification
2. Automatically mark mixed-asset UTXOs in red
3. Default lock high-risk outputs
4. PSBT-level display of recipient / amount / asset id / fee / change
5. Before batch operations, perform a small self-send verification
The more BTC L1 assets there are, the truly important infrastructure may not be the transaction button, but a "don't accidentally harm assets" safety layer.
Otherwise, users are not transferring — they are blindly signing UTXO state changes they don't understand.