Learn how to correctly set up X Core! It’s quick & easy

Start earning money by renting out the extra storage space of your machine! The set up is quick and easy, and you’ve only got to do it once.

X Core’s network selects nodes in which to allocate space, based on a series of variables. These include latency, Internet speed, bandwidth, uptime, and storage capacity, amongst others. Therefore, when getting files into your node, all these other variables are already being into consideration. That’s why we can very easily compute X Core payouts based on that single variable, allocated disk space. Each Host earns €0.01 per GB they host. Payouts are computed at the end of each natural month. We process the number of files held by a node at the end of a month, and send the payment, in Internxt tokens. Additionally, we encourage Hosts to hold the Internxt token payments they get every month. To do so, we added an extra 1% reward per 100 INXT tokens held per Host. You can easily estimate how much you can earn per month by using the calculator available in the X Core page on our site. There is a minimum payout of €2/mo per Host. If this minimum isn’t reached, no payout is sent to the Host. A Host is differentiated from another Host by its wallet address. One Host can run various nodes with the same wallet address, and all its space will be accumulated and counted as one payment.

Step 1. Download & Install the latest version of X Core. We will detect the OS you’re entering our website from and will automatically send you the correct version of the software.

Step 2. Insert your INXT Wallet address, choose where you’d like to store the encrypted shards of data of X Cloud users, allocate the desired storage capacity you want your node to provide. Finally, you need to insert your public IP in the IP Address field of the wizard, you can Google “what’s my IP” to find your public IP. If your IP is dynamic (one that periodically changes), you can use noip and enter your hostname instead. Click here to find out whether your public IP is static or dynamic.

Step 3. This is the single most important step. Most nodes that aren’t properly set up and don’t get data after 72h is because they didn’t follow this step correctly. It’s actually pretty straightforward, so let’s make sure you get it right! All communication in and to your node will go through a port in your router that you need to open. X Core will suggest which port to open (based on a quick scan on which ports can be opened and are available on your router). In this case (see the image below), it suggests us to use port 53396.

To open that port, you will need to access http://192.168.1.1/ with your browser in order to access your router configuration. In your router configuration, usually in the port forwarding section (may vary depending on which router you’re using), you can enter the port range you want to open (make sure the range includes the specific port you want to open). When entering the port number you want to open, you will also need to enter an IP. In this case, however, your IP isn’t that of Step 2 (where you entered your public IP address). In this step, you will need to gather your internal IP address instead. To find what your internal IP is, enter “ipconfig /all” in your Windows terminal. If you are on Linux or Mac, enter “ifconfig” instead. There, you will be able to find what your internal IP address is (for a quick 4-minute video tutorial on how to open a port in your router, you can click here). To make sure your node is correctly setup, please click here to check whether your port was correctly opened.

And that’s about it! You’re good to go :) Every month we will send you a payout based on how much disk space you got allocated and how many INXT you held. The more time you run the node, the more likely it is that the network will allocate your node files (since it will rank you as a higher quality node than that of other users). All you need to do now is to run X Core in the background to start earning an income thanks to your device’s extra storage capacity! For any questions, you can join our Telegram community to directly chat with our tech team and other community members.

PS. Some tips on how node reputation works:

To understand reputation and how it is used, you should first understand why it is there. It is used to find the most available location for a shard. It is not there to determine your node’s overall reliability, though reliability plays a factor, it is not the only factor. First, let’s look at some basic accounting of how reputation is measured. The smallest reputation score is 0. The largest is 5,000.

If your node responds to an ALLOC request, your reputation increases by +1.
If your node does not answer to an ALLOC, your reputation decreases by -1.
If your node responds to an ALLOC but is unable to fit the shard, your reputation decreases by -1.
If your node reports an error, your reputation decreases by -10.
If your node goes offline, your reputation decreases by -1000.
That may seem straight forward and it is, but the important thing isn’t just to keep your node online and error free. It’s the conditions that would cause your node to not respond to an ALLOC. It will do this by design if:

Your node is full.
Your node can’t fit the shard.
You may think that if you have a 200GB node, you can fit any sized shard. But this is not true. The way X Core’s file system works is that it divides up the shared space into 256 equally sized buckets. So if you have a 200GB share, the maximum shard size your node can accept is 781MB. Anything larger, and your node won’t respond to the ALLOC request. And your reputation will go down.

The largest sized shard that is possible is 31.25GB. But only 8TB nodes would be able to accept that sized shard, and only if they had an empty bucket. (Because buckets can fill with other sizes, they can run out of space to fit larger shards.) All other node sizes below 8tb run the risk of losing reputation when shards won’t fit.

So ultimately, the smaller your share drive, the bigger the chance you will have a lower reputation. Whereas larger mostly empty shares will get the most data and have the highest reputation. At least until they start running out of data.

Because of this, it’s also completely possible to have a small node (such as 200GB) have a reputation of zero, and still be working perfectly fine. It just may be that someone is uploading a lot of large shards that have caused your node’s reputation to drop to zero. Over time, when smaller shards are being uploaded again, your node’s reputation will start to rise.

At the end of the day, your node’s reputation will determine how you receive “mirror shards” but the first shard will not use reputation (for now) as a determining factor in who receives the shard. In this way, even with a reputation of zero, assuming no errors, your node will still receive shards. Just more slowly.

What if the power goes out and my node goes down? Will my reputation still get -1000 through no fault of my own? Yes. The Reputation of your node will decrease every unanswered or answered with “No” ALLOC request. This will decrease the chance to receive additional data. We need to have a reliable node to deliver a high SLA to our customers.