Git Product home page Git Product logo

ledger-kmd-reward-claim's Introduction

Ledger KMD Reward Claim

Claim your KMD rewards on your Ledger device - atomiclabs.github.io/ledger-kmd-reward-claim/

Usage

  • Make sure the KMD app and firmware on your Ledger are up to date.
  • Connect your Ledger.
  • Open the KMD app on your Ledger.
  • Open the Ledger KMD Reward Claim app on your computer.
  • Click the "Check Rewards" button.

If you encounter any problems, be sure to check the FAQ below. If you still can't resolve the problem then open an issue with as much information as possible and we'll try and help.

FAQ

I get an error signing or broadcasting my claim transaction, what went wrong?

This is most likely because you are using an outdated version of the KMD app on your Ledger which doesn't support the overwinter hardfork.

Make sure the KMD app and firmware on your Ledger are up to date before trying to claim your rewards.

If you are sure your device is up to date then please open an issue with as much information as possible and we'll try and help.

Why do all my funds get sent back to a new address?

We follow the same BIP44 standard that Ledger Live follows. We will send your reward claim to the next unused address in your account. This means all UTXOs in a single account are consolidated in a single transaction, which does have some privacy implications. However, in the Komodo ecosystem, most wallets just have a single address which is re-used, this is even worse for privacy. If you want privacy you should use a shielded address. Therefore, after consulting with Komodo lead developer jl777, we don't see this to be an issue.

To clarify, to preserve privacy across accounts, UTXOs in different accounts will never be mixed together, this is why you need to claim your rewards in each account separately. For increased anonymity, you should claim each account on different days to avoid time analysis linking the separate claims.

If consolidating the UTXOs is an issue for you and you'd like a solution that doesn't link addresses together, then please let us know.

My browser is unsupported, can you support it?

We don't blacklist any specific browsers, we detect compatibility for the U2F API which is required to communicate with the Ledger. If the browser doesn't support the U2F API then we show an "Unsupported Browser" dialog.

You can view a list of U2F supporting browsers at caniuse.com/#feat=u2f.

Credits

While this app was built by Atomic Labs, many community members were a great help.

Reference reward calculation code

  • jl777 (C++)
  • pbca26 (JavaScript)
  • CHMEX (PHP)

Consultation

  • jl777
  • ComputerGenie
  • jorian

Testing

  • zatJUM
  • TonyL
  • SHossain

If you feel you've contributed and aren't listed here, please let us know.

License

MIT © Atomic Labs
MIT © Luke Childs

ledger-kmd-reward-claim's People

Contributors

lukechilds avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

ledger-kmd-reward-claim's Issues

Issue with KMD claim recognizing LedgerNanoS

Error "height" option must be a number. It comes in the second verification protocol: Approve all public key export requests on your device. There will be multiple requests.
This fails and I get the error.

I updated firmware and application version for KMD. Tried doing this in three browsers and still.

Please help.

Ledger KMD Reward Claim Issue

Hello,
I need help to locate where are my KMD coins has gone to.
I am claiming KMD store in Ledger Nano S via https://atomiclabs.github.io/ledger-kmd-reward-claim/.
I did several claims in September & October 2019 without problem. However, the last attempt on 29-Oct-2019, the transaction went out and did not return.
The Ledger Live account page shows operations up to 29-Oct-2019, interestingly after connecting my Ledger Nano S to Magnum Wallet only has transaction up to 18-Sept-2019.
Attached are screenshot of Ledger Live & Magnumwallet and Ledgerlive Operations CSV file for reference.
Thanks in advance for any help you may be able to provide.
Ledger Live KMD Operations Screenshot (20200116)
Magnum Wallet Screenshot (20200116)

Error: Ledger device is unavailable

I cannot connect to my Ledger device.

Steps to reproduce:

  1. Start Ledger device, oben the Komodo app.
  2. Open https://atomiclabs.github.io/ledger-kmd-reward-claim/. (Tested with Firefox and Chrome)
  3. Click "Check Rewards"
  4. Get "unavailable" error.

unavailable

I can connect other usb-apps, such as the "TronWalletPlay" or "Ledger Live Desktop" app, so I assume the usb-connection is working in principle.

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu 19.04"

Ledger Nano S

Dear all,
I got the following error, when I tried to claim KMD reward

image

WIN10 64/crome/Ledger NanoS
Could you adwise

BR
Darko

Unable To Claim Komodo Rewards on Ledger Nano S or X

