Native UTXOs on Ethereum. Payments should be one-shot objects, not permanent state. Bitcoin got this right. Ethereum can bring the same idea to payments: prove existence from history, keep only a spent bit in state, and reduce permanent state by ~99.8%. Check out the blog post for details.

Bitcoin miners don't censor UTXOs, so why should @THORChain? That's the argument @cbarraford made to me. 🔁 @tayvano_ calls it a false dichotomy and says THORChain should try to stop direct thefts.

Toccata hard fork brings programmable UTXOs to @kaspaunchained and native covenants and ZK verification to its Proof-of-Work BlockDAG. Our article covers what changed, what Argent adds for builders and how ChangeNOW supports $KAS. See what Toccata adds to Kaspa 👇

THE BITCOIN LOSS/PROFIT RATIO IS HITTING EXTREME LEVELS. UTXOs in loss becoming increasingly significant. These readings only appear during periods of strong market stress. Bear market territory on this specific metric. But here is the important context. This indicator strips out price distortion entirely. It simply counts UTXOs in profit versus loss. A constant specific to Bitcoin behavior. And at these extreme loss ratios long term accumulation opportunities have historically been exceptional. The pain is real. The signal is equally real. But watch what happens when euphoria eventually takes over. When UTXOs in profit send this ratio sharply higher... That is when the music stops. Right now we are nowhere near that moment. Which means the accumulation window remains open.

📊 Bitcoin UTXO analysis signals the start of a broader capitulation phase, as the ratio of #UTXOs# spent at a loss has dropped to its lowest levels — corresponding to bear market phases — analyst @Darkfost_Coc points out. This is the first time this signal has triggered since the start of the correction in October 2025. The analyst notes that these periods "have always been profitable for long-term investors," as they correspond to the moment when the majority gives up and loses interest. Meanwhile, analyst @lukasz_wydra highlights that the bullish RSI divergence on the #Bitcoin# chart has now been confirmed — with the decline stalling exactly inside a key support zone while the expected panic failed to materialize.

For those who dont know, $DOG is Rune #3#. Etched at block 840,000, the 2024 halving. It sits in Bitcoin UTXOs, under the same base-layer security as BTC. Not a sidechain. Not a wrapper. $DOG MODE HAS BEEN ACTIVATED Now you know

One positive consequence of all the recent detailed thinking about transaction formats - not just 8141, also "future of state" discussions eg. UTXOs, PBT, keyed nonces, and also recursive STARK mempool - is that we have a much more explicit understanding of how transactions have "actions" and "dependencies", and we can engineer around optimizing the two separately. An action is an effect that a transaction has. A dependency is a fact about the transaction and/or the state that must be true for the transaction to be valid. eg. a signature is a dependency, a Merkle proof of a UTXO is a dependency, a ZK-SNARK (or STARK) is a dependency, a call that sends ETH is an action Dependencies can be processed in parallel. Dependencies that involve state can be reasoned about by a mempool, especially if the specific state accessed is statically declared. Dependencies that are pure (no state calling allowed) can be processed once at the mempool layer and never need to be processed again - and potentially even replaced with a STARK verifying them, allowing not just execution but also data to be elided. In principle, dependencies and actions can all be expressed as calls (if needed, calls to precompiles). This would make the transaction format itself very bare-bones and minimalist (a list of calls, flags for the type of each call eg. dependencies would be static or pure calls, and origin, nonce, etc) and allows maximum cross-compatibility even if different EVM chains have different features. In 2015-era Ethereum, thinking explicitly about these differences was not very important: execution was execution, there were few enough transactions that we could process them all serially, and single-key ECDSA accounts were good enough for everyone. Ethereum's current scaling strategy, however, requires moving beyond that paradigm. Ethereum is beloved by many developers because the execution and state model is so dynamic and flexible. But dynamic and flexible is not friendly to scaling. Fortunately, >90% of Ethereum's activity by volume does not require anything dynamic and flexible. So, we require contracts, accounts and transactions to more explicitly specify what is dynamic and flexible and what is more statically-analyzable but more restrictive, and more statically-analyzable things get the lowest gas cost and thus scale the most. Effectively, learning from the best of both the 2015-era Ethereum model and a more Bitcoin-like model (reminder: Bitcoin has had what I call account abstraction since the beginning), and making a mixture of both (really, the full spectrum between both) available, with gas costs appropriate for the level of scale involved. New state types, the recursive STARK mempool, keyed nonces, etc all go in this direction. This all relates to transaction types, because a general-purpose transaction type is a very natural interface layer on top of which all of this can be implemented, and the current thinking around the EIP-8141 transaction type is going in this exact direction that is friendly to these kinds of future generalizations. So in that sense, 8141 done well is not just a culmination of 10 years of account abstraction work, it's also preparation for the next few years of responsible decentralization-friendly hyper-scaling.

Near Brings More Privacy To Bitcoin Payments Unstoppable Wallet (@unstoppablebyhs) has integrated NEAR Intents’ (@near_intents) Confidential Execution for more private on-chain payments. Its new Private Send feature lets users send bitcoin:native without exposing their originating wallet UTXOs. The feature will also support ethereum:native, USDT, USDC and other eligible assets. Unstoppable says the system improves privacy without offering complete anonymity. Private Send is expected to launch with version 0.51 by the end of the week.

RGB Lightning Node v0.0.8 Release Notes - Added direction validation for multi-hop sell paths. - Added a pre-check for BTC/RGB per-HTLC capacity on the first hop. - Added RGB channel validation for the return path of direct sell transactions. - Added support for manual UTXO consolidation. - Fixed an issue where channels could not be opened when multiple small UTXOs were used. v0.0.8 introduced a major refactoring of RGB-LDK-Node as planned in the roadmap. The issue “RGB Asset Loss After Channel Opening Failure” is currently in progress and will be fixed in v0.0.9. Make Bitcoin smart and build with us.