Documentation bug - https://docs.bluzelle.com/

[dffffffff]

How to reproduce

Go to https://docs.bluzelle.com/developers/staking/validator Click OS Setup for Curium, land on https://github.com/bluzelle/curium/blob/devel/setup/os.md Click next, land on https://github.com/bluzelle/curium/blob/devel/setup/devenv.md Click next, land on https://github.com/bluzelle/curium/blob/devel/setup/build.md Click next, land on https://github.com/bluzelle/curium/blob/devel/setup/deploy.md - Expected result is to land on https://github.com/bluzelle/curium/blob/devel/public-validator-+-sentry/buildvalidatorsentry.md

[dranastos]

I can confirm that this is an issue.

Followed the documentation all the way through ans then get an error at step 9

"blzd add-genesis-account $(blzcli keys show vuser -a) 500000000000000ubnt"

Gives the following error:

While parsing config ( 79,10) keys cannot contain new lines

[njmurarka]

The fact of the matter is, the bug listed here is pretty legitimate. It is not clear which way to go to deploy a node on one of our existing networks vs deploying your own private chain. The steps that @dranastos was following was for the latter, not the former, which I suspect was the intention. Noted and will resolve.

Thanks.