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

Issue setting up a node to run on testnet #342

Closed
sam0x17 opened this issue Apr 18, 2024 · 6 comments · Fixed by #358
Closed

Issue setting up a node to run on testnet #342

sam0x17 opened this issue Apr 18, 2024 · 6 comments · Fixed by #358
Assignees
Labels
blue team defensive programming, CI, etc testnet-skip This PR will skip testing on testnet

Comments

@sam0x17
Copy link
Contributor

sam0x17 commented Apr 18, 2024

Copied from @rajkaramchedu:

  1. I believe running subtensor node for mainnet is okay, no complaints there.
  2. But whenever a user wants to run the node on testnet, for some reason it keeps going to mainnet, is what they are saying.
  3. It may be as simple as one of the nucleus team members to look at testchain command syntax for both "using source" and "using docker" sections of the doc and help identify what's wrong with those command options. Maybe the bootnode public key is wrong for the testnet? https://docs.bittensor.com/subtensor-nodes/using-source#lite-node-on-testchain
    [3:51 PM]
    Latest issue the user is facing is from a few mins ago https://discord.com/channels/799672011265015819/1228380578949369947/1230596951381119079. This is all familiar, we've been getting these questions since almost 2+ weeks ago.
    [3:53 PM]
    This issue resolution alone will reduce a good number of subtensor node related questions in the community.
    Doc Issue on this Write subtensor installation docs developer-docs#188
@sam0x17 sam0x17 added the blue team defensive programming, CI, etc label Apr 18, 2024
@open-junius open-junius self-assigned this Apr 19, 2024
@rajkaramchedu
Copy link
Contributor

One user gave up on testnet and went directly to mainnet due to this issue. Linking Discord message just as fyi. https://discord.com/channels/799672011265015819/1228380578949369947/1231302939797229660

@rajkaramchedu
Copy link
Contributor

@open-junius
Copy link
Contributor

The root cause is the spec and bootnode in the doc is wrong.

  1. for testnet, we should use the raw_testspec.json or raw_spec_testfinney.json
  2. the bootnode in the cli for testnet is the same on with mainnet, except with the dns prefix.

we need update the doc.

@rajkaramchedu
Copy link
Contributor

So @open-junius in https://docs.bittensor.com/subtensor-nodes/using-source#lite-node-on-testchain section and for archive node also all I have to do is to fix the "--chain raw_spec.json" to one of the two you mentioned, correct? The boot node for the testchain in these two cases, lite and archive, looks correct to you?

Also has anyone run the node with testchain settings you said and confirmed it works? I am on mobile now so can't run it now. Thanks!

@open-junius
Copy link
Contributor

the bootnode for lite and archive should be the same for testnet. I will ask team to get a correct bootnode in testnet. then will try it by self.

@open-junius
Copy link
Contributor

/dns/bootnode.test.finney.opentensor.ai/tcp/30333/p2p/12D3KooWPM4mLcKJGtyVtkggqdG84zWrd7Rij6PGQDoijh1X86Vr is the correct boot node. And from our docker-compose.yml file, we can find out the correct spec as well. just need to update the doc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blue team defensive programming, CI, etc testnet-skip This PR will skip testing on testnet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants