We have not been receiving any supernode rewards yet - do they need to be claimed? Does it appear as a transaction on the primary account?
Yes, you should see the rewards as regular transfer transaction to your supernodeās main account.
Which supernode is yours?
Yes all of them are multisigs accounts.
Here are all the tx hashes:
- ab094791088ca5576ccd8307ccf93b2869053e55f88cd8da82c0fc4bcef82f58
- 4e98e6468c0c1ee2dd330493291d9edaa2f1d2f06d5108896a3275bc435a3b5e
- b85508df1c9888bcda5f32827f6276dd58c24f4b498f09236efc82de777a7ad9
- 1c1b5dd4de118299381e424d06f473adeb33b12cfb5cc7239c16ed574fdf4478
- bc61ea2ea695e0aeee3c27b77af664505c810da41ffd5a6fa8e41fff38fc5739
- 207c205b81a2573f1f0906a4e99ce8b85b3bbd8ff6b2e5033af444c1f436e47a
- 76593d8d3dcb2fbca60c74140ee90df327cc6fb9e716e571b95e5bb91aabbec6
- d7961bf322e69129bf1189c747fcd0c0a4595d3bde966e1f9216e14229175bbd
Hi BR,
Thanks for the response. Maltablock ie https://supernodes.nem.io/details/1090.
We started delegated staking from last week.
Will need a few rounds until the first payout.
Done.
Thank you.
HI BloodyRookie!
Please activate a super node 209.250.226.98 ANECHKA2019
Block 2306655
Hash 6cdf77f6fbb584e7700feca3586054ee0ee7d98fc8fe24885a84eab9f62d0099
Your enroll message
enroll 209.250.226.98 anechka2019 223b58d0b4fbb56625047c6e67494050607dd0cc3452d978a677486a8
has an invalid public key (too short).
checking
Do not understand why. I can not insert the key completely
Sent a new one))
Block 2307397
Hash 7afd48ba949129ab0734633afcc3a38b196c58a4b2bff96970da035d15c82462
It worked this time.
I ask you to deactivate the ANECHKA2017 node
@BloodyRookie
Iāve sent an IP change request for Himmelsfaller 2 to NAFUNDBUKIOSTMD4BNXL7ZFE735QHN7A3FBS6CMY:
change IP 85.10.248.126 to 167.99.253.59
Itās now a more scalable server from digitalocean. Could you change it please. They do not recommend to use swapfile because the drive is pure ssd. Will there be problems without the swap?
Many Thanks.
Just forgot it for the moment. I think Iāve sent the msg from the wrong account. Iām away
for some hours and will check later and send the msg again.
Hi @BloodyRookie . Please help to change IP address and alias for this supernode:
https://supernodes.nem.io/details/787
Cyberblox_sn_service7 >> cbx-sn-07
45.63.42.67 >> sn07.cyberblox.my
Here are the tx hashes:
- 18f587e30a39860c89d861d1ec284090590aff10e966183ea74edf36ff6310ed
- 69f56f2f248fb890b617e1f2d9c73ed3724074e1fe16920a2f5b8cc40861a96f
Hi @BloodyRookie
now the change ip msg should be ok. Could you please change
85.10.248.126 to 167.99.253.59
tx hash
099e4093c591db25bd3082bb1712e4a6aa294779d5133eed1843ef09cb9ed0af
Many thanks!
Done
Done
Hi @BloodyRookie, I have to change the node 167.99.253.59 back
to 85.10.248.126. I changed it because they didnāt told me that it had more RAM
meanwhile. So change was not necessary. Now java has 5 GB. Maybe I will
change it to 8 GB, when the node works fine
msg: tx hash:
c742685fe0a3ff705f2225c22d89a8d9193be0f7aa7fb021906832a67f7360c3
Many thanks for changing back
The 167.99.253.59 digitalocean node always failed and
tail -f nem/node-rewards/servant/logs/servant-0.log
told me that there arenāt any logs. Except that the node works
Maybe port 7778 is not open despite that I allowed 7778, 7780 and 7890 in their droplet firewall. Anyway I will try an installation with Ubuntu and if it works Iāll have a spare node.
Hi @BloodyRookie , need some help on supernode cbx-sn-02 (https://supernodes.nem.io/details/779)
The node is failing since the migration. When i tail the nis and servant logs, they seems to work fine. No java error and crash reported. The other cbx-sn-xx nodes are working fine except for this one.
Is there any other configs that i need to take a look? or anything you can check from your end?