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

docs: remove blockspace race testnet Celestia #4220

Closed
wants to merge 1 commit into from

Conversation

jcstein
Copy link
Contributor

@jcstein jcstein commented Mar 26, 2024

This PR removes an old testnet that is no longer live for Celestia. cc @Bidon15

@reversesigh
Copy link
Collaborator

reversesigh commented Mar 26, 2024

This is a good chance to actually fix up the testnet situation with celestia on here.

Instead of completely removing, I suggest:

The folder that is currently labeled testnets/celestiatestnet3 needs to be renamed testnets/celestiatestnet. Sidenote - I don't think Mocha was a fork of anything, but if it was then we'll add "pre_fork_chain_name": "celestiatestnet3". If it was a new launch with a new genesis and from block 1 then ignore adding that field.

I only joined Celestia during Mocha so i can't speak what was before, but if blockspace race was the testnet before mocha, then rename the blockspace race testnet folder to celestiatestnet3 and change the status to killed and change the chain_name to celestiatestnet3. Also delete the images folder for this.

@jcstein jcstein marked this pull request as draft March 28, 2024 21:16
@JeremyParish69
Copy link
Collaborator

I think it might be better to reassign the chain_ids for the celestia testnets in a separate PR (celestiatestnet3 -> celestiatestnet, and celestiatestnet -> celestiatestnet1)

@JeremyParish69
Copy link
Collaborator

PR has been abandoned.

@jcstein
Copy link
Contributor Author

jcstein commented May 30, 2024

will open a new PR for this

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

Successfully merging this pull request may close these issues.

None yet

4 participants