-
Notifications
You must be signed in to change notification settings - Fork 144
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
Update receive modal with more complete options per type #3307
Comments
We've removed the copy option from Bitcoin so we can show a warning on the QR page re: not depositing ordinals. But I agree, we should find a way to put it back for convenience. I also agree the QR code option should show for ordinals and Stacks NFTs.
I imagine it could confuse, though we may have to see. The idea here is that the wallet now has two paths generally for FTs vs NFTs given the current intricacies of our ordinals support, so we wanted to bifurcate the experience. But as we build out feature parity for both, we could end up collapsing into one path again.
We may indeed want to do this once we have coin control in place for both Taproot and Native SegWit addresses. Right now if the user were to deposit inscriptions into the Native SegWit address, they could end up losing them upon sending BTC.
We're assessing how much demand there is for legacy addresses and will add if it's significant. |
Miners and stackers need to use the legacy address but there is not currently a wallet that supports both the STX account and legacy BTC address. Furthermore, some stacking pools payout BTC to the legacy address. So this can be considered an important, if uncommon, utility for a Stacks wallet. |
We have updated this to show more options and it will be available in the next release |
## [6.4.0](v6.3.1...v6.4.0) (2023-08-16) ### Features * updated bitcoin contract api, modified responses, added error handling ([3a77bfc](3a77bfc)) ### Bug Fixes * add copy and qr options to receive modal, closes [#3307](#3307) ([efa14d0](efa14d0)) * **firefox:** short session duration, closes [#4030](#4030) ([5a09c43](5a09c43)) * header indentation for Stacks transaction signing [#3881](#3881) ([8bfcf60](8bfcf60)) ### Internal * add modal for BTC Stamps QR receive ([fc33210](fc33210)) * inscription sends, closes [#4111](#4111) ([b2f0690](b2f0690)) * refactor receive modal to share code better ([77d8704](77d8704))
Primary concerns: Why do some of these have a QR button, some have a Copy button, and some both? Both options should be available for all types of address.
Secondary concerns: Why is the STX address duplicated, one without a QR? This has potential to increase rather than reduce confusion. (By the way, did you know that the 'T' in 'NFT' stands for 'Token'? FT and NFT are all "Tokens".)
A sensible iteration on this might simplify to 3 (or 2) options, with STX shown first (once), and Bitcoin addresses shown next. The Bitcoin address might be simplified to just taproot, since technically isn't any reason why inscribed and uninscribed sats need to be kept separate, assuming the wallet knows not to spend inscribed sats.
Furthermore, shouldn't legacy addresses still be supported for better compatibility? Legacy 1xyz/3xyz and native segwit bc1qxyz could all be hidden under some "advanced" option or something.
The text was updated successfully, but these errors were encountered: