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

[Bug] “ERROR Could not find authentication sk for pk” wallet Limit #15261

Open
easleycorey opened this issue May 11, 2023 · 5 comments
Open
Assignees
Labels
bug Something isn't working plotnft

Comments

@easleycorey
Copy link

easleycorey commented May 11, 2023

What happened?

My first 6months of plotting/farming was wasted because of a issue with a wallet limit and a bug or design flaw in the GUI back in that time.

I mentioned this is discord and my dissatisfaction and
"jde5011
justin_chia#4358"
Said I should start a thread on github to have it officially tracked down and make sure it is 100% addressed

In the gui if you batch create nft plots you created a new nft wallet each time, and after 20, you no longer can farm

now let me set a perspective

I started before 1 Eib and after not winning well beyond expected
I had to google everything thing that looked like an error in my log to learn from a 3rd party source that I had to many wallets and I couldn't ever win with those plots I already created. Netspace now at 36Eib

I didn't want to but I started over and walking on "egg shells" being very cautious , I have now won since then
However I'm at in impasse and need some clarity

At the time I was using the gui and thought It would be the safest, I have done things in cli before on new projects and that bypassed the gui and database which lead to issues , etc
Bleeding Edge vs risk and investment trumps all I guess and should have waited but this goes against chia wanting everyone on the newest version.
However netspace was huge and I was trying to be preemptive and be able to pool if netspace kept growing etc
It was released as a official release not bleeding edge.

To render everything on an account or key useless shouldn't be so easily screwed up.

This never got the attention it should have,
and has/is stopping me from investing significantly more in the project, on the chance something like this happens again when fundamentally chia is very sound otherwise and see it having a great chance at huge success.

Now in other ways chia team has seemed to have gone to great lengths to stop people from having to replot,
However this seems to be the first time they did have too even though they did everything they were suppose too and someone out there probably never realized they had this issue. It was all swept under everything else happening

"mariano54"
https://github.com/mariano54
OG thread
https://chiaforum.com/t/please-check-your-logs-for-error-could-not-find-authentication-sk-for-pk/13127
OG bug
#9857
#8550

Thank You,
Corey

Version

1.2.6

What platform are you using?

Windows

What ui mode are you using?

GUI

Relevant log output

No response

@easleycorey easleycorey added the bug Something isn't working label May 11, 2023
@MumfMeisterT
Copy link

Thank you for submitting this to us. We acknowledge and apologize that this issue caused headaches. We have tracked this and added to our future planning to resolve.

@github-actions
Copy link
Contributor

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

@github-actions github-actions bot added the stale-issue flagged as stale and will be closed in 7 days if not updated label May 26, 2023
@easleycorey
Copy link
Author

Any update or is this just going to stale out? Thank You

@github-actions github-actions bot removed the stale-issue flagged as stale and will be closed in 7 days if not updated label May 28, 2023
@emlowe
Copy link
Contributor

emlowe commented May 30, 2023

It's a glitch in the bot

@easleycorey
Copy link
Author

Any update on this? It probably isn't but with the hot wallet being used now , just checking if it would be a good time to help those very few screwed over by this issue. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working plotnft
Projects
None yet
Development

No branches or pull requests

4 participants