NEM Supernode Rewards Program

Blog Posts
#3128

Request: node name “bue.twitter”

please help to change ip 52.2.187.5 to 39.98.206.146

http://39.98.206.146:7890/node/extended-info

TX:
Block 2782692

Hash 67eab551c64acb8875f45d354f4f2ec2be55cae3360702cd756d1d4cd781ed97

Multisig hash4643fa1cb47bbdf0e88dfa59a05eaf16c53ad24bc51b7606531d6742571001f0

#3129

https://explorer.nemtool.com/#/s_tx?hash=6870be808297415bc83a6dc238c35578e0c4d51387f31fbc0dad0356b6d2ffb1

#3130

Done.

#3131

Done.

#3132

Reactivated the node.

#3133

please help me (nis.bootName = opensesame) to change ip 120.27.68.25 to 47.252.10.84

Block 2788844
Hash a47db51c1c34a179cd3a9feac01ea1ec0dc8c5fb776e84c0afa1403bebe75efd

#3134

please help to change node name “bue.twitter” ip 39.98.206.146 to 8.211.51.165

Block 2788847
Hash 926919e7440b2bd5b11db55abbfea9356ba87d61608eb5dc0353d9bef3c4f8a5

#3135

Done.

1 Like
#3136

Hello, we have finally managed to start the 3rd node.
Can you reactivate it?

the enroll hash is
c789eda072bea1d8f6cb46eb595775b2006531d032c65137de27c3cfc415beed

#3137

I inserted it manually:
https://supernodes.nem.io/details/1120

#3138

@BloodyRookie
Hi BloodyRookie,

Can you take a look at my messages on Telegram regarding running a Symbol testnode on a NIS1 SN: https://t.me/c/1480701111/12343

Thanks in advance,
garp

#3139

If the supernode account is in a trezor, I have to create a new account outside in order to “opt-in”, right?
Can I change in current supernode the “delegated private key” of the new account, keeping name and IP, or do I have to create a new supernode with the new account?

Thanks

#3140

If you switch to a new delegated private key, you need to enroll again. If the enroll-bot cannot handle it automatically, then post the hash of the enroll transaction here and i will manage it manually.

#3141

hello,Bloody Rookie.
I setted up new supernode , QRKU https://supernodes.nem.io/details/1151

but I’ve misstaken to send enroll message , balance 0/3000000 .(in my wallet, it keep 3000000 or up)
enroll hash:
db75878ffe70db6f3ac395fb03abdc2dc0c7fa2d613c5926cedba3de6a7ad6b8

#3142

You need to activate delegated harvesting for your main account first, then send the correct enroll message again. When done, post the tx hash here and i will add the node manually to the db.
Meanwhile i will disable the incorrectly enrolled supernode qrku.

#3143

@BloodyRookie
I activate delegated harvesting, and send enroll message again.
hash: d87da95e08fe4d1bdea668416ea95399f00f2017e867f85d0b31f9194feb54b9

#3144

http://chain.nem.ninja/#/multisig/3edd793150596fc6b78a57f867b455f6497f46c66fdb4de9ac6174669b446f49

Are you sure your remote has public key 112e19ae9383aa02df28c96596c040e34c7219bd954098a12dabe5f1782ee149?

#3145

Hi @BloodyRookie, could you please help me with this problem?
My supernode nemczech has last days problem with passing “chain part” tests. I already tried to restart my server few times but it did not help. All other test is passing. So, do you know where is the problem? Because I am constantly missing supernode reward for lots of days.
Thank you.

EDIT: I also see that few last supernode reward payments are higher than usual Eg the last one for round 6805 - 6808 is 583 XEM. So maybe I am not the only one with the same issue. I am just guessing but it seems pretty weird to me. Or do you think the problem is on my side? If yes, where? Thanks.

#3146

Might be related to the internet problems that appeared on sunday. The summary for the round is always a bit later. Generally your node is passing the chain part test so i think everything is fine.

#3147

Thanks. I will check it today and tomorrow if all test will pass, mainly the chain part test. So do not you think the problem is on my side (on VPS provider side)? I actually use hostus.us VPS. Maybe allnodes.com are more reliable for supernodes? What do you think?