Using Nano X, after step one is green lighted, I get this error message at step two: Failed to Fetch. All pop-up blockers are off. I did this last month without a problem. What's wrong now? All apps and Firmware are up to date. I am using Windows 10, 64 bit. I have also tried on different browsers without success. I am mainly using Chrome.

Ledger Komodo Claim Form

I get the following error when attempting to use the ledger Komodo Claim Form at:
https://atomiclabs.github.io/ledger-kmd-reward-claim/

On Windows 10
A Windows Security Popup appears that appears to override all subsequent attempts to complete any transactions.

On Windows 7
The transaction works all the way up to the final 'broadcasting' step and then fails.

I've used your Claim App, which I'm very thankful for, many times and never had these issues before. It could be related to a Windows Update. Ledger Suggestions are currently not working.

Thanks for your time,
Linda

"Ledger device is unavailable" error

Hi there,

I tried to use this app for the first time to claim my reward for Komodo I'm holding on Ledger Nano S (latest firmware version 1.5.5). I followed the instructions and when a new window "scanning blockchain for rewards" opened, after 15-20 seconds of waiting I got the error message saying "Ledger device is unavailable", which is strange because meanwhile I got question on my Ledger device asking "Export public key?". I guess it means it recognizes my device, but the message says it doesn't so I'm confused. Komodo app on my Ledger is the latest version 1.3.8.
I'm using Chrome (version 73.0.3683.86, official build, 64-bit) and Windows 7.
Any idea what could be wrong?

http://i65.tinypic.com/2jcam1k.png

Support Request

Hello AtomicLabs,

Google Chrome is up to date
Version 73.0.3683.75 (Official Build) (64-bit)

Ledger Nano S Firmware - Secure Element 1.4.2
Ledger Komodo App - 1.2.10
(Both say Up to date on Ledger Live)

I get the following error when attempting to use the ledger Komodo Claim Form at:
https://atomiclabs.github.io/ledger-kmd-reward-claim/
(this occurs in Chrome, Firefox and Opera).

Error
Ledger device: Invalid parameter received (0x6b00)

Check Rewards Button works, and gives the following information:

_________________start
Account 1
125.18286611 KMD

  • 2.46334987 KMD Claimable Rewards
    UTXOs
    Address Value Locktime Rewards Rewards Stop Accruing
    Address Value Locktime Rewards Rewards Stop Accruing
    RUmGiSq2WF62W4iHfMT9ysT1BD7hmxHjSL 24.998 KMD
    0.10565697 KMD 2 months ago
    RTNmhndGn9h6u2KZJKniqypDMLcdAmWeKM 18.998 KMD
    0.0802458 KMD 4 months ago
    RWyFTR7o8fbhAoYqJdhsvQuCGWm9zvwWBv 3.198 KMD
    0 KMD in 2 months
    RJFbZKgMcbg631nWtWMRPmVLL8E7dG1SEc 20.998 KMD
    0.85696166 KMD in 2 months
    RH1i9SeYU2jSXaNYw3AqmfwEyQmwfZRAbk 31.096 KMD
    1.55034595 KMD 2 months ago
    RRd26BX9W2Lrv1g2ZqeRn4KX2q1ST16CkS 25.89486611 KMD
    0 KMD N/A
    Breakdown
    2.59321038 KMD Rewards accrued
    0.12966051 KMD 5% service fee
    0.0002 KMD Network transaction fee
    2.46334987 KMD Total claimable amount
    ________________end

I then hit the Claim Rewards Button resulting in:

__________________start
Claiming Rewards

You should receive a total of 127.64621598 KMD to the new unused address: RSbGKhhcprBQTdtNYAFrckf3FzfKwZqCe9
There will also be a 5% service fee of 0.12966051 KMD to: RQzv9tVzCHXN9j3kF5qNzms555zzLC9HQF

Connect and unlock your Ledger, then open the Komodo app on your device.
Confirm the address on your device matches the new unused address shown above.
Approve the transaction on your device after carefully checking the values and addresses match those shown above.
Broadcasting the reward claim transaction to the network.
_______________end

This results in EITHER a single quick address that matches RSbGKhhcprBQTdtNYAFrckf3FzfKwZqCe9 and then a U2F TIMEOUT (shown below 1)
or I get two quick 'confirm address' events on the ledger with the second address never appearing on the ledger resulting in error 2 (shown below 2)

Claiming Rewards

You should receive a total of 127.64621598 KMD to the new unused address: RSbGKhhcprBQTdtNYAFrckf3FzfKwZqCe9
There will also be a 5% service fee of 0.12966051 KMD to: RQzv9tVzCHXN9j3kF5qNzms555zzLC9HQF

Connect and unlock your Ledger, then open the Komodo app on your device.
Confirm the address on your device matches the new unused address shown above.
Approve the transaction on your device after carefully checking the values and addresses match those shown above.
Broadcasting the reward claim transaction to the network.
Error
Failed to sign with Ledger device: U2F TIMEOUT

Claiming Rewards

You should receive a total of 127.64624811 KMD to the new unused address: RSbGKhhcprBQTdtNYAFrckf3FzfKwZqCe9
There will also be a 5% service fee of 0.12966221 KMD to: RQzv9tVzCHXN9j3kF5qNzms555zzLC9HQF

Connect and unlock your Ledger, then open the Komodo app on your device.
Confirm the address on your device matches the new unused address shown above.
Approve the transaction on your device after carefully checking the values and addresses match those shown above.
Broadcasting the reward claim transaction to the network.
Error
Ledger device: Invalid parameter received (0x6b00)

Maybe make this a paid service again

It seems that updates on the Nano firmware (or Komodo app ?) can break this claim tool.
Since i am losing money if this tool does not work, i would rather pay a small percentage when claiming if that would ensure regular/quick updates.
Just my 2 cents. I don't want tot go back to a software wallet after the fiasco with Agama wallet last year.

Ledger device: Internal error, please report (0x6f02)

Fully updated firmware + Komodo app on Ledger Blue

follow all steps fine until: Approve the transaction on your device after carefully checking the values and addresses match those shown above.

Which flashes red and gives the following error: Ledger device: Internal error, please report (0x6f02)

Unsure what to do from here, please advise.

Trying to claim rewards No compatible devices found after ledger firmware update.

I have been trying to check and/or claim rewards and after many infinite spinning wheels during the validation of firmware and Komodo hardware, I thought I would disconnect and reconnect the ledger device (Nano X) - now it will not recognize the device at all - the pop up box says: pbca26.github.io wants to connect "No compatible devices found." Any help would be appreciated, I am using Chrome, which I'm sure has had an update since I last checked as well.

Unable to redeem rewards - Ledger

I'm on the most recent versions 1.3.17, Nano S firmware version 1.6 (and this is when it stopped working).
I've tried with Chrome and Brave browsers, can't get it to move beyond step 3. Error is:

Failed to sign with Ledger device: U2F Device_ineligible.

Many thanks for any help.

error message

I receive an error message

image
Please tell me what I have to do to make this work.

User feedback on the service fee

You can read about why there is a 5% fee here.

Feel free to give us feedback and let us know how you feel about these fees.

You can click to vote on the poll below:



User feedback on output address

You can read about why funds are sent back to a new address here.

Discussion leading to the decision of the current behaviour with Komodo lead developer @jl777:
https://discordapp.com/channels/412898016371015680/502811530002300939/517482251324358662

Click to open

