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
Txn version not supported #104
Comments
Can confirm. Same also happens with ledger-polkadot. All type of transactions fail with the error stated above. Seems like it started happening with the latest runtime upgrade. |
Related to: LedgerHQ#10 |
the ledger-polkadot issue is resolved after the new ledger polkadot app was released. There is no Kusama updated app on ledger so the Kusama issue still persists |
yes, Kusama had another additional release and we are working with Ledger on that at the moment. |
The referenced PR that was valid for yesterday's upgrade (v6) is not applicable today because the network is running (v7) |
does anyone know the derivation path used by ledger for the KSM wallet? How long will it take to fix it or roll back the app? |
Is there any other 3rd party wallet that allows Ledger-Kusama app v5.30.1 to interact with the blockchain? I'd like to be able to stake, unstake, unbond, transfer again. |
I also cant get DOT to work. I have the same error for DOT and KSM; everything is fully updated |
Any updates on when the KSM -ledger bug will be fixed? I need to unstake this KSM ASAP... |
great, you are a KSM programmer? Any updates for your investors? |
New Ledger Live update... might help but I doubt it. |
Any update? |
I received the below just now from Polka Support."This happened because of the most recent update to the Kusama runtime. However, these upgrades happen often and sometimes a new transaction version is introduced. When this happens a new version of the app needs to be developed in order to be compatible with the new transaction version. Zondax is currently working on a new app that will solve this. This time the overhaul was quite big, which is why it's taking a bit longer to release the new version. I understand this can be unsettling, but rest assured your funds are safe. We are exploring ways to make this process more seamless, but it's quite difficult because of the way the Ledger device handles accounts and signs transactions. If you want to explore another cold storage method, I can recommend Parity Signer. When installed on a factory reset phone that's kept in airplane mode, it provides practically on par with the security Ledger provides and it doesn't suffer from these "downtimes". However, one downside is that you can't verify what you're signing, like you can on Ledger, so you need to trust the site that provides the QR code you read with the app. You can check the video in this article on how to create an account in Parity Singer: I hope this helps. Let me know if you have any other questions." |
for cases like this one i.e. people locked out of their KSM and DOT funds if they use the ledger, PLEASE add support for the BIP39 passphrase in https://polkadot.js.org/ , so that at least we do have an emergency recovery option to access our funds. Currently people who use the BIP39 passphrase have no recovery option at all :( :( :( I am referring to the user-defined string (BIP39 passphrase) that can be used in addition to the BIP39 seed phrase (12, 15 or 24 words). It is part of the BIP39 standard and supported by the Ledger and most other wallets, but sadly missing from https://polkadot.js.org/ . If you have a DOT or KSM account derived from a passphrased seed, there is no way to access them with https://polkadot.js.org/ . |
we created a library to allow for recovery. This has always been an option, however, we have not been asked to build a user interface for this because of the inherent risk of leaking the mnemonic that is connected to other coins. We have finalized our update. It was really extensive.. (at least 258 files) and it is being tested at this precise moment. As the ecosystem approaches Polkadot first parachains this update was much larger than usual and affected Kusama data structures much more than normal (the canary chain). We believe very much in the substrate ecosystem and look forward to a great 2022! |
Ok @jleni Im having the same issue. So to clarify, you guys are working on the fix for the "txn version not supported" for KSM via ledger? Feeling uneasy about being stuck Thank you |
automatically closed |
related PR LedgerHQ#11 |
Yet you support entering the bip39 24 word menemonic. Why not implement bip39 completely? There are software wallets that support bip39 mnemonic and passphrase, e.g coinomi. The issue is not about risking to expose a hardware wallet seed. The issue is being able to use a seed thar uses a bip39 passphrase, whether that seed was used in a hardware or software wallet is irrelevant. |
Not sure what you mean... Ledger apps (this included) are fully BIP39 and
BIP44 compatible.
…On Thu, 21 Oct 2021 at 23:01, loupiote ***@***.***> wrote:
@jleni <https://github.com/jleni>
however, we have not been asked to build a user interface for this because
of the inherent risk of leaking the mnemonic that is connected to other
coins.
Yet you support entering the bip39 24 word menemonic. Why not implement
bip39 completely? There are software wallets that support bip39 mnemonic
and passphrase, e.g coinomi. The issue is not about risking to expose a
hardware wallet seed. The issue is being able to use a seed thar uses a
bip39 passphrase, whether that seed was used in a hardware or software
wallet is irrelevant.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADIQLWHHFSS7XUN22UEKA2LUIB5R7ANCNFSM5FZX3YAA>
.
|
@jleni thanks for your reply. |
Hi, ledger just released the app. |
Could you indicate which operation you are trying to execute?
…On Fri, 22 Oct 2021 at 14:58, eleuname84 ***@***.***> wrote:
Hi, ledger just released the app.
After updating the firmware to 2.0 and the KSM app itself, I still get the
same error Txn version not supported.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADIQLWBZAO33VAIJ3OFGUY3UIFNXVANCNFSM5FZX3YAA>
.
|
I am trying to stop staking, so from https://polkadot.js.org/apps/#/staking/actions I click stop, sign on ledger and I got txn version not supported. |
I've tested a bit more, the app crashes on average 15 times, then miracolously remains open for once, then I submit the tx for signing, that's when I get the same error as before the update, txn version not supported. I hope this helps. |
Are you sure what you describe as a crash is not ledger live that is open
and interfering? If that is the case, these are not crashes.
Could you verify that you are not leaving ledger live open please?
…On Fri, 22 Oct 2021 at 15:36, eleuname84 ***@***.***> wrote:
I've tested a bit more, the app crashes on average 15 times, then
miracolously remains open for once, then I submit the tx for signing,
that's when I get the same error as before the update, txn version not
supported. I hope this helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADIQLWHJZ6EEZKHFOAQU6VTUIFSFJANCNFSM5FZX3YAA>
.
|
Closing ledger live refers to the supposed "crashes" you describe. These
are ledger sending a close request because it was probably open.
Let us check chill as a different issue.
…On Fri, 22 Oct 2021 at 15:44, eleuname84 ***@***.***> wrote:
yes, ledger live is closed , same behaviour:
[image: image]
<https://user-images.githubusercontent.com/63816425/138463752-09232fa3-9e29-436c-8905-9c7af7c85dd5.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADIQLWBSVPBYGCKXEXFGI7DUIFTCBANCNFSM5FZX3YAA>
.
|
Icam talking about polkadot-js. I cannot enter my coinomi seed in it,
because i always use a bip39 passphrase, and polkadot-js is not bip39
compliant (it does not support passphrases!!!)
Le ven. 22 oct. 2021 à 00:12, Juan Leni ***@***.***> a écrit :
… Not sure what you mean... Ledger apps (this included) are fully BIP39 and
BIP44 compatible.
On Thu, 21 Oct 2021 at 23:01, loupiote ***@***.***> wrote:
> @jleni <https://github.com/jleni>
>
> however, we have not been asked to build a user interface for this
because
> of the inherent risk of leaking the mnemonic that is connected to other
> coins.
>
> Yet you support entering the bip39 24 word menemonic. Why not implement
> bip39 completely? There are software wallets that support bip39 mnemonic
> and passphrase, e.g coinomi. The issue is not about risking to expose a
> hardware wallet seed. The issue is being able to use a seed thar uses a
> bip39 passphrase, whether that seed was used in a hardware or software
> wallet is irrelevant.
>
> —
> You are receiving this because you were mentioned.
>
>
> Reply to this email directly, view it on GitHub
> <
#104 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ADIQLWHHFSS7XUN22UEKA2LUIB5R7ANCNFSM5FZX3YAA
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTVMJ46B227IZAO3CPKNL3UICF4XANCNFSM5FZX3YAA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I see, so excluding my app initial problem, the txn error still persist. what to do next? will you test/investigate further? |
I am talking about polkadot-js. I cannot enter my coinomi seed in it, because i always use a bip39 passphrase, and polkadot-js is not bip39 compliant (it does not support passphrases!!!) |
I can confirm this issue "Txn version not supported" with the new ledger live/ ksm app Issue happens both when using:
Unable to send, unbond, redeem.
|
Ok, that's a completely different problem in polkadot-js. |
Huge thank you from me, Txn issue is fixed on my end! Adding details in case it helps others:
|
@tsiitd
|
Worked perfectly after updating to Kusama app v7.9111.00
|
oh-my-god. |
No problem, I was just replying to you and asking you to confirm that your version was correct |
After the release, our testing plus a few confirmations from users, we are closing this issue. If you find this problem:
if you still have trouble, PLEASE open a new issue so we can track things independently! |
I just moved some Kusama from one account to another --- not getting Tx Version not supported message. Thanks!!!! |
Hello, I am trying to vote on a proposal. LedgerLive v2.34.3 Is it an issue with batch calls? On polkadot.js I've tried connecting ledger via WebUSB as well as WebHID. I've also tried using Ledger Live's Kusama app as well as their KusamaXL app. After a couple days now trying here are the errors I've received: Unable to claim interface |
Kusama app v5.30.1
polkadot{.js} extension 0.40.1
I was trying to change the validators I am using for staking but was hit with the message
Txn version not supported
The text was updated successfully, but these errors were encountered: