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

1.3.0 pool bug #10610

Closed
OMeliante opened this issue Mar 8, 2022 · 17 comments
Closed

1.3.0 pool bug #10610

OMeliante opened this issue Mar 8, 2022 · 17 comments

Comments

@OMeliante
Copy link

Updated to 1.3.0. I have 4 different NFT on the same wallet. All of tem was mining at space pool. After app update, all nft returned to mine at the first pool they were inserted. And I try to change pool and the pool does not change. It is stuck with the first pool they were created.

@Panteraldo
Copy link

same here

@nmurray67
Copy link

Same here, but... after copying back the old config.yaml file (no restart required), pooling resumed properly.

@mariano54
Copy link
Contributor

What operating system are you using, and what chia version were you using before?

@mariano54
Copy link
Contributor

If possible can you send me your config file to me on keybase (sorgente711)?

@Muslix
Copy link

Muslix commented Mar 9, 2022

Rename the Appdata/roaming/chia blockchain file and try to install the chia 1.3.0 update again. it should work after that . maybe u have to delete the wallet db as well.

@OMeliante
Copy link
Author

If possible can you send me your config file to me on keybase (sorgente711)?

Already uninstalled 1.3.0 and running 1.2.11...

@OMeliante
Copy link
Author

Rename the Appdata/roaming/chia blockchain file and try to install the chia 1.3.0 update again. it should work after that . maybe u have to delete the wallet db as well.

Already uninstalled 1.3.0. Running 1.2.11 and will wait for a new app version

@mariano54
Copy link
Contributor

If anyone is experiencing this issue, can you please send me your config.yaml and debug.log? It would really help us to solve this faster and make a new release with the fix.

Sorry for the issues.

@Muslix
Copy link

Muslix commented Mar 9, 2022

i think this problem is because of some cache folders in the roaming/chia blockchain folder. i tried some stuff and just after deleting(renamed) this one it all worked again.

@advlive
Copy link

advlive commented Mar 9, 2022

I was install 1.3 then I done upgrade but pool show like self pool but up mention name of pool!!!!
so many try change config file then tired and downgrade to 1.2.11 but always start make db file from 0 and interesting from v2. so many problem in this version
most issue is all CAT tokens you have to add your self then show number of token!! and if I have some Cat but I don't know about that means need forget it

@mariano54
Copy link
Contributor

mariano54 commented Mar 9, 2022

I think this should be fixed by: #10631
Download: https://github.com/Chia-Network/chia-blockchain/actions/runs/1959674376
Note: you will need to delete the wallet DB and start again.

@advlive
Copy link

advlive commented Mar 10, 2022

actually I find problem for not showing pool correct or show address pool but same time show as self pool
all because in config file authentication_public_key: show address without 0x and only xchpool can understand for others need add 0x at firt of address
also some pools remove name in pool_url:
and this also need add manually

@mariano54
Copy link
Contributor

@advlive are you on version 1.2.11? Version 1.3 should not use authentication_public_key anymore.

@OMeliante
Copy link
Author

I think when you download a Windows app, it should come ready to use, not needing to put something manually. I recomend use 1.2.11 until this 1.3.0 problem ( unexisted on other versions) is solved

@advlive
Copy link

advlive commented Mar 10, 2022

@advlive are you on version 1.2.11? Version 1.3 should not use authentication_public_key anymore.

All issue happened in 1.3 new version also a lot more on wallet as can not show what CAT token you have ,need to add manually asset ID. and story become nice when you don't know in which token you have something

@nmurray67
Copy link

At least for me, this isn't #10631. I'm running the node on Ubuntu 21.10, and upgraded from 1.2.11.

@emlowe
Copy link
Contributor

emlowe commented Mar 10, 2022

Consolidating issues - marking duplicate of #10590

@emlowe emlowe closed this as completed Mar 10, 2022
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

No branches or pull requests

7 participants