-
Notifications
You must be signed in to change notification settings - Fork 167
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
Comments
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 |
The root cause is the spec and bootnode in the doc is wrong.
we need update the doc. |
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! |
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. |
/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 |
Copied from @rajkaramchedu:
[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
The text was updated successfully, but these errors were encountered: