NEM Supernode Rewards Program

Blog Posts
#1823

that means your node couldn’t reach (and perform the ping test) some other nodes. That has no negative influence on your test results. The log doesn’t show which nodes couldn’t be reached. There are nodes where the servant is not running and that could explain the above exceptions.

#1824

Ok! Thank!
Which servant file is right for use ?: config or config.use
Which is right and better?

#1825

config.properties is ok and if you want, you can supply config-user-properties additionally.

#1826

I went ahead and reenrolled my supernode. As it seems the delegated pub/private keys have changed…

#1827

Have to add a new entry manually.

Edit: done
https://supernodes.nem.io/details/862

#1828

@willowfoot, seems the servant is not running on your node.

#1829

ok looks like everything is working yet, the balance is not registering?
https://supernodes.nem.io/details/862

Is there something in the nano I need to do?

#1830

hmm…what is the main account’s addess?

#1831

main account:
NA4U2N-ILIGOR-EG7CGW-M7SOJA-73NVJL-PM4FRL-E4AY

#1832

lol, then the old remote account is still active:
http://chain.nem.ninja/#/account/NATEX7-6QGQQR-7YIGBP-346D62-5V5HR5-4W7Q45-KMDO/0

#1833

ok dont fully understand, what do I need to do?

#1834

where did you get the key from that you wanted to enroll with?

#1835

Originally I started the supernode (LandofNode) in NCC, so delegated keys came from there.

This new supernode (London-Fog), just imported private key into nano, and got the delegated keys from the nano … but they are different.

#1836

So you can deactivate delegated harvesting, wait 6 hours and reactivate it using the Nano Wallet key.

#1837

Hello Bloody Rookie

I send to forum following message just now.
(delete NoiseR1 and add NoiseR10)

Please disable supernode NoiseR1
enroll 153.122.87.54 NoiseR10
d76f7d2ccefd5ba666e387aca3802ee28834a9ca6f1e2549e51175754231864d

Please respond to that.

Thank you.

#1838

@chibi: Done

#1839

Good morning BR

Thank you very much.

By the way , I sent another message following:change ip 153.122.84.149 to
153.122.87.50

IP address have changed , but appear “FAIL” only.
Do you understand that reason.?

Thanks.

#1840

the public key you supplied for supernodes is

dd50cb3db9c0792f4d2c69b43334dc968f380584c35fa6d08b260dff5f0cec61

but the public key i see in the request http://153.122.87.50:7890/node/info is

6a7dccf22dc2655bd4bb83dd127cc715c1f60468f0e5c34eee619df3be043d8f

So it is a public key mismatch. Which one is correct?

#1841

Hello Bloody Rookie

I understand this.

Old supernode use delegated account private key,but new supernode use
private key.
So “dd50cb3db9c0792f4d2c69b43334dc968f380584c35fa6d08b260dff5f0cec61” is
correct.

Do you correct my mistake?
Or may I retry to make supernode which use delegated account private key?

Thank you.

#1842

In that case, you need to use the correct delegated private key in the NIS configuration and Servant configuration. Please check the configuration files.