Upgrade instructions
This commit is contained in:
parent
a769694417
commit
d23a450223
20
README.md
20
README.md
|
@ -1,6 +1,8 @@
|
|||
# genki-4000
|
||||
# genki-4001
|
||||
|
||||
Interim community testnet before GoS resumes tomorrow.
|
||||
Interim community testnet before GoS resumes on Jan 3rd/4th. On Dec 28th, we are attempting a hard fork from block 50,000 of `genki-4000` as was passed in a governance proposal.
|
||||
|
||||
If this fails to produce a correct state, the plan is to iterate till we get it right.
|
||||
|
||||
The network will do a quick start, and everyone can join in later by creating a validator on the running the chain. There is NO disadvantage if you join later - after all, testnet tokens are worthless.
|
||||
|
||||
|
@ -13,6 +15,20 @@ The network will do a quick start, and everyone can join in later by creating a
|
|||
|
||||
## Getting started
|
||||
|
||||
### Upgrading from genki-4000
|
||||
|
||||
We are attempting a hard fork from `genki-4000` on December 28th.
|
||||
|
||||
if you were validating on `genki-4000`,
|
||||
|
||||
1. Halt your node.
|
||||
2. Consider backing up `$HOME/.gaiad/data`. This will make it possible to restart `genki-4000` if the hard fork state is invalid.
|
||||
3. Download the new genesis file from `https://raw.githubusercontent.com/certusone/genki-4000/master/genesis-final.json`
|
||||
4. `gaiad unsafe-reset-all`
|
||||
5. `gaiad start`
|
||||
|
||||
|
||||
|
||||
### Genesis collection
|
||||
|
||||
DONE
|
||||
|
|
Loading…
Reference in New Issue