Default avatar
npub1tfyk...prn8
npub1tfyk...prn8
This #L-BTC story has to be the "I lost my #BTC on a boat accident" of the year 2026.
What do you think? Is it dishonest to put 245k USD next to 3.127 #blake2b #BTC as the market value for subsidy + fees? Last time I checked, there's only one exchange actually providing a market (XBT/USDT) for the #BIP110 coin, valued at 236 USDT for one XBT. image
Let's look at this random #bitcoin address: bc1qt7rlt7u770nra4pvgan26txd3tu4yvw7jr92g6 As of now, it has a confirmed balance of 51.52101347 #BTC, a bit more than 4 million in paper USD. Interestingly though, transactions around that address have been both mined on the SHA256 and the #blake2b chain, very recently. This transaction, for example: b487419b1b2d7dd3bcdd0de551f5cda573790c96d3f2ea65daae2864e03c4bae Which chain did the sender intend to use? The transaction had no replay protection, so either #NiceHash or #AlphaPool therefore performed a replay attack. Could this be considered malicious activity? 👀
On the #BIP110 chain using #blake2b there's currently a block every 4.4 minutes, on average. Many blocks are empty. Let's see where this #bitcoin fork is going... 😬 image
For those wondering: Protecting yourself from a replay attack on #bitcoin can be easy. Let's assume you have been hodling for a while and you have UTXOs in your wallet that already existed before the #bip110 soft fork became a hard fork. Protect yourself by getting some new #btc on the SHA256 chain (from a DEX or CEX), transfer that to your own wallet, verify that the new UTXO is only present in one of the two chains (e.g. by checking and ) and then create a new transfer to your own wallet. The new transaction broadcasted will include an UTXO that is only valid on the SHA256 chain, thus creating a new UTXO that will only be valid on that chain also. This way, your previous UTXOs should stay as is on the #blake2b chain while on the SHA256 chain you will have a single, completely new UTXO.