pull down to refresh

Difference between Sparrow and Blue Wallet in signing/verifying a btc address?
320 sats \ 2 comments \ @BitcoinHandsOn 23 Nov bitcoin
I'm working on new exercises for my book MORE Bitcoin, Hand-On! (my previous book Bitcoin, Hand-On! is available here - https://www.amazon.com/dp/B0F4SZSCH8).
This exercise is to sign/verify an address with a message. I'm trying it out in both Sparrow and Blue Wallet. But the signature that comes up does NOT match between these 2 tools.
AI says that there's not really standards for message signing and verification, and different tools may use a different message prefix, which changes the signature.
Anyone have thoughts on this? Does this pretty much mean that if you provide a signature, you also have to say which tool you're using?
write
preview
related posts
153 sats \ 0 replies \ @kristapsk 23 Nov
Yes, signing with anything else than P2PKH (old addresses starting with 1) is non-standard, different wallets use different formats. Basically, there are two standards - BIP137 and BIP322.
reply
32 sats \ 0 replies \ @mothepro 24 Nov
The standards only exist around signing using a legacy address. Also, I have found that as long as the base64 decoded signature is 65 bytes. you can safely ignore the first byte.
It's easier to try all the recovery flag / compression combinations rather than rely on the recovery id byte.
reply