How to setup your own node in a blink of an eye (Now support multi-nodes per host)

[Jared]

@Linnovations

So if I hear you correct, I do not need to stop any docker processes nor do I need to run the “uninstall” command.

Yes, this is correct. The script will automatically stop your containers prior to checking for new ones so you don’t need to stop them yourself.

@Linnovations

Let’s say I want to decommission one of my vNodes, is the reverse true - I.E.
All I need to do is remove the vNode Validator Key from the script and then re-run the script?

That is correct. However, you will need to stop the container of that node and delete the data. Then remove the key from the script and re-run it.

[fredlee]

@Linnovations

I believe we no longer have to open any ports on my firewall, right?

You still have to open the RPC port to be able to add the node to your incognito app and stake. Not sure if the incoming mainnet port is also needed for validators or just full nodes? Maybe someone else can answer that?

@Linnovations

Is there a way to retain the “/mainnet/block/” beacon and shard chains to reduce the amount of bandwidth and time needed to re-sync my previously active vNode or is this not advisable/possible?

I’ve done a lot of experimenting with data sharing between nodes. Every node will create its unique data. You can however copy a node and change the validator keys and continue running, which means that “bootstrapping” is possible.

If your previous vNode is working as intended, you can copy all data to your new nodes.

[GGolov]

Thanks for the guide and the script. Although, I’ve got some questions.

I’m trying to set up my very first virtual node. May I only know what value I have to type for VALIDATOR_K? It seems to me that it should be an alphanumeric string of some sort that I can retrieve somewhere.

Do I have to also run it as a full node to take rewards?

Do I have to change the INDEXER_ACCESS_TOKEN generating an hash from a random string?

Thanks in advance.

[Jared]

Hello @GGolov

@GGolov

I’m trying to set up my very first virtual node. May I only know what value I have to type for VALIDATOR_K ? It seems to me that it should be an alphanumeric string of some sort that I can retrieve somewhere.

Yes, you will need a validator key in order to run your vNode. This key can be found in your app under the wallet you plan on using for your vNode. Select Keychain from the home screen of the app. Next tap the key icon on the wallet you’d like to use. Here you will find the validator key (you can copy with the far right button).

@GGolov

Do I have to also run it as a full node to take rewards?

No, a full node is not a validator and will not earn you rewards.

@GGolov

Do I have to change the INDEXER_ACCESS_TOKEN generating an hash from a random string?

See below:

@Rocky

INDEXER_ACCESS_TOKEN does not need to be changed but it should be changed.
It helps prevent unauthorized access to the coin indexer on your node, which can cause the node to use up all the computing power (when the RPC “ authorizedsubmitkey ” is called) for indexing coins instead of doing its main job (block verification, inserting to the chain…).
You can find more about coin indexing here: Full-nodes’ Cache - A Faster Way to Retrieve Users’ Output Coins

Please keep in mind that vNodes require 1750 PRV to be staked. Once you have acquired 1750 PRV simply transfer it to the wallet in the app you plan on using for your vNode.

While these instructions are outdated the steps to follow are not. Please read over this article to get an understanding of how setting up a vNode works.

How to host a Virtual Node (out dated)

Edit (Sept 1 2021): The steps to setup below is outdated, Please try new method to setup validator here Did you know that you can run a virtual Node on your computer, or on a cloud instance? Below, you’ll find the instructions to hosting a vNode so you can join the Incognito Network and start earning crypto! Block rewards are paid out in PRV and transacted currencies, such as pBTC, pETH, pBNB and more. Step 1: Set up your server

Click to expand explanation

You can run Incognito on a low-cost s…

[fredlee]

I can’t seem to get the indexer working. When accessing the RPC I get the error

-13001: -13001: enhanced caching not supported by this node configuration

Looking at the run_incognito.sh file inside the container it says

--numindexerworkers=0 --indexeraccesstoken=$INDEXER_ACCESS_TOKEN 

Which means that it is always disabled?

[Jared]

@daniel

From flag

Add the following flags to the command (remember to add the indexeraccesstoken flag if you want to run the cache with the enhanced mode).

• usecoindata : if this flag is present, the node will operate with cache.
• coindatapre : the folder prefix in which the cache is stored.
• numindexerworkers : the number of workers for the cache. If this number is 0, the full-node’s cache will ONLY operate in BASIC mode. Otherwise, it has an enhanced cache layer with numindexerworkers workers running in the background.
• indexeraccesstoken : a 64-character long hex string.
• Example command:

./incognito --usecoindata --coindatapre="__coins__" --numindexerworkers=100 --indexeraccesstoken="0c3d46946bbf99c8213dd7f6

