Skip to content
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

Update category names #336

Open
FrederikBolding opened this issue Dec 14, 2023 · 6 comments · May be fixed by #318
Open

Update category names #336

FrederikBolding opened this issue Dec 14, 2023 · 6 comments · May be fixed by #318

Comments

@FrederikBolding
Copy link
Member

No description provided.

@Montoya Montoya linked a pull request Jan 9, 2024 that will close this issue
@BananaFoDavid
Copy link

@BananaFoDavid
Copy link

Ok

1 similar comment
@BananaFoDavid
Copy link

Ok

@ajeetd
Copy link

ajeetd commented Feb 11, 2025

@FrederikBolding still something to consider?

@FrederikBolding
Copy link
Member Author

Yep!

@BananaFoDavid
Copy link

Poorly trained, I would not be able to explain to anybody what I'm doing... Except for the fact it seems close to a resolution. I have been struggling with hash signatures and I did not begin the way that was suggested. I'm having adware issues and running out of memory in devices, bought another ledger as I'm seeing the scope of the recovery and I bought an external hard drive. I may have trapped some crypto in the first deployment of ledger hardware as I Found ledger live app in my hard drive that seemed to have a lot of storage used up I'm going to see how it is secured today as I could not accept
any more seemingly negative experiences with ledger.
Thanks for your time,
Dave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants