When I enloll my supernode, I send wrong public key to NAFUND-BUKIOS-TMD4BN-XL7ZFE-735QHN-7A3FBS-6CMY
Please tell me how to revise it.
which supernode is yours?
My super node is “super4610node”
what is the correct public key? Is the rest of the data (alias / ip) valid?
The correct public key is"18f8c3da358a6dcdc5ddecb9d5130e037f06bc6bfb9c4a40c579375c1d2bc6e6"
The rest of data is correct.
ok, disabled old one and added new one with correct public key.
https://supernodes.nem.io/details/504
Thank you so much!!
today supernodes is 396 xem
is a little
i can not understand
why does not incrreased a little
the supernodes???
because on average the payout is ~400 xem and that is enough.
@BloodyRookie
Node rewards payout: round 1673-1676
was not paid. Please check.
It seems stopped since Block Height 979507 2017-02-12 15:52:48
Ok, will check that, thx for the info.
Payout resumed, sorry for the inconvenience.
Thanks for prompt support 
Hello BR, I see the new version out, when is the deadline to update the SN?
Just updated my new super node ninja2016 at ctl.io with NEM version 0.6.83-BETA but it keeps failing the Version test.
Not sure it’s because I registered wrongly or something else.
some links:
The upgrade is not mandatory, not sure if there will be a deadline.
ninja2016.dynu.com resolves currently to 205.139.18.80 while in your config i see 205.139.20.4.
That is the problem.
We built an NIS server with a possession amount less than 3 million XEM and sent an enroll message.
Is there a problem when providing NIS service in this state?
I do not need super node compensation.
It is not a real problem but unwanted since it can never pass a round if it has less than 3M XEM and it occupies some space in the database.
Any chance you get the 3M XEM within a reasonable amount of time?
1 Like
If you get something big, you can prepare 3 million XEM, but it is quite low as a possibility.
Every time it is less than 3 million XEM, the round pass fails, but if you can technically play the role as an NIS server, I would like to contribute.
Currently, it is impossible to understand what behavior behaves when it is specified as a harvesting server, so we can not specify it as a harvesting node destination.
Nis.unlockedLimit = 0
IP address : 153.122.13.112 (My Server)