Consistency...

[HankFit247]

For consistency sake, kindly add -n under Prepare Chainflip
echo -n "YOUR_PRIVATE_ETH_KEY" > ~/chainflip/config/ethereum_key

If I come across any other 'potential' issues, I'll post here in this thread, as I try to spin up this node.

Better yet, I'm a complete NOOB to Docker...

[CumpsD]

thanks for your feedback, edited in 78bdc7b

Let me know how it goes :)

[HankFit247]

Install was SIMPLE and Effortless. Now comes the fun PARTS...

I already have an active Validator, so I want to make this my
2nd Node.

So I know I need to update my "keys" file.

I could simply STOP the Services, and Edit the "keys" file, with the contents of
$ sudo ./subkey inspect "Secret Phrase"

Is this data captured or homed anywhere else that would need to be updated, say Docker?

[CumpsD]

@HankFit247 no, that's pretty much it.

These are the keys that count:

cat config/node_key
cat config/signing_key
cat config/ethereum_key

This one is just for your validator id and readability:

cat config/keys

That being said. I don't know what will happen if you use the same values from your 1st node on this one...

It might make more sense to have it fully separately? Basically follow the guide and add it as a second node?

[HankFit247]

Not an issue, but rather instructions for those that might follow....

If moving from a previous Active Validator.....
ethereum_key_file remains the same, as you are using the same MetaMask wallet.

List Containers:
docker container ls
(there should be three: chainflip-engine, chainflip-node and chainflip-geth)

sudo systemctl stop docker.socket

Remove Containers:
docker rm CONTAINER ID
replace <>

If you have a copy of "signing_key_file", then simply edit config/keys.
This was created during the command $ ./subkey generate
If you do not have a copy of "signing_key_file", but know your Secret Phrase, use:
$ sudo ./subkey inspect "Insert Secret Phrase" to view the original contents.