NEM Supernode Rewards Program

Blog Posts
#2825

I checked in config.properties and old IP address was in there, changed it to new one. Will monitor.

config-user.properties just had node name and some long key, no IPs.

#2826

seems to have passed a test, fingers crossed. :crossed_fingers:

#2827

Question, when I reboot my supernode it always loads the chain from 0 height. Takes awhile. I use the ‘tail’ command to verify loading the blocks.

I thought when moving this .db dump to the nem/nis/data folder it should skip straight to the 2015000 block for a speedy load, but it always starts on 0 for a reboot. Am I missing something?

#2828

Nope, restarting NIS always result in loading the entire chain.

#2829

Hi BR,

Payout for rounds 4533-4536 was 402 rewarded to 348 nodes.
Payout for rounds 4537-4540 is 782, rewarded to 179 nodes.

I see a lot of Ping and Responsiveness failures.
If that is correct, what possibly might have caused it?

garp

#2830

I don’t know what caused it, but most of my Alice nodes failed too.
Probably network issues but that is just my guess, not a fact.

#2831

Seems that chain height test failing again. Can you supply current log again, @suky321?

#2832

Hi, Sorry just saw message now, sending you PM with link to log file.

#2833

I know ponti was spamming his mosaic again.
on reddit he talked about taking down nodes last time with his scripts.
This is somewhat concerning …

any reason why my public-key would be different on?
xxx:7890/node/extended-info
vs
xxx:7880/nr/metaData

#2834

Public key displayed reflects the delegated private key entry in the config.

#2835

same here I have had an influx in failures over the last week… chainpart; ping; responsiveness; version failure???

my nodes were running stable with a weekly reboot without failures for months.

Is this a real threat?

Also is there a historic PERFORMANCE RESULTS list?

#2836

Aside from the history page of the node rewards web page

https://supernodes.nem.io/history/search/HugeAlice2

the only way to get historical result is via a POST request using the node rewards api.

#2837

Can you deactivate 206.81.15.16, I sent a message to your address

#2838

Done.

#2839

Is NCPAYOUTH2BGEGT3Q7K75PV27QKMVNN2IZRVZWMD the reserved payout pool? Does that mean it’s almost dry? What happens next? Mega-dump?

#2840

Here is the Supernode Rewards address:
NAFUNDBUKIOSTMD4BNXL7ZFE735QHN7A3FBS6CMY

#2841

Thanks, that one looks better. :slight_smile:
31 july 2020 I guess.

#2842

did stuck the today rewards?
what happen?

#2843

It is not stuck, not sure what you mean.

Edit: OK, i see it, the payout account is empty :confused:

#2844

Payout process has resumed. There were some missing payouts due to the lack of xem in the payout account in round 4653 - 4656. Those missing payouts were done today and are listed in the following document:

payouts.pdf (62.2 KB)