-
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
Sending STX/SIP10 with Ledger fails with "sending bitcoin is temporary disabled" error #4083
Comments
Hello, I have initiated this topic on Discord due to an issue to send STX from my Hiro wallet and a guy werner.btc has launched this topic on Github. I tried again but I have always the same message, impossible to send STX. My version is 6.2.0 I have installed my extension chrome wallet + ledger with this link chrome-extension://ldinpeekobnhjjdofggfgjlcehhmanlj/index.html#/get-started |
## [6.2.1](v6.2.0...v6.2.1) (2023-08-03) ### Bug Fixes * only route to error when asset is bitcoin, closes [#4083](#4083) ([099f96d](099f96d))
@Lapy71 there is a fix for this in version 6.2.1 of the wallet. This has been released but is pending review by the extension store for Chrome. Once accepted your wallet is expected to update automatically within a couple hours or you can force it with a restart of the browser. |
Thanks Werner
I will update the chrome wallet extension and check if the version is 6.2.1
Many thanks for your help
Have a nice weekend
Regards
Le jeu. 3 août 2023, 13:29, Werner ***@***.***> a écrit :
… @Lapy71 <https://github.com/Lapy71> there is a fix for this in version
6.2.1 of the wallet. This has been released but is pending review by the
extension store for Chrome. Once accepted your wallet is expected to update
automatically within a couple hours or you can force it with a restart of
the browser.
—
Reply to this email directly, view it on GitHub
<#4083 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWCQV42YBQOPKGLUSPIYN3DXTODRVANCNFSM6AAAAAA3AD4RL4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey Werner, I have updated my chrome wallet. |
## [6.2.1](leather-io/extension@v6.2.0...v6.2.1) (2023-08-03) ### Bug Fixes * only route to error when asset is bitcoin, closes [leather-io#4083](leather-io#4083) ([099f96d](leather-io@099f96d))
## [6.3.0](v6.2.1...v6.3.0) (2023-08-08) ### Features * add option to broadcast rpc psbt, closes [#3895](#3895) ([da7b51b](da7b51b)) * add taproot txs in activity list, closes [#3249](#3249) ([d4b1065](d4b1065)) * fetch inscription by output in separate query ([281e138](281e138)) * hide increase fee for txs with taproot input ([a01071f](a01071f)) ### Bug Fixes * change logic to upscale amount in input field ([086c329](086c329)) * handle case when there's no ticker of < 4 chars ([ce3c7c9](ce3c7c9)) * make input text perfectly centered ([0b23519](0b23519)) * only route to error when asset is bitcoin, closes [#4083](#4083) ([bed3820](bed3820)) ### Internal * move fn to utils, use constant and provide more descriptive fn name ([5356069](5356069))
This is affecting any Ledger user. A viable workaround seems to be to use https://sendstx.com to send STX. For other tokens I think Ledger users best wait for a fix unless they are familiar with calling the token contract directly using the Explorer sandbox.
Steps to reproduce
The text was updated successfully, but these errors were encountered: