Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Overdue payments and incorrect backup key #12538

Closed
MatthewDLudwig opened this issue Jan 7, 2018 · 2 comments
Closed

Overdue payments and incorrect backup key #12538

MatthewDLudwig opened this issue Jan 7, 2018 · 2 comments
Labels
duplicate Issue has already been reported

Comments

@MatthewDLudwig
Copy link

I am the owner of a Brave wallet that has transitioned from the original BTC wallet as well as taken money from the UGP. Originally I was unable to take UGP or submit a payment, and upon checking my backup key saw it was incorrect. I backed up the wallet manually from my original code and I was then able to take from UGP but the payment was no longer available. The history showed no transaction and I was hoping to submit this month.

Currently my payment is overdue and my backup key is simply "a". If there's anything I can do to help the team with this issue before backing up, I would like to do what I failed to do last time. Also, if there's any way to still go through with my contribution rather than backing up and missing another month I would love to support the platform!

@MatthewDLudwig
Copy link
Author

For all current (and future) additional information:
Intel I5 CPU running Windows 10.

brave key broken

@bsclifton
Copy link
Member

@MatthewDLudwig there is a known issue with restore (which we have fixed in an upcoming release, captured with #11383)

Do you still have your keywords saved? If so, our next version should have this fixed. If not, do you have a backup of your ledger-state.json file?

I'll close this issue as a duplicate of #11383 but I'd love to help you work through this. Apologies that you ran into it ☹️

@bsclifton bsclifton added the duplicate Issue has already been reported label Jan 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate Issue has already been reported
Projects
None yet
Development

No branches or pull requests

2 participants