lukechilds - 29/11/2018
by the way, how do you think is the best way to group the UTXOs to claim interest from a Ledger Live acount?
They use BIP44
not sure how familiar you are with it
but it has the concept of accounts
and inside an account you have a new address derived for each recieving TX and a new address derived for each change TX
if you make a payment larger than a single UTXO for one of your addresses it will combine UTXOs together from any addresses in that account
but it will never combine UTXOs from seperate accounts to preserve anonymity between accounts
the way that makes the most sense to me would be to allow users to claim rewards per account
claiming on an account wil combine all UTXOs from all addresses in that account (received and change) into a single transaction and send to a new unused address from that account with interest
this will consolidate all UTXOs/addresses in the account to a single UTXO
the pros are:

  • It's only a single TX that has to be manually approved by the user on the Ledger
  • We can sweep all UTXOs, including one's that don't have nLockTime set (like change UTXOs in Ledger), meaning they will now start acruing interest in the new UTXO
    So the end result is you have your entire balance in a single new unused address all now acruing interest (even the UTXOs that weren't acruing interest before)
    the cons are:
  • This is bad for privacy, it clearly links all your addresses within that account together in a single TX
    However only for that account, other accounts would have their own TX
    It seems like maybe the privacy issue isn't a huge issue in the Komodo community as public addresses aren't that private anyway, and can already be linked with chain analysis. This would just make it easier. If Komodo users want privacy they use Z addresses.

It also seems like it's quite common in the Komodo community (encouraged by Agama, BarterDEX) to just have a single address that is re-used for incoming/change transactions and then use a Z address for privacy. Reusing a single address for everything has even less rpivacy than using seperate BIP44 addresses and occasionally consolidating them.
That's just my assumption, so correct me if I'm wrong. But it seems like if that is the case, then combining UTXOs from different addresses in the same BIP44 account shouldn't be a big deal.
I've already spoken to Komodo Ledger users who have said they use multiple BIP44 accounts in Ledger to seperate their funds properly. This is issue won't affect them. They will have a seperate reward claim transaction for each BIP44 account consolidating only the UTXOs inside those account.
If this is an issue, the alternative would be to create a seperate reward clam transaction per address. So every address in every account get's it's own claim TX.
the pros are:

  • preserves anonymity slighly, all account UTXOs aren't consolidated into a single transaction, it was one TX for 1 address
    the cons are:
  • requires a seperate TX per address. This is quite a huge pain for the user. Each TX need to be signed on the Ledger device, which is slow, and manually approved by clicking buttons on the Ledger. If they have been using the account for a long time it could have hundreds of UTXOs. This would involve manually verifying and physically clicking the button on the device hundreds of times.
  • it isn't actually that much more private than my previous proposal. All addresses in the accounts will probably be claimed very close together and would quite likely make it into the same block. So although they aren't linked in the same TX, it would be quite obvious if you see a block with a large amount of reward claims going from one address to another in the same block that they are all from the same person.
    I'm leaning towards the first implementation, one TX for all account UTXOs. It's not as private as the second option but clear addresses aren't private anyway. Someone can already follow your chain of TXs with chain analysis if they want to, this just makes it a bit more obvious. If users want real privacy, they should use a Z address.

@jl777c what do you think?

jl777c - 29/11/2018
I agree with you. a simpler implementation will be more reliable and anybody that believes they have privacy without zaddr is just kidding themselves
as long as the funds separation is retained for the different accounts, that seems to be a non-privacy related issue, whatever solution seems fine


Currently all UTXOs in a single account are consolidated and sent back to the next unused address in the reward claim transaction.

We don't see an issue with this but might be open to changing this if it's a problem for a lot of users.

You can click to vote on the poll below:



Firefox support

It can be added on the Wiki:

  1. Type "about:config" (without quotes) into the Firefox address bar and press Enter
  2. Search for “u2f”
  3. Double-click on security.webauth.u2f to enable U2F

Ledger KMD Reward Claim

I used to claim the 5% reward by my Ledger. But now suddenly it doesn't work anymore. Everything is up-to-date. Specs: Windows 10 Home, 64-bits. I tried different browsers: Chrome, Wave and Opera. All the same issue: failed to make connection.
But now I tried an Apple with Opera and that works ok.
Does anyone know which settings I should use with Windows 10 to make it function again?
Ledger KMD-1
Ledger KMD

Locktime

What does Locktime mean?
screen shot 2019-02-19 at 14 04 40 pm

Why I have a red badge?

KMD Reward claims

Hello there, I have exercised couple times already hard time claiming my KMD rewards, I have my KMD on my ledger nano X and usually I used to use this website https://dexstats.info/rewards.php?address=RF4jGWEheWmhsxBpjbqB81pYjc6jw7gTFq then last couple of months I had an issue with it and I have switched into Magnum wallet now they are temporarily suspended, I found this website https://atomiclabs.github.io/ledger-kmd-reward-claim/ and now when I connect my ledger device and open my KMD app on it and press "check rewards" I approve the path then approve the address then export the first public key after that
"Connect and unlock your Ledger, then open the Komodo app on your device." shows checked (green checked mark on right side) but after that there are some other keys also should ask me to export to be able in this step "Approve all public key export requests on your device. There will be multiple requests" but it doesn't and after a while it gives error "Failed to fetch" and my ledger device and KMD app on it all up to date
Thank you for your help , my rewords stopped because it passed 30 days and it doesn't accumulate before I withdraw my rewards.
Please help me to fix this issue
Thank you in advance
Sincerely
Tony

Error NetworkError when attempting to fetch resource

I have used your website many times before, never had any issues with claiming rewards - actually worked wonderful. Thank you for that!
Since the last Ledger Nano S update (1.55 -> 1.6), I get the same error message in all the browsers (chromium, brave, firefox, vivaldi). Also using latest App version: 1.3.16
Error NetworkError when attempting to fetch resource
This error is displayed, right after the first public key export request.
kmd_claim

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.