NEM Supernode Rewards Program

Not sure what you want to tell us with that post…

Hi @BloodyRookie I changed the main account for supernode NEMczech (I sent all my XEMs to new account). So in new main account (new wallet address where I sent my funds) I generated new delegated private key which I already edited on my supernode server. Is there any other thing I need to do to properly receive payments to my new main account? Thanks.

Since you are using a new account, you need to do a full supernode enrollment again. Once done i can deactivate your old supernode.

Thanks. So from my side everything is done? Am I right? I should not do any other step right now? How long it take to do full supernode enrollment?

Did you send the new enroll message to the noderewards account? Can you paste the transaction hash?

Sorry I missed that step. So I have just sent the enroll transaction. Please check it :).

Please paste the tx hash.

2cf55316e5ac3e2ba04d0fe07c2d451001d0409cef61e2e35b09496622e12f05

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

Thanks. So is it now done correctly? :slight_smile:

Yes, everything should be fine.

1 Like

Do you really think that it is really OK for my supernode nemczech? Because I still see that it cannot pass tests… Thanks.

The servant was started with the wrong boot key:

http://185.185.40.67:7880/nr/metaData

NIS seems to be stuck:

http://185.185.40.67:7890/chain/height

I have just fixed servant boot key and also restarted my server. I hope it will be fine then.
Also, thanks for your assistance (as you can see I made some mistakes).

So I restarted my server, but as you can see it again stucked at height 2593996
http://185.185.40.67:7890/chain/height

Do you have any idea how to fix that and why it stuck at exactly same height like before restart?

EDIT: I try another restart of server. Before restar of server I deleted all log files. It is just a try if it can be somehow related. If you have any idea please reply here.

Looks like your supernode is syncing now. Or loading the chain…
If it is stuck again, download the chain from bob.nem.ninja.

1 Like

I think it seems OK right now. Deleted log files seems really solved the issue (or I do not know what it solved :))

Hi! all settings are complete, ports are open, but the servant does not work. Nis is synchronized. what is the problem ?! For whom was this done at all? Why couldn’t it be easier to configure it !?

Coronavirus01

Seems the node is not reachable, are the ports 7890 and 7880 open?

45.32.94.92:7890/node/info
45.32.94.92:7880/nr/metaData

Hello, BloodyRookie.

Please, I want you to look into it.
Yesterday I tried to register the node.

My node is registered on this website (https://nemnodes.org/nodes/ )
But my node is not registered on this website (https://supernodes.nem.io/).

Am I doing something wrong?

The transaction hash is http://explorer.nemtool.com/#/s_tx?hash=ecdf1d12f7eec0ab091f4007bfe46cbe2c773c6af113cb49476c3540e5383a7f .
The name is t-inter.