How to verify legacy address signatures signed using window.unisat.signMessage? about extension

[cloud6605]

please search "sign" in https://docs.unisat.io/dev/unisat-wallet-api, then you can find the example.

[thienma1258]

also wondering how to doing that too

[ArbitronNL]

please search "sign" in https://docs.unisat.io/dev/unisat-wallet-api, then you can find the example.

@GGG888GGG @cloud6605 We hereby request this issue to be re-opened, since it is not about "how" to sign a message, but the fact that the created signature is invalid: cannot be verified by bitcoin-core RPC or by bitcoinjs.Message.verify.

---

As a matter of fact, we've determined the same issue in BitonicNL/verify-signed-message#3 (comment). As a TLDR, UniSat is using the incorrect recovery flags for addresses, causing the signatures to not work anywhere that the uses the official specification (Electrum, Bitcoin Core, Trezor, etc).