Skip to content

returning-user.md

Latest commit

 

History

History
49 lines (37 loc) · 1.39 KB

returning-user.md

File metadata and controls

49 lines (37 loc) · 1.39 KB
Raw

Quick Instructions for Returning User

Between launches, we will typically update a significant portion of the scripts.

This is a quick guide on how to get ready for the next launch as soon as possible.

Note: Skip parts that you know that are unnecessary for your scenario (for example, if you have already updated EOS.IO to the next tag, skip the "Update EOS" part)

Update EOS

cd /path/to/eos
git checkout dawn-v4.2.0
git submodule update --init --recursive
ex -sc '16i|set( CORE_SYMBOL_NAME "EOS" )' -cx CMakeLists.txt
git pull
./eosio_build.sh

Ghostbusters folder

First, cd into the Ghostbusters folder.

curl -sL https://raw.githubusercontent.com/HKEOS/Ghostbusters-Testnet/master/setup.sh | bash -

This updates all of your scripts but params.sh

rm params.sh
wget https://raw.githubusercontent.com/HKEOS/Ghostbusters-Testnet/master/params.sh
nano params.sh
# Fill in your information again
# Save
cat my-peer-info
# Check that your peer info is still correct

ghostbusters- folder

sudo rm -r ghostbusters-<account-name>
./installGhostbusters.sh
./publishPeerInfo.sh my-peer-info
./updatePeers

By completing these, you should have your node peered and ready to go again!

Wait until the team decides on a launch block before you run autolaunch.sh. Run updatePeers.sh regularly to add new members into the mesh.