How to host a Virtual Node

[khanhj]

For now Infura/eth-client required to verify blocks that have shield/unshield transaction.
We’re working on the upgrade that validator doesnt require eth-client anymore. Will keep u guys inform when this release.

[Jared]

@khanhj Will it affect node earnings or selection if we are not running eth_mainnet?

[khanhj]

Hi @Jared,

• Committee selection is totally random.
• Eth-client(parity) or Infura is required to validate new shard blocks

[doc]

@khanhj Just an FYI… based upon comments seen in this thread and others, I dont think everyone is running an Eth-clinet on their vNode… I dont really understand what the repercussion of this is, as I know I had vNode selected, part of committee for multiple epochs and it did not have the eth-client running.

I plan on adding it back now that you have stated it is needed, and provided the updated script for showing how to add it… but I am not sure wha this means for the chain, that we have several people running vNodes without an eth-client.

[Jared]

Fastest way to add eth_mainnet back to your server is to just rerun the script.

[doc]

The updated script @khanhj provided,

@khanhj

I personally prefer using Infura (a 3rd party service - free 100000 requests/day). As running eth-client docker will consume server power/resource.

Please check this file: run_3.sh for sample config

I am more curious about how this effects the overall chain, since there are apparently multiple people who did not think it was needed and @mesquka mutlinode script has the Eth client removed:

@mesquka

This script doesn’t start eth_mainnet, it did at some points in the past however.

[Jared]

@doc Ah, my mistake. I’m still using the old script and hadn’t checked to see if a new one was available.

[khanhj]

Hi @doc

I’ll check with CS team to update the official run.sh script. As i said before, when validate block that have shield/unshield (deposit/withdraw ETH/ERC20), the docker inc_mainnet will query data from eth-client, that why we need ETH Parity docker running (or query via Infura service)

The reason why your node could still earn without eth-client is that your node would have been in a shard that gave enough proper votes to commit a new block.

Here is a sample screenshot of testnet:

@Peter can you please check our official run.sh file?

[Peter]

The current official run.sh file is here: https://node.incognito.org/run.sh

[doc]

@Peter and @khanhj Just to be clear, I am sure the official file is fine, what I am referring to is the file that was created here, and is used by several people (which all have more than 1 vNode, so could be a substantial portion of the community validators), does not utilize the eth-mainnet.

@mesquka

This script doesn’t start eth_mainnet, it did at some points in the past however.

There seems to be confusion among community and incog team members (if you look at the responses in last few days to both threads), that didn’t think it was necessary anymore. It appears this is ok because Incog core team hold 2/3 of validator spots, but surely sounds like something you would want to point out to vNode owners, especially those running that script.

I assume its not really a huge issue until new shards and spots are opened up, and that has been pushed out to mid 2021, but IMHO it doesn’t sound great that possibly a large portion of the community run validators would be returning invalid results for shield/unshield transactions… Of course if the dev team is looking to remove the dependency before the new positions and shards are opened up, then its really moot.

Just trying to elevate an issue that could arise in future based upon confusion that has been seen and now cleared up.

[abduraman]

@khanhj

the docker inc_mainnet will query data from eth-client, that why we need ETH Parity docker running (or query via Infura service)

I have one eth_mainnet but more than one inc_mainnet in the same VPS machine. This is OK, isn’t it? @khanhj

[doc]

@abduraman that should be fine as long as they are both on the same virtual network when the dockers are created.

    --net inc_net

The script he provided below, shows only 1 eth_mainnet for multiple vNodes on same machine. But if they are not on the same virtual network (inc_net, in case of the new file), they will not be able to communicate.

@khanhj

Please check this file: run_3.sh for sample config

[Jamie]

@doc

There seems to be confusion among community and incog team members (if you look at the responses in last few days to both threads), that didn’t think it was necessary anymore.

When your initial question was posted, I contacted the devs and was told it wasn’t needed anymore. After that devs started to ventilate different opinions . Unfortunately that created confusion.

[3ncrypt3d]

Thanks for these instructions, @annie! I sync’ed my node from scratch in 4.5 hours and now I want to stake it, but the “Stake” button is missing in the Incognito app. Instead an “Import” button has replaced it. How do I stake my node?

[Jamie]

Import the private key of the account you are using the validator key of, running your Node.

[3ncrypt3d]

Thanks for the reply, @Jamie. When I try to do that I get the error “The account already exists on your device. Please try another.”

[Jamie]

I guess that means you are using the wrong validator key, or added the wrong Node ip address.

[3ncrypt3d]

Let me rephrase the question: Why can’t I stake my validator using the Anon keychain that was created when I opened the Incognito app for the first time?

[Jamie]

You can if you use the validator key of that account to start the Node. I am assuming we are talking virtual Node, not physical Node.

[DarwinXu]

Is there a minimum bandwidth requirement for the server configuration? Can a server run multiple vNODEs at the same time?