NEM Supernode Rewards Program


#2761

Your new nodes are not showing the delegated public keys that you enrolled with, please check.


#2762

thank you!


#2763

@BloodyRookie
My supernode is running but failing all the tests after change ip.
Message was send, and everything looks ok. Please check it.
http://62.113.254.99:7890/node/extended-info
https://supernodes.nem.io/details/973


#2764

The ip in the db was not changed. when did you send the message? Can you give me the tx hash?


#2765

24 december, 9f21e08ccf0f7473c169e4b8d3f2b7a42f76ebc6fd3f1e3a1c7f764f84979512


#2766

I don’t see any such transaction in the main chain.


#2767

Strange, in account it confirmed.
Send message again:
http://explorer.nemchina.com/#/s_tx?hash=24f03de4329cfc0647ee7ab43a4dd8e46588bac51bc519dd19830c1b8a976650


#2768

Oh, you are right, nembex is the problem. But your message states that old ip is 23.163.0.42 and the db has ip 45.56.162.254 for entry with alias fortune. That is why the ip wasn’t changed i guess.


#2769

Oh, i send message to change ip from 45.56.162.254 to 23.163.0.42 early.
http://chain.nem.ninja/#/transfer/b54aafc541bf2b803dfad2b4c01c40d24b0786af587539a18974b094fd76b1df
but don’t control that it change.
Can you fix it or i need to send new message?


#2770

Changed ip manually. Should be ok now.


#2771

Thank you. It’s work. Happy New Year! )


#2772

Hi, BR, what’s happened with SuperNode measuring among 2019-01-06 12:58 GMT and 2019-01-07 09:14 GMT ?


#2773

The result evaluation task was stuck. I fixed it.