Buy crypto anonymously on the Incognito pDEX   

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

#35

My bad, will include curl right now

2 Likes
#37

Can one infura API be used for multiple nodes?

#38

Yes, I use one API key for more than one node.

2 Likes
#39

One Infura with free plan supports 100,000 Requests/Day. So yeah, you can use one Infura for more than one.

1 Like
#40

After using the new script “sudo ./inc_node_installer.sh”, I see only “inc_mainnet” running after sudo docker ps. I no longer see “eth_mainnet” running in docker after using the new script. Is this correct? Can someone share a correct return value for “sudo docker ps” after running the ./inc_node_installer.sh script?

1 Like
#41

hello! Eth_mainnet The command incognito does not use) infura)

  • On Setting tab of project, copy the mainnet endpoint api key
    image
    Eg. Copy this string be5fe1410b024a8f94f62fbc106439xx
    [/quote]
    How to host a Virtual Node
#42

We no longer use eth_mainnet docker image. We use Infura instead.

#43

If only inc_mainnet is running and no settings for infura are included in the script, what functionality is lost regarding incognito? My nodes appear to be functioning normally.

#44

Please check the post again, I believe there’s a reference to Infura setup guide already.

#45

Sorry, I see the post now and have setup infura and restarted the node. One last question regarding infura: in what ways can I test or check that the infura connection to eth network is working?

#46

@Socrates, let your node sync data and validate transaction for a while (few days i think) then check setting on infura to see if there is any query
mine, for example
image

1 Like
#47

Just for clarification for the community.

The eth-mainnet docker container can be killed and we should be running infura now, correct? I had been running both.

Is there anything other than adding our infura api key that we need to do to insure not having our nodes slashed?

#48

Yes, you just need Infura only.

There are many things that can cause the node to be slashed. We will have to take a look at the log to find the cause. If your node is slashed, feel free to contact us we can help investigate.

#49

Prior to slashing taking affect can we have an indepth post about it. For instance, common reasons for slashing and how to prevent each reason.

#50

Yes, we will do that, thanks for the tip.

1 Like
#51

Hey guys,
I’ve just update the script and this guide to support running multiple node per host.
Please check it out!

4 Likes
#52

Thank you so much! It’s great to see an official script for running multiple nodes!!

Do we need to change either of the following?

#53

NUM_INDEXER_WORKERS can be left un-change.

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

3 Likes
#54

Does validator nodes use the indexer at all? When I first read it I thought it was only for full-nodes to cache user coin balance for transaction creation? But I’m a bit confused about the v2 details so far, so I might be wrong. :relaxed:

#55

Yes, the coin indexer is only used for caching coins, it can be disabled if you have no desire to query balance or create transactions on your node.
I will add an option to the setup script allowing disable/enable the cache later.

1 Like