-
Notifications
You must be signed in to change notification settings - Fork 380
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
Create a section for testnets and their purpose #1254
Comments
@jcstein Hi, i'd like to work on this. Could you provide more details on what is expected in this section? |
gm @Mackenzie-OO7 - I'm actually fairly certain it's covered as an overview in https://docs.celestia.org/nodes/participate, but maybe the pages for mainnet/arabica/mocha could use a review of whether they speak to the differences in the networks and their individual purposes. |
Alright, thank you for clarifying. Let me take a look at them. |
cc’ing @rootulp for a second set of eyes here. i think maybe we can edit existing pages, but curious what you think |
I think the content on https://docs.celestia.org/nodes/participate addresses this issue. Specifically:
and
|
agreed. i think we can close this issue, if anyone has reasons to reopen it, please do 😄 |
We should formalize the purpose of the main longer lived testnets by documenting them. We all have social consensus around mocha being the network that is as close to mainnet as possible, but I don't think we have a formalized role for arabica. It could be useful to document to users that they should use mocha for longer term tests, and use arabica for bleeding edge things such as UX changes.
cc @cmwaters @Bidon15
Discussions around the purpose of arabica are likely outside the scope this issue, however we should likely come to consensus over that before we can create docs and thus close this issue.
The text was updated successfully, but these errors were encountered: