pull down to refresh
I thought Bitcoin-Blake2B already has one way replay protection. Why not use that instead?
Unified sighash:
A new opt-in SIGHASH_UNIFIED format works across legacy, SegWit and Taproot inputs.
It provides linear signature hashing, commits to every input amount and gives one-way replay protection.
Source: #1558342
reply
Maybe there is no wallet software that implements it, yet? Knots might have it, but they may have just introduced it on protocol level and not as a wallet feature, yet. Also, it is hard to import funds from mnemomic-based wallets into Bitcoin Core, so presumably the same is true for Knots.
reply
the irony of the whole thing is the reason for my post.
Doublespeak, I believe that’s what they call it
reply
I get a feeling that people are going to lose a lot of real BTC trying to either unload this shitcoin or if they’re bip110ers they’ll willingly trade their real coins for shit.
In his latest tutorial video Kratter walks you through how to protect yourself from a replay attack. He literally walks you step-by-step on how to send a transaction with an op return greater than 83 bytes which ironically was the main reason behind the bip in the first place.
He pushes a “experimental software” a forked sparrow wallet (shrike).
And finishes with “I really hope I’ve done everything right in this video. If I haven’t, if you see something I’ve done wrong, be sure to put some notes in the um in the comments section below.”
I’m really sorry for anyone’s recent or future loss 🫡.