Hardfork Blake2B MTB Explorer

[Hardfork Blake2B MTB Explorer @berm_blazer]

@cguida6 @SteveSimple @bitcoinsbanker 😊

[Satoshi Stockpiler 🟧 #BIP-110 @ConsumingCrypto]

Did @blockstreak/@Adam3us just pull an @nvk? Investigate the big players including @excellion. I do not trust anyone anymore.

[Kretch🐸 bip110 blake2b @kretchino]

@cguida6 @Blockstream Scamson Mao and his Aqua wallet just got liquified🤗

[Hardfork Kratter @mattkratter]

@mempool Someone needs to check Andy's pockets for spare change

[Hardfork Kratter @mattkratter]

@AquaBitcoin @Liquid_BTC @Blockstream Has anybody checked Scamson's pockets yet? Maybe some of the coins made their way there?

[Trey Sellers ∞/21M @ts_hodl]

@Liquid_BTC @NEEDcreations @Blockstream Is this related in @AquaBitcoin wallet?

[Hardfork Blake2B MTB Explorer @berm_blazer]

@davelund_ @phil_geiger 😂

[Hardfork Blake2B MTB Explorer @berm_blazer]

@Rory_D_Fpic @roryhighside 😂. Poor Rory.

[Hardfork Blake2B MTB Explorer @berm_blazer]

@parman_the So I understand it has electrum. In order to split coins, you need to add op returns not valid on blake2b, when signing ? To prevent replay?

[Luke Dashjr @LukeDashjr]

@Scavacini777 Bitcoin Knots is basically the only Bitcoin node software left, and it is still maintained.

[Greg Tonoski, BIP-110, Blake2b @GregTonoski]

@MarcanoFilms @Awoken_Lazarus Mining bitcoins, too. Solo.

[Luke Dashjr @LukeDashjr]

August 8th, Spamcoin forked off from Bitcoin with a contentious hardfork attempt (removing/violating BIP110 rules). Bitcoin continued, albeit maimed by miner abandonment.

August 19th, "Purity" did the same (by removing/replacing the DAA). Bitcoin continued, unfazed.

August 30th, Bitcoin deployed a proof-of-work change to BLAKE2b. It was uncontroversial and unanimously supported by what was left of the network, and carries the original chain forward undisputed.

[Greg Tonoski, BIP-110, Blake2b @GregTonoski]

$ ./bitcoin-cli getmininginfo
5 PH/s and keeps rising 🚀

[stepnoy🪢 @stepnoy385394]

@uanbtc A fork is Bitcoin by birthright, it is already Bitcoin. This is a rare chance when there is a large team of ideologically and technically mature people around the fork, it is necessary to take advantage of it.

[Seed @sesi_the_man]

Do you really want to buy something from an individual/manufacturer that posts something like this… and then deletes it?

[Pepe Lapiu | Sha-coin = Shit-coin @LapiuPepe]

BITCOINERS PSA: Replay protect your coin!!

So for those of you who want to do replay protection, here are the instructions if you run a node or not. It still works without a node.

And don't worry, this is 100% safe. None of the coin on the core chain will be affected by this.

1- Install and run Shrike wallet, which is just Sparrow adapted to work on the Blake chain.

2- If you run a node other than Knots 29.4.1, you might want to turn off your node before you do any of this. Or just run Shrike on a machine that doesn't have a node.

3- In Shrike, create a new wallet. Call it something you can relate to. Like "protected Blake" or whatever else you want. This is where you will send all your Blake coin. It's not worth all that much right now, so you might not want to go crazy with the wallet security stuff just now.

4- Load your core coin wallet seed into Shrike. Don't worry, Shrike can only see your Blake chain coin, it can't move your core chain coin.

It should take some time to scan the chain for your wallet. For me it took almost 6 hours per wallet.

5- If you have sent or received any coin on the core chain since August 8, your balance could look different than your core chain wallet. Don't worry, that's okay and to be expected.

6- Go to UTXOs tab and select only the UTXO with the least amount of sats on it. So you can get comfortable with the process.

7- Click "Send Selected ...." button at the bottom right.

8- You should now be on the Send tab. Copy an address from the "protected Blake" wallet you created earlier. Send it.

9- Now you can check if your coin is being received in your "protected Blake" wallet. And if you check your old core coin wallet, you will see nothing has moved on the core chain.

10- Repeat for all the other UTXOs. You can do that one by one, or all at once. Depends on your level of comfort.

Now your coin is safe from replay on either chain.

You can do as you wish with your Blake coin. Sell it, buy more, or hodl it. My advise is that you just put your seed away and forget all about that wallet for now. It will be your life boat at some point.

And most importantly, ask yourself why bitcoin influencers like BTC Sessions are refusing to show you any tutorial on how to replay protect your bitcoin, and falsely claiming this is dangerous, like he did here:

And you might want to keep an eye on your wallet in Shrike whenever someone sends you any core coin. They might actually be sending you one of each as a bonus because they didn't bother to do replay protection.

Cheers 🍻

Please share this and retweet it for maximum views.

[Simple Steve 🌌 @SteveSimple]

@LucasBean91 If Coldcard needs more income I don’t understand why they can’t just ask the CIA for more

[HMLE @1hmle]

How about you refund purchase costs and reimburse stolen funds to the victims of your shitty product.

[Luke Dashjr @LukeDashjr]

Lots of things deter it happening again, actually. The most obvious being the precedent. But also BLAKE2b isn't vulnerable to ASICBoost, is simple enough for a competitive manufacturer market to form, etc. And RDTS closes the threat of approved data storage. Spam filters continue to work for everything else.

Changing the PoW is long overdue based on technical reasons alone. Bitcoin only stuck with it this long because miners were cooperating. I didn't want things to go down this way, but it has provided a huge opportunity to address many long-standing technical problems with it.

The new fork is Spamcoin, not BLAKE2b. BLAKE2b was deployed with consensus, and remains the same Bitcoin as Bitcoin always was. Spamcoin offers nothing - it lacks all the important properties Bitcoin has.