Sebastian / Sebastian is on Nostr

"494c2c44b23e60ca80c61546eec9cf8f2f66d711deedc049a9aeff89ffe65540c3054253fc1fe25e43f0dff1aeedfd6e1e589bdf9e68bc51e93024d27a1eceb7"

Last Notes

2026-09-09 17:26:49 GMT

This #L-BTC story has to be the "I lost my #BTC on a boat accident" of the year 2026.

2026-09-09 17:22:37 GMT

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.
https://blossom.primal.net/19560af5f4dcae3fe64efdadceb2745439fa0d222c07e8244bea0fa7f3d2b9ef.png

2026-09-06 05:22:08 GMT

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? 👀

2026-09-06 05:02:44 GMT

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... 😬
https://blossom.primal.net/0eb447e22fafeaff738ff1b335739d76dd06a26d2a4ab68c7bf54847ff856cac.png

2026-09-05 07:29:33 GMT

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 https://mempool.space and https://mempool.guide ) 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.

2026-09-05 06:36:32 GMT

- reply

Do you ever read your own advice from time to time? Looking at your posts on here, it doesn't seem that way 😂

2026-09-03 16:23:25 GMT

- reply

Ah yes, nothing is better than sending your assets to some random sites 😂 People, be careful out there, could be a rug pull!

2026-08-29 19:52:32 GMT

- reply

Doesn't the difficulty adjustment exist exactly for this? Too little fees => mining earnings sink => miners shutdown their ASICs because of lower profit => total network hashrate sinks => blocks don't come on 10 min average => difficulty is lowered => profitable mining setup reached. If the price doesn't play along, the hashrate sinks and it goes up when #BTC pumps.

2026-08-29 16:04:25 GMT

@nprofile…kwh5 https://www.youtube.com/watch?v=83ItqcnAi3s You are right on this one. You have chosen to support the hard fork and that's fully your choice, anyone can run the open source software they want, on their node, on their hardware. Personal attacks are out of place and say more about the people behind those messages. I'm excited to see what happens with the blake2b coin and how the new node implementation is perceived. As of now, I'm running a non- #BIP110 client and I find it unfortunate that @nprofile…7y8r won't be further supporting that chain with bitcoin knots, it seems. I'm open to new node recommendations valid on the current SHA256 chain.

2026-08-29 05:41:09 GMT

- reply

It could work but it's not guaranteed and the chances are super low. Think of it this way:
As of today, all the BTC SHA256 nodes accept both transactions that are valid in the #BIP110 and non BIP110 chain.
All the BTC SHA256 nodes enforcing BIP110 accept only transactions that are compliant with the mempool filters of BIP110 and also they accept only blocks that implement the mandatory signaling on a chain that requires the signaling since the split.
The BIP110 chain has been adding new blocks with BIP110 signals only and those blocks have been very few since the split. The "normal" SHA256 chain has been adding many blocks since the split though, so there have been many new confirmed UTXO.
So it's 29th August today and you send your BTC from the CEX to your hardware wallet, this will happen:
The CEX's BTC node will propagate a UTXO based on previous UTXO to send BTC to your address. Note that CEX will have many UTXO constantly, since they transact often.
Chances are, their UTXO is based on UTXOs that were not mined on the BIP110 chain since the split but are only present on the "normal" chain.
In other words, if that UTXO today uses UTXOs that were not mined on the BIP110 chain since the split, the transaction won't be valid on the BIP110 chain because there is no such UTXO since the split.
In the rare case that the CEX uses an UTXO that was present *before* the BIP110 chain split that happened earlier this month and they create a new UTXO to your address, then that transaction could also be seen as valid on both chains and nodes + miners could pick it up on both sides of the chains, including it in their blocks, effectively doing the same transaction on both chains. When the recipient address is controlled by your own private keys, it's the best case, you have effectively ensured your coins on both chains. Considering that the chains are quite different since the split, valid UTXOs from a CEX are very unlikely.
What would be the best case instead?
Ideally, you would have all your BTC in self custody *before* the chain split that happened earlier this month. Then you stop transacting and wait for the blake2b coin to have their own node software etc., this should be the case by 1st September. By that point, both chains will be confirmed to be completely different and transactions created by HODLers by then will be based on data valid only on one chain but not the other. This is also the best scenario for dumping one coin and keeping the other.
I hope this helps a bit.

2026-08-27 05:21:05 GMT

- reply

👆

2026-08-24 15:17:09 GMT

- reply

Most likely it will be a waste of their time and money. #BIP110 was a good idea as a soft fork, as a hard fork it is doomed. The small #BIP110 crowd has been split again, there will be a single point of failure with Luke's new node software, no hash power security, no proper wallet software... be careful out there. I'll wait and see if CEX list the coin. The next step is dumping. Many sellers, little buyers.

2026-08-23 18:08:40 GMT

"#BIP110 's fork will have an immaculate conception". Sorry @nprofile…kwh5 , I've been following your channel for years but on this point I strongly disagree. The Blake2 coin was already influenced by @nprofile…7y8r and its node client software will launch with a face tied to that coin's name. This creates an attack surface that wasn't there when Satoshi created #Bitcoin. The social situation that #Bitcoin had at the time can't be replicated. Every shitcoiner has experienced that already.

2024-08-27 16:44:17 GMT

- reply

Keep in mind that Telegram doesn't use encrypted channels by default. I'd recommend Signal instead.

2024-02-16 10:53:17 GMT

- reply

Another great video Matthew, thank you.