NEM Supernode Rewards Program


#2535

Br, check please z1, z3 and z4 new ip addresses.
Sent messages yesterday


#2536

IP addresses were changed.


#2537

BR, something wrong with measuring or displaying of results ? I see last results on Rewards History page (or pages, looks like it’s global) around 2018-06-20 03 p.m. GMT, nothing fresher (?)


#2538

Yea, result analyzer task was stuck, had to restart master. Hopefully works now.


#2540

I don’t think it’s working


#2541

Yes it seems the analyzer is still stuck.

Does this delay payouts in any way?


#2542

I found the problem and corrected it. Unfortunately i had to restart the master again.

Yes, there were no payouts during the time the master was stuck.


#2543

As of now the payout still hasn’t started it seems.


#2544

We are at collecting results for round 3627 now. Next payout is scheduled when we have finished collecting results for round 3628.


#2545

Missing rounds will be paid ?


#2546

I will evaluate the missing payouts probably tomorrow.


#2547

Here are the missing payouts. Any supernode which had a payout in the last two days before the incident, was eligible to receive a payout. It turned out that 422 node were eligible, each getting 663 xem. Here is the list:

payouts.pdf (112.9 KB)


#2548

great


#2549

I guess now is a good time for buying 3,000,030 XEMs. :smile:


#2550

I’m not sure I did it right, my intention was dismiss the rigel9 supernode and riactivate the old rigel8 with rigel9’s account

Please, @BloodyRookie, check it


#2551

That won’t work that way ^^
I manually disabled rigel9 and added a new rigel8…

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


#2552

Measuring / rewarding is stuck / disabling again ? I see - on history page - last round #3661, which is ~ 24 hours ago…


#2553

There was a delay but is not stuck.


#2554

BloodyRookie, could you please help with https://supernodes.nem.io/details/889

I’vent made any changes last 30 days at least, but it fails tests https://supernodes.nem.io/history/search/Xem1Xem

Thanks in advance.


#2555

Looks like it is doing fine in the current round. This will be reflected within the next day.
Maybe your node was rebooted by the provider and didn’t restart NIS / Servant?
Did you restart NIS / Servant in the last few days?