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] chia plotnft get_login_link generates wrong URL when farming to multiple pools #17768

Open
whosrdaddy opened this issue Mar 22, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@whosrdaddy
Copy link

whosrdaddy commented Mar 22, 2024

What happened?

I farm currently to 2 different pools, first wallet ID is connected to spacepool , second wallet ID is connected to spacefarmers .
When I execute chia plotnft get_login_link -l I get the correct link for spacefarmers, when I do the same for the first wallet (spacepool) I get an url for spacefarmers, not spacepool, it seems like it always generates the URL for the highest wallet ID, which is in my case spacefarmers. My workaround is to correct the wrongly generated url with the correct url but this is a bit annoying.
Second problem is that the link is not correct (observe the second / after https://xch.spacefarmers.io/

Version

2.1.4

What platform are you using?

Linux

What ui mode are you using?

CLI

Relevant log output

pc:~$ chia plotnft show
Wallet height: 5114136
Sync status: Synced
Wallet ID: 2
Current state: FARMING_TO_POOL
Current state from block height: 543474
Launcher ID: ...
Target address (not for plotting): ...
Number of plots: ...
Owner public key: ...
Pool contract address (use ONLY for plotting - do not send money to this address): ...
Current pool URL: https://eu1.pool.space
etc...

Wallet ID: 3
Current state: FARMING_TO_POOL
Current state from block height: 3526817
Launcher ID: ...
Target address (not for plotting): ...
Number of plots: ...
Owner public key: ...
Pool contract address (use ONLY for plotting - do not send money to this address): ...
Current pool URL: https://xch.spacefarmers.io/
etc...

pc:~$ chia plotnft get_login_link -l <launcher ID of wallet ID 2 (spacepool)>
https://xch.spacefarmers.io//login?launcher_id=<redacted>&authentication_token=...
^^
Incorrect, should be https://eu1.pool.space/...
pc:~$ chia plotnft get_login_link -l <launcher ID of wallet ID 3 (spacefarmers)>
https://xch.spacefarmers.io//login?launcher_id=<redacted>&authentication_token=...
@whosrdaddy whosrdaddy added the bug Something isn't working label Mar 22, 2024
@wjblanke
Copy link
Contributor

Hey adam, must be here somewhere. Not sure why the URL is not being correctly assigned.

https://github.com/Chia-Network/chia-blockchain/blame/main/chia/farmer/farmer.py#L722

@arvidn
Copy link
Contributor

arvidn commented Apr 25, 2024

@whosrdaddy in your config.yml there should be a section pool: and it should contain a section called pool_list:.

In your case, I would expect this list to have two items, each representing a pool. Each pool has a few fields, such as:

  • authentication_public_key
  • launcher_id
  • owner_public_key
  • p2_singleton_puzzle_hash
  • payout_instructions
  • pool_url
  • target_puzzle_hash

Do your pools appear to have the correct pool_url value associated with them?

@wjblanke
Copy link
Contributor

wjblanke commented May 1, 2024

Could you save a copy of your current config.yaml, and then delete it and resync your wallet? That will repopulate config.yaml and we can see if the old one was somehow corrupted/different.

@BrandtH22
Copy link
Contributor

Hey @aqk take note that with the new config you might need to repopulate a few other things also:

  • If your farmer also has plots you will need to add the plot directories, easiest way is via the GUI but this can be done in CLI or by directly editing the config file.

  • Any custom settings will need to be manually added back to the config (db location, peer information, etc)

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

No branches or pull requests

6 participants