NEM Supernode Rewards Program

Blog Posts
#1057

When I tried it from my home PC, I can see the correct IP from FQDN. Please check.

Non-authoritative answer:
Name: ec2-52-69-175-217.ap-northeast-1.compute.amazonaws.com
Address: 52.69.175.217

#1058

@owner of supernode RED_SP_TRON. You wanted to change the public key but the new public was trancated in the message. Please state the new key in a message to NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3

#1059

i informed QM of the problem.

#1060

To remind you:

NIS Version 0.6.87 is out. The upgrade is mandatory. Please upgrade your supernode

1 Like
#1061

Thanks for the reply.
Yes, my NIS server itself works as ec2-52-69-175-217.ap-northeast-1.compute.amazonaws.com.

But the registered ip(FQDN) of my node at “https://supernodes.nem.io/details/618” has NOT been changed yet.
So, the tests keeps “fail” referencing no longer valid old ip.

1 Like
#1062

Thanks, i will wait for a while.
FYI. NIS Version is 0.6.87, newest one. :wink:

#1063

Hello guys! For changing my public key i have to send a message like

“Change public key myOldPubkicKey to myNewPublicKey” ??

Thank you!

#1064

Ok thank you but what is trancated?

#1065

the new public key in your message was truncated, maybe you were using ncc which does not support such long messages?

#1066

I’am using nano wallet 3

#1067

oh, actually you are right, non truncation, was my bad ^^
will change it. This mean i will deactivate the old entry and create a new entry in the db.

#1068

Ah ok :slight_smile: thank you! All its done?

#1069

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

#1070

Good! Thank you!

#1071

try to enroll with the ip 52.69.175.217, the enroll bot doesn’t like that extrem long amazon domain name.

#1072

O.K. i got a static IP for my node.
i will try enroll with ip, instead of looooong FQDN.
honestly i want to change my host name from “rpi01.tane” to “aws01.tane” because now aws, no more raspberry Pi.
can i send completely new enroll message like “enroll newip newname delegated-public-key”?
or should i send 2 change messages for ip and node-name?

#1073

If it is the same public key you cannot enroll again, you need to change ip with one message and the name with another.

1 Like
#1074

I see, thanks! :slight_smile:

#1075

Hello BR
This time exporting from NCC to Nano and rewriting config properties, which is configuration file of NIS and Servant, although I sent a message to enroll with new delegated public key, the setting is not reflected.
Please give me a response in regards to that.

Details sent: Mon, 17 Apr 2017 09:40
[destination] NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3
[alias] liang2
[old public key] 39108aea5d9d408c3029600a1f54e9d7c876405507c01afa11371ec2d775f00c
[new public key] 5040dfaa21974b23b74470ec3f6b4ecdaf1bfd6ec11224d6feb5696f79f68d4b

node info:http://160.16.63.95:7890/node/info

#1076

Sorry, forgot about it. I disabled the old entry and added a new entry with the new public key:

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