NEM Supernode Rewards Program

BloodyRookie · April 4, 2018, 7:58am

Hi there

tehfiend · April 4, 2018, 8:50pm

Best thing to do is just add your Trezor account as a co-signer to your existing supernode account.

yohanzah28 · April 5, 2018, 3:06am

Hello @bloodyrookie the supernode guy kudos to you and need more guidance on my project proposal

ryucoin · April 5, 2018, 3:46pm

Hello.
I changed the server of supernode.
I sent a message to 【NAFUND-BUKIOS-TMD4BN-XL7ZFE-735QHN-7A3FBS-6CMY】.
change ip 27.134.243.236 / DRAGON to 110.44.135.54 / DRAGON
Is this the procedure?

BloodyRookie · April 5, 2018, 4:00pm

try again without name, e.g.
change ip 27.134.243.236 to 110.44.135.54

ryucoin · April 5, 2018, 4:26pm

I sent it again.
Please check.

change ip 27.134.243.236 to 110.44.135.54

BloodyRookie · April 5, 2018, 4:28pm

It worked.

ryucoin · April 7, 2018, 9:53pm

Thank you.
But I’m sorry.
I moved to another IP again.
I sent a message again. (Change ip 110.44.135.54 to 110.44.135.87)
By the way, is this work done automatically?

BloodyRookie · April 8, 2018, 8:14am

Usually the bot can handle the message and makes the ip change. In some cases i have to do it manually.

fulcrum_013 · April 9, 2018, 7:21am

Hello here. I need some support wih my supernode ACS-01. Trouble is: supernode configured and installed following the manual, node info page and log files show no errors, but it fail all tests. Other 3 supernodes installed by same way on same hosting prowider works smoothly. Where to find what same is wrong with this supernode?

BloodyRookie · April 9, 2018, 7:57am

The node is using the wrong private key. The database is expecting the public key to be

04e4f701d62a8d6f10499115d0170e86e6ca7cb1a70d9f1aa2ea25f3822e8e53

but the node is exposing the public key

3b24ef761dd5dc0b5de486b3122c72458f83d5b21a674163882b4a730f0473ea

see response to

http://185.185.40.27:7890/node/info
http://185.185.40.27:7880/nr/metaData

nemstar · April 9, 2018, 5:18pm

hi,
we are running 0.6.93 nis-ncc. Is that a problem? Should we upgrade to 0.6.95?

BloodyRookie · April 9, 2018, 5:21pm

Not a problem per se, but it is recommended to run the most recent version on a supernode.

nemstar · April 9, 2018, 5:33pm

I wonder if there is anything different or special I need to know when upgrading. Different from the guide, i mean

BloodyRookie · April 9, 2018, 5:34pm

Not sure which guide you are referring to. Updating is done by replacing the jars for example.

nemstar · April 9, 2018, 5:58pm

I mean this: https://blog.nem.io/nem-supernode-command-line-tutorial-for-debian-8-4/

BloodyRookie · April 9, 2018, 8:24pm

It seems to replace the package folder with the new folder. Should work i guess.

fulcrum_013 · April 10, 2018, 5:34am

But node has worked with key that his shown smoothly since may 2017. After i has moved it to other server it failed to pass tests.
Also wallet from wich node has been enrolled shows deligated public key 3b24ef761dd5dc0b5de486b3122c72458f83d5b21a674163882b4a730f0473ea

How it possible that database contains other key, then deligatet public kay of wallet that has been used for enroll and still contol changes of node IP? Looks like it is database bug. And how to solve this issue?

BloodyRookie · April 10, 2018, 8:22am

You seem to have several supernodes. The main acounts are:

ACS-01: NAC35QKLVJ7AM6GNS7ZAVC2HV2ZBAYWYB5D4QPTV
ACS-02: ND2ISYVYU4E5IM3WJRUXVJWDZVMKUGA3R22PDETS
ACS-03: NCR34B4C37OY3ZINWORNR5L2MNKCF5HK3FEVOJFY
ACS-04: NBMOZNNLNYUMR2JT5GTYWJBOPIZFI25ULVMR43SY

Are you sure we are talking about ACS-01?

fulcrum_013 · April 11, 2018, 5:42am

Of course i am sure.I has double checked wallet numbers. Number for ACS-01: NAC35QKLVJ7AM6GNS7ZAVC2HV2ZBAYWYB5D4QPTV matches number on wallet from screenshot that have public deligated key 3b24ef761dd5dc0b5de486b3122c72458f83d5b21a674163882b4a730f0473ea. Other nodes matched specified wallet numbers and public keys that thay shows too.