likecoin/likecoin-chain:sheungwan-2image to support
halt-timeparameter for upgrade purpose.
.likeclifolder, or in mnemonic format,
.envfile to fill in the details, including chain parameters and custom parameters:
LIKECOIN_UID: normally keep it as
"1000"is fine, but if you are using root user under Linux (e.g. in some VPS) then you should change it to
LIKECOIN_MONIKER: any name you want to call your node. Will be displayed on validator list as the name of the validator.
Ctrl+Cat anytime, it won't stop the node operation.
<DESCRIPTION>: the content of the proposal, which should include some introduction to the upgrade, and also the following contents:
1for the first proposal).
vote "yes" in proposal ID 1.
.envfile and changing
LIKECOIN_HALT_TIMEto the Unix timestamp of the halt time in the proposal.
CMDcolumn. You should see the Unix timestamp you have just set in the
.envfile instead of
1233for different validators, then validators may use
1233as the height for exporting state.
<HEIGHT>is the height confirmed with other validators in the previous step.
priv_validator_key.json(consensus key) and
addrbook.json(address book) from
.liked/configinto the fotan node folder:
docker-compose.ymlfrom the new software:
.envfor the new chain:
LIKECOIN_CHAIN_ID: the new chain ID specified in the proposal.
"0"so that the new chain node can start up.
"genesis.json". The init script will detect that it is a local file and copy it from the migrated genesis file generated in the next step.
<ISCN_FEE_PER_BYTE>should be modified to the values specified in the upgrade proposal, and
<GENESIS_TIME>is determined in the previous step (format:
YYYY-MM-DDThh:mm:ssZ, in UTC).
.envfile, which won't be used since we will use the original key instead. If you are already a validator, you will probably never use the field again so this is fine, but you are free to delete this line.
app.toml, both are in
minimum-gas-pricesif needed, see the setting in your sheungwan node config
[api]section, if you need a local RESTful API server, then set
true, and also setup the corresponding port mapping in
[p2p]section, if you don't want to use the
--get-ipoption in the command parameter when starting the node for retrieving your externally accessible IP from third parties, then you need to enter your external address and port in
Skip key migration? [y/N]:,
not skipping, which is what we need.
keysfolders, so the credentials are not leaked.
docker-compose up -d.