Chia-Network / chia-blockchain

Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
Apache License 2.0
10.82k stars 2.03k forks source link

[Bug] Shadow pools that I never have added myself #9398

Closed andriitalkstech closed 2 years ago

andriitalkstech commented 2 years ago

What happened?

Pools list keeps showing me pools that I have never added myself.

I have tried to remove it from config.yaml but they keep popping up once in 2 runs. How do I delete/disable shadow pools forever? image

Version

1.2.11

What platform are you using?

Windows

What ui mode are you using?

GUI

Relevant log output

No response

loppefaaret commented 2 years ago

There was a dev build released based on main branch a little whole ago, that had a bugged wallet that caused these random plotNFT's to show up. it will cause you to have invalid data in a couple of places, that you need to manually clean out:


the heavy handed method to clean this out from your install: Close down Chia move out affected folders, ei. using PowerShell:

mv '~\AppData\Roaming\Chia Blockchain' ~\Desktop\
mv ~\.chia\mainnet\wallet\db\block* ~\Desktop\
mv ~\.chia\mainnet\config\config.yaml ~\Desktop\

This should have you ready to start up Chia again - having lost all settings, such as log level, UPNP, plot directories, and whatever else you had in config.yaml it will also wipe out any plotNFT's you had under the "Pools" tab it will also require your wallet to sync back up from 0 - and until it passes the last edit to your pooling plotNFT on the blockchain, it will not farm correctly!


Now if you want to "cheat" a bit here, some stuff you can do is:

Remember the cache data under ~\AppData\Roaming\Chia Blockchain needs to go as well.

github-actions[bot] commented 2 years ago

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[bot] commented 2 years ago

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.