#Setting up validator environment

15 messages · Page 1 of 1 (latest)

summer comet
#

Any idea what seems to be wrong here?

devout dragon
#

It’s not ready yet. Wait for announcements. We need to still freeze deposit co tract and generate genesis files.

summer comet
#

I see. Thanks

Any other guide for setting it up (node) or we need to wait till mainnet?

dire storm
#

there will be guides- but mainly for our own software (eg LUKSO CLI, network parameters) and no general setup guides for node environments. there are plenty of sources for that and we dont want to duplicate and maintain things that are out of our reach.

a good source for node setups can be found at docs.luksoverse.io (its a community driven project to gather guides about running a node or becoming validator)

hexed crest
#

I have the validator keys and deposit completed

#

will LUKSO CLI will be ready at the launch of the mainnnet?

dire storm
#

yes . it will be ready when we launch testnet as well. so you have enough time to experiment and test your node before mainnet

hexed crest
#

that is great. Validator deposit launchpad's documentation sends you to for instance the GETH documentation, such documentation points you to run an ethereum node

#

so it's a bit confusing

#

so I will wait until further announcement, thank you

dire storm
#

yes, the CLI works with different clients under the hood, namely geth, prysm, erigon and lighthouse. for now

we're are pointing operators to those pages, as the CLI has the same requirements. With the CLI, you can pass any client commands to them directly- so validators should know how to tackle errors or issues that could come up. You can choose which execution client and which consensus client you want to run.

the term "Ethereum" here, does not come from the blockchain "Ethereum"- rather the Protocol "Ethereum" (EVM) we all use. So Ethereum Clients can basically be used for all L1 EVM chains like Gnosis, LUKSO, or the Ethereum blockchain themself.