Beta launch is near: get your 50,000,000 NEM fully vested Nemesis account

There will be a limited number of nemesis accounts, each containing fully vested 50 million NEM, that we give to users that run reliable nodes.
The requirements are:


    [li]Your node should be running 24/7 or at least the major part of a day.[/li]
    [li]Your node should be updated each time a new version is available.[/li]
    [li]You should spend at least few minutes DAILY to send a few transactions to other users.[/li]
    [li]The node should be able to respond to requests from other nodes. You can test that by running your NIS, open your browser and try the request:
    http://<your ip>:7890/node/info so if your ip is 79.210.192.210 then try the request http://79.210.192.210:7890/node/info
    If the request fails it means that either your router does not forward port 7890 or that a firewall is blocking the request. If so try to reconfigure your equipment so that the request works. Nodes that fail this test are of little/almost no use for the network as they cannot participate in broadcasting data.[/li]


    If your node is ready, either post your ip here so I can check that it is correctly configured or, if you don't want to post the ip in public, send me a pm with your ip.
    If approaved I will send you a pm with the private key for your nemesis account (since it is play NEM you can be sure I will not rob your account :wink: ).

    Go for it :slight_smile:

There will be a limited number of nemesis accounts, each containing fully vested 50 million NEM, that we give to users that run reliable nodes.
The requirements are:


    [li]Your node should be running 24/7 or at least the major part of a day.[/li]
    [li]Your node should be updated each time a new version is available.[/li]
    [li]You should spend at least few minutes DAILY to send a few transactions to other users.[/li]
    [li]The node should be able to respond to requests from other nodes. You can test that by running your NIS, open your browser and try the request:
    http://<your ip>:7890/node/info so if your ip is 79.210.192.210 then try the request http://79.210.192.210:7890/node/info
    If the request fails it means that either your router does not forward port 7890 or that a firewall is blocking the request. If so try to reconfigure your equipment so that the request works. Nodes that fail this test are of little/almost no use for the network as they cannot participate in broadcasting data.[/li]


    If your node is ready, either post your ip here so I can check that it is correctly configured or, if you don't want to post the ip in public, send me a pm with your ip.
    If approaved I will send you a pm with the private key for your nemesis account (since it is play NEM you can be sure I will not rob your account :wink: ).

    Go for it :slight_smile:

The page doesn't load and I don't know how to adjust the firewall or router.  So sad because I wanted to help!

Do you have access to your router and the manual? Should not be too hard to configure it.

I have access to one router, but there maybe another one I don't have access too.  Even if I do, it will be in a different language and no manual.  Regardless, I will give it a try over the weekend.

Probably will be too late by then. Let's wait how many users want an account. I would prefer users with well configured nodes cause it helps the network more and we unfortunately have too many misconfigured nodes right now. But if there are accounts left you will get one for sure :slight_smile:

Interesting. Forwarded a port in my router and yellow error on top of client became green and is written "NIS is synchronized". Easy solution to get rid off this weird error message :slight_smile:

@Speedy69: right :wink:

No motivation to run away with the 50M NEMs, sorry dude  :stuck_out_tongue:

I may lease a netbook with public IP for this purpose running 24/7/365, however i have to solve some network troubles first, my home is completelly behind NAT because i was lazy when making a connection here and now i have to rebuild it completelly and finish it :confused:


We are talking about 50 million testnet-NEM, right?

My VPS: 5.249.147.16

@smaragda: http://46.166.186.246:7890/node/info is not responding. Is your node down at the moment?

