List of dedicated VPS nodes to connect NEM (Updated Jun/21)

Technical Discussion
#1

Down last check, not work Properly
(or port 7890 was changed/inaccessible/busy)

niss.ga
Check
findingnem0.tk
Check
eu.nemno.de
check
us.nemno.de
check
rigel3.nemwork.net
check
ec2-54-93-217-25.eu-central-1.compute.amazonaws.com
check

Others nodes can be found here: nodeexplorer.com/


But some IPs aren’t dedicated.
Since the purpose of the NEM is precisely to provide a uncomplicated experience for users, it would be good to make a list of IPs / DNS here for those who just want to open the NCC on your PC to access the wallet.

It is expected that these hosts have strong passwords and no security issue, as well as being dedicated to NEM and can not have any other purpose, unless assumed their own risk is also recommended accounts with multisig, etc. to avoid hacks.

If you want to put your Node in the list, simply reply this topic. :slight_smile:
[hr]

Note: by default, NIS is programmed to allow only one account to use it to harvest, but you can change the parameters to allow a higher number.



Is there any setting to allow more harvesters in a NIS?

NIS -> config.properties -> nis.unlockedLimit = 1 (dont go higher than 5 or 10 for now, this stills needs some testing)

it is recommended to create a config-user.properties though and copy the settings which you want to change there, before you change them. then do your custtom settings and save the file. NIS will use your custom settings in config-user.properties then and you dont have to change the config.properties.


Other topic about that: https://forum.nem.io/t/harvest-on-my-node/
#2

Updated!

#3

Hello
you spelled SevenofNine wrong
SevenofNine.nemtrader.com
OK
Updated
#4

Updated!!

I will update remove the nodes that are down after some time, about 15 days or more. :wink:

#5

4 more servers to connect to :slight_smile:

43.224.35.140
43.224.35.127
45.63.123.41
45.63.121.41

#6

you guys do realize that there is this http://nembex.nem.ninja/#nodes
right ?

#7

Can these be used to harvest on too?

#8

Can these be used to harvest on too?


depends on the limit that they have set and if there are already people harvesting on them (and you can whitelist addresses as well).
#9


you guys do realize that there is this http://nembex.nem.ninja/#nodes
right ?

I'm not sure what you mean. You cannot connect to nodes in nembex by the information listed there


Actually that should be possible unless those nodes dissalow it.
#10

I'm not so sure, but you just can harvest on the white name nodes, cause the red are not able to harvest… Or should not be

#11

you guys do realize that there is this http://nembex.nem.ninja/#nodes
right ?


IP isnt shown so that list is useless afaik.
#12


you guys do realize that there is this http://nembex.nem.ninja/#nodes
right ?


IP isnt shown so that list is useless afaik.


luzl...that's right ofc. I didn't notice that  :-[
#13

Can't someone else just fetch the same info from the network and display the ip?

If I connect to a NIS over HTTP, can't someone just monitor the data that is sent out and steal my private key?

And will the mobile app just be a mobile version of the NCC that will require a NIS to work? If so, who are supposed to support those NIS:s?

Btw what is the difference between nembex balance and network balance in http://nembex.nem.ninja?

#14

Hi  :wink:

steskoff.ddns.net

#15

Updated!


I'm not so sure, but you just can harvest on the white name nodes, cause the red are not able to harvest… Or should not be

I think that these nodes in red are not connected to nembex, even when the port 7890 is opened and working normally.
#16

please, add:
rigel3.nemwork.net

#17

you guys are awesome.  just showed this feature to a friend and he was impressed.

#18



you guys do realize that there is this http://nembex.nem.ninja/#nodes
right ?


IP isnt shown so that list is useless afaik.


luzl...that's right ofc. I didn't notice that  :-[


Haha. Coming from you, I thought you knew something we didn't. And I was looking around the website like a dick head finding for clues. You had me. Luckily it is not April 1st. today. lol.
#19

sometimes nembex is down so this thread has been really useful

#20

btw, not sure if you guys have noticed, but in 0.6.25, you can actually specify your own nodes inside [tt]peers-config_mainnet.json[/tt] file.

entries MUST include identity (name + public key).
both information can be obtained by going to http://foobar:7890/node/info

the thing is:
If I edit the file, and I will add there node foobar, and at some later point owner of foobar will change his bootkey,
I won't be able to connect to that node, as (according to my nis) he will be accused of impersonating someone.
(as key won't match).

Also I'm not sure now (and I can't check it), but I think name must match too.

So if you'll be preparing community-driven peers-config_mainnet.json, make sure to include there nodes that
are known not to change keys+name :slight_smile:

Happy Easter.