Support ECDSA Message Signing for Taproot Addresses and Support getNetwork

[ty-bt]

Story

Hello, I am trying to support the Xverse wallet in simple-staking, but during testing, I found that signMessage prompts "ECDSA is not supported for Taproot Addresses." Could you please help support ECDSA message signing for Taproot addresses? Thank you very much.

Also, is it possible to support getNetwork? Currently, I can only determine the network based on the address. Thank you!

[teebszet]

Also, is it possible to support getNetwork? Currently, I can only determine the network based on the address. Thank you!

this is being worked on and will be shipping very soon

[emilcondrea]

Can you clarify what do you need for ECDSA message signing for taproot?
There are 2 common ways of message signing

• using bip322 and for taproot only schnorr signatures are supported by consensus/protocol
• using bip137(legacy signing), for this to work the message needs to be signed with the public key derived from taproot address

If you are looking for bip137 I am curious which validation libraries you plan to use for message verification as most of them don't work out of the box with taproot.

[steven-tomo]

@emilcondrea Babylon staking requires this feature. They need ECDSA message signing for verification.

[emilcondrea]

We are investigating this.

[emilcondrea]

Can you clarify why you need to sign with the Taproot address? In Xverse payment addresses use native or nested segwit. Taproot is only used for ordinals: https://docs.xverse.app/sats-connect/connecting-to-the-wallet/connect-to-xverse-wallet

So if simplestacking only cares about stacking bitcoin, using payment address is enough.

[steven-tomo]

@emilcondrea you can try the demo: https://babylon-staking.tomo.inc/.
okx wallet and bitget wallet can sign ecdsa message with taproot.
but xverse doesn't work.

[emilcondrea]

It looks like it selects the taproot address which is only used for ordinals. During wallet connection it should choose the payment address. How is it connecting & fetching the address ? Can you point to the sdk?

Xverse uses a split address model where users have a native/nested address used for btc payments and a taproot address for inscriptions.

[emilcondrea]

Inspecting simple stacking connector it looks it selects ordinals address on purpose.

So what is the purpose of the app? To stack ordinals or to stack bitcoin?