In this example they set --numindexerworkers=100

When --numindexerworkers is set to 0 it will operate in basic mode only.

Read more here:

Full-nodes' Cache - A Faster Way to Retrieve Users' Output Coins

Introduction to Privacy V2 ▸ Problem Statement In the previous post about Privacy V2, we have spotted the improvements of Privacy V2, explained Incognito keys, introduced a new key, and explained how the public key of an output coin V2 is different from that of an output coin V1. This difference leads to the impossibility to retrieve a user’s output coins in the old fashion. In Privacy V1, all of a user’s output coins have the same public key, which is also the user’s public key. A full-node da…

[fredlee]

Thank you, yes I saw that setting 0 workers would disable the enhanced mode. But how do I do this with the docker container and the scripts from this thread? Does it require an updated docker image where run_incognito.sh reads the environment variable? Or is there something I can do?

[Jared]

Change this part of Rocky’s install script.

@Rocky

New parameters since privacy v2 INDEXER_ACCESS_TOKEN=“edeaaff3f1774ad2888673770c6d64097e391bc362d7d6fb34982ddf0efd18cb” # can be generate by running: $ echo “bla bla bla” | sha256sum NUM_INDEXER_WORKERS=100

After you have changed those two lines just rerun your setup/install script.

If this doesn’t work let me know.

[fredlee]

Nah, Rocky’s script passes on options by using environment variables when starting the docker container (-e flags). These are then read and used by the run_incognito.sh script inside the container. The problem is that in my docker container, the NUM_INDEXER_WORKERS and ENABLE_COIN_INDEXER are not used for anything.

As you can see here https://github.com/incognitochain/incognito-chain/blob/875cd37644bffc3583b39a47583968d4dce20b34/run_incognito.sh#L53 --numindexerworkers is hardcoded to 0

[Jared]

Ah, I see the issue now. I escalated this with the devs and they are having the code changed. This was changed prior and never changed back. Please note to use this environment variable you will have to be running a fullnode.

[andrey]

Hey guys @Rocky @Jared, if I have two vNodes on one server, and one of them with status latest and the second with status stall.

Should I restart the second one? If so can I do it separately, or do I have to restart both (they both are on the same server)?

[Jared]

Hello @andrey,

I have a handy guide for vNode operators helping with troubleshooting:

Official vNode Troubleshooting Guide

It’s finally here! The official vNode troubleshooting guide. No longer do you have to search around the forum for answers to your questions. Use the Node Monitor to check for issues (monitor.incognito.org). When you see an issue come here to fix it. This guide assumes you have followed the official installation/setup method for your vNode(s) which can be found here: How to setup your own node in a blink of an eye (Now support multi-nodes per host) If an alternative installation/setup m…

I would first try to restarting that stalled node with:

docker container stop inc_mainnet_#

(replace the # with the problematic node number. check docker ps for this)

To start just this node use:

docker container start inc_mainnet_#

(again change the # to your node number)

If restarting does not work follow the troubleshooting guide to stop the node. Delete stalled data (shard or beacon) and then restart the node.

[JG20]

@andrey!!!

[andrey]

Thanks @Jared, gonna try tonight )

@JG20

[Mike_Wagner]

[GGolov]

Alright, thanks for the reply.

I’ve changed everything accordingly and waited for my 1750 PRVs to be withdrawn from the Provide. They are in my wallet now.

Now I’m the step 6 (Adding your node) of the guide How to host a Virtual Node (out dated)

I’ve added the node with the IP of the server + “:9433” but it shows that the node is not active, that I have to import a keychain and the name of the node in the list is only a dash. I’ve tried to import a keychain but it fairly states that it has already been imported into the app. I have no option to stake and pass to step 7.

I checked at https://monitor.incognito.org/node-monitor and the node is online with only the Beacon synced at the current block height (and still syncing) meanwhile it is blocked at block 1 for the 8 shards and it is not syncing; it also has, rightly, no stake.

What am I doing wrong?

[Jared]

@GGolov

I’ve added the node with the IP of the server + “:9433”

It’s the other port (RPC) you’re trying to add the node port.

[GGolov]

Oh, now I get it. Thanks a lot. Now it is stakable.

[abduraman]

Hey @Support,

To avoid the risks of Ethereum full-node centralization (i.e. infura), is it possible to use our own Ethereum full-nodes?

For example, I’m a StrongBlock (provides single-click Ethereum fullnode setup) operator and have multiple Ethereum full-nodes which are ready to use with their RPC and WSS endpoints.

Thanks.

[daniel]

Hi @abduraman,

I think you just need to change the GETH_NAME into your RPC fullnode URL then all is well.