Ad I mentioned, I have v1.2.6, and don’t see those errors. It is possible, that some messages were enhanced, and v1.2.6 is ignoring that extra part (so I don’t see those). Or rather that they are running some A/B tests with some new features, and you ended up in the shitty group.
I have been having these errors since I installed the first Chia client that was pool ready and could plot NFTs. Multiple client upgrades have not changed a thing except that the error has become more common.
At first the error was rare but now it takes up most of my log.
While you are chatting with them, maybe you could ask them to put some “Errors FAQ” that would list the most common errors, and what are the best steps to fix those, or which can be ignored.
I have some errors in my logs, but those are just purge engineering garbage (e.g., Error in pooling: (1, ‘Requested signage point was reverted’)).
My take is that this is just dumb to have all of us separately ask for the same errors, and waste each other time, where they do basically shit to smooth the process.
So, maybe this is somehow related to the pool you belong to? Maybe you could reach out to that pool as well. Maybe they modified the pool code, and introduced this issue. I had one issue like that.
I have never joined any pool.
Just ran chia plotnft show and chia wallet show at dev request. I have 54 wallets! Wallet number one is “Standard Wallet”. The rest of the wallets are "Pooling Wallet"s. It looks as if every time I did an NFT parallel plot Chia created a new wallet for just those three plots (occasionally two as I filled end of HDD). They have not yet responded to my question if this is normal, lol.
That really sucks. Although, as only 2-3 plots belong to such mini-wallet, your “Estimated Time to Win” is like thousand years, but still possible to be lucky, though. Maybe you could just start consolidating those mini-pools, and dump those extra wallets. Or, I assume you use just one cold wallet on all those mini-pools.
Thankfully, I don’t have those problems. All my plots are K32, though, and all are MadMax generated (on few computers). Maybe that is a K33 or latest OG “feature?”
Sometimes, I am thinking that Chia Network signed a deal with energy providers, and are creative to have us replot from time to time for no reason, where they get some kickbacks. Of course, not true, but all the pain is on our side.
Yep. We have confirmed the problem.
I always used the Plot page to create plots. When NFTs came out I continued to do so. I did not want to join a pool so never hit the Join a Pool button on the Pool Page. I should have done this for my first NFT plot and then done the next step which I was unaware of to create my own pool. After that I should have always used the Pool page to create further NFTs, all in the same self-pool I first created.
By using the plot page I ended up creating a new pool and a new wallet every time I plotted. The Chia GUI limit for wallets is 20 and that is not recommended. I have 54 wallets.
Now after .bak and re-creating my config.yaml it does not create/include the required Pool_List heading or the wallet entries under it. I have broken my client by creating too many wallets.
Since updating config.yaml farmr tells me that I am not farming or harvesting at all and my log is almost all errors.
Wallets cannot be deleted and at this point, neither can the references to the wallets be removed from the Chia GUI. The dev I was chatting with said he hoped that there would be a way to do so soon.
At this point it appears that due to my lack of knowledge and a GUI that offers no explanations have led to my entire farm being useless.
Dev has suggest a possible re-plot out of the problem but not a too many wallet fix.
I think the only way I can have a Chia farm after this colossal screw up is to format the machine and all the plotting drives, install Chia and start from scratch with a new mnemonic. Over 70TiB of plots and plotting utterly wasted.
I think its time for bed. Today has been a complete bummer.
Thats some really bad news, sorry for your loss.
One thing to consider before replotting is to make sure you get it right.
This statement seems incorrect to my mind , so tread carefully.
Firstly, if you create an nft and don’t point it at a pool it’s automatically self pooling, so no need to create your own pool, it just does it as self pooling unless you then point that nft at a pool.
Secondly, creating further nft’s all in the same self pool you created seems wrong.
Each nft can self pool or pool depending on what you want.
There would be no point creating further nft unless you want to split your plots, so one nft self pooling, another at pool xyz.
I have OG plots and 1 nft that I plot to, as I won’t split my farming I have no need for more than one nft.
@Aspy68
Really sorry to hear that.
I would suggest to switch to MadMax, as that is an independent plotter, so will force you to provide correct data, and at the same time will not be able to screw up your Chia setup. You can run it on a box that doesn’t have Chia software installed, and that further protects you from making any mistakes.
@Bones
You are one of the most experienced people here, so we all look up to you, and hope that you will chime in when we are in trouble.
However, any, and I mean any decent software has two purposes: 1. provide some features, 2. protect the user from harming himself/herself. Any software that is using engineering logs, that are furthermore not easily recognized by the dev team that put them in a couple of months back, is just a joke.
We are all trying to help each other on this forum, where Chia Network is deflecting all shitstorms back to end users. Plus that is a company that got ~$60m investment just four months back (one engineer in Silicon Valley is about $200k/year), so not to hire people to beef up the UI, and still keep it in the alpha-engineering mode is just plain wrong.
Very kind of you, but to be honest I’m fairly new here, few months, but am a long time crypto enthusiast, there are alot here with far greater knowledge than I, but I try to help where I think I can.
As for the software, yes, it needs improvements, but the best tests are always in the wild.
Sure they could have held out on the release but it is what it is.
Yes. I should have said, “After that I should have always plotted to the first and only NFT.”
Not really, we are all learning, and not having help from the software to protect us from some “beginner” mistakes is the biggest issue for me. As that dev guy said, the max for those wallets should be 20, so why they let you get over 50, without screaming in those logs.
I re-installed my backed up config.yaml which did still have the Pool_List. I now have farmr saying I am farming again though with many errors and 300 or 335 plots being farmed depending on whether you believe farmr or Chia. Anywaze, one or two of my drives (35 plots per drive) are not being farmed as the plots are not found by the Chia GUI after I add the last two drives to the GUI. I may be farming and I have probably lost contact with 70 plots but I’m not out of the game, lol!
One step forward, two steps back …
I only want K33s which are not supported by madmax.
You’re right, the wallet shouldn’t have even allowed it.
But look at btc, unless it’s changed, certainly used to be the case.
The wallets could hold 100 sets of keys, and if you still had coins on add 1, then created add 101 the very first one could get dropped leaving you without access to your btc.
The wallet never came with a warning, ppl learnt from trial and error just as we are.
BTC was started as more or less volunteer based project, where Chia Net is sitting on that $60m investment, that would be one difference. The second is that you learn as you go, and I would apply that to Chia Net as well, i.e., learn that if your main UI are those engineering logs, your ecosystem hurts.
Currently, thanks to people like us, the real Chia Network worth is not really in those $70m investment money, but rather in the premine that they are sitting on. They can use bits of that to hire more people. Their HQ is here, in SF, so there is really no reason not to hire few extra guys that would be rather happy to work for them, and help us at the same time.
This is my big peeve. The complete lack of GUI guidance or any indication that I was using the wrong procedure really pisses me off. The inability to separate these wallets from the Chia GUI just makes it worse. I am far from computer illiterate and was completely blindsided by this.
Obviously, most peeps figured it out correctly, but the lack of guidance or instruction in the GUI has led many more than just I to make this error. I am now going to spend a lot of tomorrow answering the same question I found asked by many others while searching for my solution.
I’m really pissed at myself and at Chia.
No need to be. You did what was the best based on your knowledge, and what the UI let you do.
I really cannot comprehend, why that UI doesn’t have “The Issues” section, that would at least repeat in red all the errors that are in the log (a standard tail for the last 10-20 errors). At least, that would make more people ask some questions, as I bet not that many those smaller farmers are checking their logs.
To be honest I’m not sure what they can and can’t do with those coins.
I believe thet are to be used to get businesses on board without affecting the price negatively so as to hurt farmers.