Issues with instructions

[njmurarka]

• Make new path including go permanent -- the instructions only make it temporary.
• Need to install git.
• The step "curiumd version --long" fails -- curiumd is not in the path!
• Why do you ask the user to build curiumd but also ask them to download the binaries? Isn't it either or?
• You state the version is v10.2 for the downloading binaries url but otherwise leave it to the user to decide that when cloning the repo. Not consistent.
• You suggest the user to add seed nodes. What seed nodes? Do we have any?
• Is the addrbook, if done, a replacement for persistent_peers???
• Quicksync's tarballs are wrong. They are resulting in a "home" folder in .curium. Please verify.
• Need much more information on how exactly to do StateSync. The instructions there do not explain clearly exactly how a node operator can find the right height and node hash. Please provide all this.

[njmurarka]

Also need to clearly indicate that block sync may not work if there have been software upgrades that change state machine behaviour.

Is there a way to know there were breaking upgrades?

[njmurarka]

#question: Why do you ask the user to build curiumd but also ask them to download the binaries? Isn't it either or? #answer: some users like building from source code and some want to download the pre-built binary. Providing two methods is a conventional.

I understand there are two options but you are clearly indicating they are mutually exclusive options. It might seem you need to do both?

[njmurarka]

Let's keep this instruction. Maybe some node operators would run this kind of seed node. :)

What's a seed node?

[njmurarka]

???

You state the version is v10.2 for the downloading binaries url but otherwise leave it to the user to decide that when cloning the repo. Not consistent.

???

[njmurarka]

Still not clear how to get the trust height and corresponding trust hash. These have to match right? The instructions need to SUPER CLEARLY say where to get this PAIR of matching values.