@renolteng.li: you can let NIS autoboot if you edit the config.properties in the nis folder (don't forget to remove the "#" at the beginning of the line):
nis.bootKey = <your private key used for booting>
nis.bootName = <any name you like>
nis.bootWithoutAck = true


Thanks for the update.
I'll be thrilled if anyone here vote on this link.
https://forum.ournem.com/index.php?topic=2524.0
I'm one of the unlucky guys who lost NEM AE token with wrong NXT account.
I'm not trying to mess up with the votes, if you have a minute just do it on behalf of yourself ~~
Thanks!


Again. Could you post your NXT address with lost nemstake in it?


@smaragda: http://46.166.186.246:7890/node/info is not responding. Is your node down at the moment?


No...  the node is up & running but I just noticed that the IP keeps changing...  I guess I will have to sit on the sidelines this time. 

I got the results that I posted before using the IPv4 address...  I am connected through a VPN...  :'(


Post (or pm) your current ip. It's ok if your ip is changing, The other nodes will discover your ip. Your node only needs to be correctly configured :)

I have been trying to get my port open but not sure how to do it.  I have managed to get past the foreign language with a little help from Google translator, but I am still a bit lost.  I have fiber coming to my building about 3 meters away from my computer, there is a router than or maybe two, and then one here on my computer.  I'll try a little more later I think and will have it figured out someway by the time Nemesis comes, but I doubt I'll make this launch.

jabo38s : what is the name of your router model?

I see some progress. Here's what I'm getting here:

{"timeStamp":6595293,"error":"Internal Server Error","message":"network has not been booted yet","status":500}

:slight_smile:

{"metaData":{"application":"NIS","version":"0.3.2-ALPHA","platform":"Oracle Corporation (1.8.0_05) on Windows 7"},"endpoint":{"protocol":"http","port":7890,"host":"xx.xx.157.9"},"identity":{"name":"Spider","public-key":"0385d6ace67d826f9a0359a31674d5fcf1a529aebd82bdadc11f6ca9cff13c7b49"}}


@smaragda: http://46.166.186.246:7890/node/info is not responding. Is your node down at the moment?

@renolteng.li: you can let NIS autoboot if you edit the config.properties in the nis folder (don't forget to remove the "#" at the beginning of the line):
nis.bootKey = <your private key used for booting>
nis.bootName = <any name you like>
nis.bootWithoutAck = true


Question about that actually. What act of stupidity am I committing? abc123 is a proper pubkey, just swapped it here for simplicity. It should also be noted I get identical behavior whether on windows or Linux with different 1.8.x JDKs.

When booting normally from ncc (which is working fine) I get the following node info:

{"metaData":{"application":"NIS","version":"0.3.2-ALPHA","platform":"Oracle Corporation (1.8.0_25) on Linux"},"endpoint":{"protocol":"http","port":7890,"host":"xxx.xxx.xxx.xxx"},"identity":{"name":"test","public-key":"abc123"}}

with the following config changes in my properties file to nis:

nis.bootKey = abc123
nis.bootName = test
nis.bootWithoutAck = true

I get the following node info:

{"metaData":{"application":"?","version":"0.3.2-ALPHA","platform":"?"},"endpoint":{"protocol":"http","port":7890,"host":"xxx.xxx.xxx.xxx"},"identity":{"name":"test","public-key":"abc123"}}

As I am also experiencing the alpha bug "NIS info is not avaiable yet. Trying to retrieve NIS info...", I'm also not positive what the actual NIS status is as reported to NCC, but just to check, I submitted a transaction and got:

An error occurred that the development team did not have foreseen. Apologies for this, maybe a retry might help. Otherwise, please open up an issue within the NEM NIS/NCC community.

jabo38s : what is the name of your router model?


My router is an ipTIME N104V

I got as far as this is the process https://www.dropbox.com/s/zqxo7w3kfkgan8m/Screenshot%202014-10-19%2021.18.28.png?dl=0

I basically made a name and tried to forward a port, but it didn't work I guess.

I see some progress. Here's what I'm getting here:

{"timeStamp":6595293,"error":"Internal Server Error","message":"network has not been booted yet","status":500}

:)

{"metaData":{"application":"NIS","version":"0.3.2-ALPHA","platform":"Oracle Corporation (1.8.0_05) on Windows 7"},"endpoint":{"protocol":"http","port":7890,"host":"xx.xx.157.9"},"identity":{"name":"Spider","public-key":"0385d6ace67d826f9a0359a31674d5fcf1a529aebd82bdadc11f6ca9cff13c7b49"}}


Spider, so boot your nis and pm me your ip.