NEM Supernode Rewards Program

Sent you a pm BloodyRookie. Need re-activation on xnode in case you missed it

I send the message to change IP and Aliase of UNIY. please check it.

Failing everything after re-activation (2 rounds).
Cant connect with http://86.45.107.3:7880/nr/metaData but that happend before and others here were able to see it.

Servant output
2016-07-20 15:40:47.925 INFO ping -> pong (org.nem.rewards.servant.servlets.PingServlet handlePost)
2016-07-20 15:40:47.950 INFO ping -> pong (org.nem.rewards.servant.servlets.PingServlet handlePost)
2016-07-20 15:40:48.751 INFO ping -> pong (org.nem.rewards.servant.servlets.PingServlet handlePost)
2016-07-20 15:40:48.756 INFO ping -> pong (org.nem.rewards.servant.servlets.PingServlet handlePost)
2016-07-20 15:40:51.726 INFO ping -> pong (org.nem.rewards.servant.servlets.PingServlet handlePost)
2016-07-20 15:40:51.756 INFO ping -> pong (org.nem.rewards.servant.servlets.PingServlet handlePost)

Have patience, @fragout, your node looks good in round 873.

tks :slight_smile: I knew i should have waited for 1 more, doh

Need to change IP . Xnode . msg sent to NAFUNDBUKIOSTMD4BNXL7ZFE735QHN7A3FBS6CMY

ip was changed by the bot.

Owner of Supernode FREA
You have a typo in your nis config, please eliminate the trailing space in your ip address.

Can you reactivate supernode 48? Its ready to work again

  1. Your NIS config shows a static host: 74.201.226.99
    Since you are using yodanodesbest.ddns.net in the enroll message it would be good to adjust the config for NIS and servant to use it as host.

  2. Your NIS config shows a wrong public key, that is not going to work. Please fix the config accordingly.

How about now @BloodyRookie?

Public key is ok now.
In the endpoit section of the config I meant to change

host: “74.201.226.99” to host: “yodanodesbest.ddns.net

The node name doesn’t need to be changed it still can be

name: “Yoda”

also having the same problem
but finally i found the fix

nevermind

“change ip 216.189.150.183 to 216.189.147.226” message sent for supernode300

HI,

My supernode NEMDONG failed Version test?
Why is this the case? I have not made any changes, can you check and let me know what the issue is here?
330xem is alot these days and I’m not happy on missing out on 1 round.

It can happen that at the moment that the master tried to perform the version test on your node, the connection to the node was unavailable. Internet connections are not as stable as everyone thinks.

“change ip orbedragones.no-ip.org to 92.222.75.65” message sent for orbedragones

Thanks

A question, when is scheduled to be increased the rewards for supernodes?

According to the Jeff’s document it is 3 months after start, that would be September.
Probably a good idea.