Node Runners - Frequently Asked Questions

NOTE: The node client isn’t released yet. Sign up to the newsletter and be the first one to test the radix node when it is released. LINK: https://radixdlt.typeform.com/to/TGOduF

Can I have several nodes/clients behind the same IP address?
Yes. You may have multiple nodes behind a single IP address but it doesn’t necessarily mean that you increase the chance of earning more rewards.

Do I require a static IP address to run a node?
Yes, you need a static IP address to run a node. In most cases, you will have to configure your router to port forward. A static IP address gives a fixed address to your computer on the local network at your business. Port forwarding is used by computers on the Internet to connect to a specific device on your internal network. To set up port forwarding, you must assign specific ports or a range of ports to a specific IP address.

How do I get one?
You may get a static IP address from your internet service provider or the easier option is to run the node on a VPS with a static IP like Digitalocean or Vultr. As the node runs in a docker container, it will be fairly easy to spin a radix node in minutes.

What are the minimum hardware requirements to run a node?
The current requirements are

  • 2 CPU cores
  • 8 GB memory
  • 256 GB disk

Is there a guide to set up a node?
A pre-release guide to help you get started with the node-client software is published.Click here to read. We will notify you when the node client is released.

Do you need Radix tokens to host a node?
No, you do not require tokens to host a node.

Is there a main net or testnet to test or run a node?
There’s a private testnet on https://explorer.radixdlt.com/, but no public testnet yet, there will be open developer alpha/beta in the near future.

Sign up to the Node Runner Newsletter and be the first one to test the radix node when it is released.
LINK: https://radixdlt.typeform.com/to/TGOduF

1 Like

When runner node mainnet?? Good job team Radix! :+1:

Hi Angad, please could you explain why several nodes behind the same IP will not necessarily increase rewards. I presume by extension to increase reward I would have to install more computers so how do you think that would pan out economically versus running multiple nodes on one computer since presumably I would have to secure multiple dedicated IP’s. plus more computers, albeit low end machines. Thanks.

Is the potential for rewards higher if we used higher performing computers than that which is cited such as quad cores, 64K Ram and ssd hard disks of minimum 1TB? Thanks

Hi There!

Node runner fees come from two sources:

  • Atom Fees
  • Network Subsidy

Please refer to the recently released Economic Whitepaper regarding these fees.

tl;dr: both fees take into account that you are running an active Origin Node.

We are still defining what “Origin Node” means. The properties we have defined thus far include:

  • publicly accessible (internet)
  • ability to send/receive atoms on behalf of a client

Current alphanet (testnet) is fee-less and only allows a single node per public IP address (over HTTPS port 443).
We are looking into supporting custom ports for betanet/mainnet but it has to align well with the (future) “Origin Node” definition and fees in question.

Hope this helps and sorry I cannot give more details than this at this point.

1 Like

Hi Zalan. Thanks for the info. I’d like to suggest that in addition to the custom ports, that it should be possible to run an “Origin Node” on a dynamic IP. This will allow the average person to run nodes from home rather than require them to spin up a hosted VM or purchase a static IP. You already have to be able to handle the case where a node goes down temporariliy. When a node reconnects it can advertise both its IP and port and if the IP/port has changed then that can be propogated to the other nodes and then to the clients when they need a transaction verified.

1 Like

Hi guys, I have launched my betanet emulator. But I see some strange logs from docker coming in:

Aug 01, 2019 11:30:56 AM com.stijndewitt.undertow.cors.Filter handleRequest

INFO: undertow-cors-filter: CORS headers NOT added for origin null

15:36:49,106 INFO: [network] v:251 - UDP RADIX://172.19.0.3:30000 ID:8d93b63f313728e0bb44e357afcf35ba - Banned for 3600 seconds due to Message from self
15:36:49,106 ERROR: [network] v:291 - UDP RADIX://172.19.0.3:30000 ID:8d93b63f313728e0bb44e357afcf35ba - Disconnected - Message from self

is that ok?

Hi @novy,

A couple of words from one of our core developers:

What is happening is that the node is trying to synchronise with itself, so the system makes a note of it. It really shouldn’t be logged at the ERROR level.

The general strategy we use when nodes send messages that are incorrect, but not dangerous, is to ban them for a shortish period of time. The ban means that we don’t process any future messages for the indicated time. That doesn’t stop nodes from sending more incorrect messages, but it will mean that we extend the ban if they do, and there will be more logs stating this.

Hope to have been clear,

Keep up the good work!