-
Notifications
You must be signed in to change notification settings - Fork 15
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
[BUG] Error message when attempting to claim airdrop at app.tangle.tools/claim #2273
Comments
This error is due to Tangle network not being supported by Ledger app, we plan to release a ledger app soon. |
I'm not sure Tangle/Ledger support is needed here. I'm signing the text with the Polkadot app on Ledger. The Polkadot address is eligible for airdrop based on being a Polkadot validator. The recipient address is a Tangle wallet and is not a Ledger wallet. Indeed the reason I am requesting the payout to a different address is that I don't expect to be able to use the Ledger with Tangle. Is there an alternate way to claim the airdrop if this method is not supported? |
We're investigating @validorange and will get back to you to re-test. |
After conducting some investigations, I have reached several conclusions:
Regarding which signature scheme to use when users employ Ledger via Talisman, I'm uncertain. However, based on my research findings, I propose modifying the last byte if the signature is from EVM wallets and truncating the first byte if the signature is from Substrate wallets, whether both are via Ledger. |
Hello, @validorange! Could you please try signing and claiming with your Ledger wallet on this PR preview link? |
Hi @AtelyPham , |
Is there an existing issue for this?
Current Behavior
The claim airdrop dapp gives an error when I try to claim an airdrop from my Ledger device using Talisman wallet.
The airdrop remains unclaimed after the error.
Expected Behavior
I expected to receive the airdrop.
Steps To Reproduce
Screenshot
https://github.com/webb-tools/webb-dapp/assets/150610035/038f91a1-2a3f-40eb-b0c5-5d491c271d06
Anything else?
No response
The text was updated successfully, but these errors were encountered: