NEM Supernode Rewards Program

Blog Posts
#1532

when i deactivated them, they had the old version 0.6.91 and thus failed.
I activated them again.

#1533

So I specified correct public delegated key.

how to fix it?)

#1534

@BloodyRookie
thanks. is there a way to get notification that i need to update my node version ?

#1535

No, you need to watch out for new versions every now and then.

#1536

What is your main accounts address?

#1537

NA2WQE-ENXFTX-L4R2OL-552BL6-WA7DTE-KBYOOV-6RHR

thanks

#1538

nembex shows this as importance transfer:

http://chain.nem.ninja/#/multisig/99fa6f63a3402d8fdc624d6a53617d235b2bc09db81fa6269e574fb0471c714d

so the remote account is

http://chain.nem.ninja/#/account/NBCMHWYRPNY74U2X442NOFZZUH6ETO4GFY3MHISU/0

which has the public key

01bdba1326ef9c95e775ae36db820a6cc7d39fbaf38048395286b12ef896c815

and that shows your account as main account

http://alice2.nem.ninja:7890/account/get/forwarded/from-public-key?publicKey=01bdba1326ef9c95e775ae36db820a6cc7d39fbaf38048395286b12ef896c815

#1539

Thanks,

01bdba1326ef9c95e775ae36db820a6cc7d39fbaf38048395286b12ef896c815 - I see it in the one of cosig wallet,manage delegated account of multisig accounts --> public delegated key.

This cosig initiated enroll transaction.

Could you please change delegated public key to 01bdba1326ef9c95e775ae36db820a6cc7d39fbaf38048395286b12ef896c815 from your side or How should I do it?

Thanks in advance

#1540

You need to adjust the delegated private key in the config.

#1541

@Andrey: new entry in db with the new public key 01bdba1326ef9c95e775ae36db820a6cc7d39fbaf38048395286b12ef896c815 is

https://supernodes.nem.io/details/816

#1542

Thank you so much for the help.

will change private delegated key also.

Thanks

#1543

Hi, i got the problem when i moved the old server to the new server. You can check here:
https://supernodes.nem.io/history/search/nem4singapore … I saw that the problem occur when my server from singapore is connecting with africa node and i wondering why this problem happened.

This is the message that i sent to the address NAFUND-BUKIOS-TMD4BN-XL7ZFE-735QHN-7A3FBS-6CMY to change the new ip address. I did two transaction between change ip address and change alias.

  1. for change ip = change ip 197.242.90.170 to 45.76.185.133
  2. for change alias = change alias nem4africa to nem4singapore

Please help and check my supernode because i saw a lot of test fail. I dont want miss my payout day. :frowning:

#1544

I would wait a bit more. The change in location means that for a few rounds the master still sees old results for the tests and picks a node as test partner which is near the old location.
So no wonder it picked a node in Africa.
If it still fails tomorrow then i should investigate.

1 Like
#1545

I changed the Delegate Private key, should i send enroll message again? My Nodes are failing all the tests

#1546

Is the corresponding public delegated key different from the one you used to enroll?
If yes, then state the node alias + ip + correct public key here.

#1547

Yes its different, will do it later, not home atm. thanks!

#1548

@BloodyRookie

Please deactivate my supernodes.
I sent messages to NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3.
hash:f62c22e4929ee90899a21690cd1c441c5ce7789a383451d0d76a5540e1af0f58
hash:76fac58f1052b51c4ad619785370f8dcaae5dc66c9883d94afd308bb5ef9c532
Thank you.

#1549

Could you tell me what the names of the supernodes are?

#1552

Done, thx for reporting.

#1553

In case you are wondering: I had a bug in the update i made to master, therefore for some rounds lots of nodes failed the version test. Sorry for that, it is fixed now.

Reason was that quite a few supernodes supplied a domain name for the ip when enrolling but have the ip (and not the domain name) in the NIS config. I hadn’t expected that.