NEM Supernode Rewards Program

You have to send a message for each of the 2 changes separately.

So the only way to host a supernode is to invest $600k which will generate $300 day in the best scenario? this looks kind of joke. Why supernode is forced to have a 3kk deposit? I’m not sure the network can evolve in long term with such requirements.

Well I’m not familiar with supernode payout but if this is really 300$ per day that’s mean it’s over 100k$ per year (1/6 invested money). And to tell the true in my opinion buying xem is good investment and that’s mean today 600k$ xem will be like 1.5-2mln in next year. If I would have this kind of money to invest probably I’ll buy :wink:

Have a look at here: " http://explorer.ournem.com/#/supernodepayout "…thats around 300 XEM per day at the moment, ( only when a SN passed four rounds-performance-tests " https://supernodes.nem.io/history " ).

2 Likes

ok change requests made separately

Hi!!
55

12

This is normal?
I’m new to the super node, I see this for the first time.
Please explain to me.

mainnet

A photo of mine.

I had a look at my servant-output…sorry…the testnet-address for servant is ok…my mistake…a long time ago, I looked at the output…
I will delete the post above from me.

The servant outputs log with wrong network settings (testnet instead of mainnet). You shouldn’t be wooried about that.

Ok. Thanks))

thank you garm a lot for the link. i’m currently very interested in learning these things (i’m also interested in buy anavar for my health issues but that’s something else) so i was wondering if i can ask you for some help later if i would have some questions for you? thank you very much!

Any reason why my supernode keeps failing?

I just switched to a new droplet on Digital Ocean, all other details remained the same correct?

I requested both IP/alias changes, but cant get a first pass:

https://supernodes.nem.io/details/196
http://178.62.36.182:7890/chain/height
http://178.62.36.182:7890/node/extended-info

Yes, the key in the config is wrong. Also check if the servant has correct key and is running.

Why did the version fail in Round 2757?

https://supernodes.nem.io/archive/860/2757

Where can be the problem?
I’m using version nis 0.63.93-BETA

Those failures are usually due to connect timeouts. Not sure if it is just the internet connection or something else that makes the connect fail.

Thanks!

This failure has a negative effect on the operation of the node?
With this problem, the node will not get a reward?

yes

The servant periodically has this appearance:
05

59

It worries me