-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different types of bitcoin addresses in UserSession object #833
Comments
For btc requests, please use our sats-connect library. Here's the repo and the docs are at https://docs.xverse.app |
For additional info, we don't currently use a native segwit address, only a nested segwit, for payments, and taproot, for assets. |
@victorkirov hi, do you have plans/ETA to support native segwit/taproot for payments? |
@chybisov we do have plans. Expect it soonish 🧑🍳 😄 |
@victorkirov, that's nice to hear! The lack of Native Segwit for payments prevents us from supporting the Xverse wallet for LI.FI Widget and Jumper users :) Hope we can see it soon 🙂 |
I think is not possibe, right now. |
…red-txs Fix: Update sponsored flag ui for contract calls + handle legacyResponse [ENG-5981]
Hi team,
When an app connects to the xverse browser extension using @stacks/connect the UserSession object is populated iwth some data from the extension.
Xverse extension returns a nested segwit address right now.
Is it possible to return maybe the native segwit and taproot addresses as well?
The text was updated successfully, but these errors were encountered: