NEM Supernode Rewards Program

still old ip :confused:

ok, if it is not solved in a few hourts, i will change the ip manually in the db.

@Dimas, QM informed me that you sent the message to the wrong account:

http://chain.nem.ninja/#/transfer/03f8c5cf8b5d7fcf9b4a7e6addaa8cd5bc45f44231aa1804bc7cab6a408ac477

You have to send the message to the noderewards fund account, not the payout account.

oops
NAFUNDBUKIOSTMD4BNXL7ZFE735QHN7A3FBS6CMY
this one?

yes

… and nothing changed :worried:

It was changed :slight_smile:

Oh, thank you)
http://chain.nem.ninja/#/nodes/
still shows old ip
Is there any other site where I can check it?

supernodes.nem.io ?

Trying to figure out why node https://supernodes.nem.io/details/16 is failing tests since I converted the funding account to 2 of 3 multisig. I re-transferred the importance and entered the new delegated private key into NIS and the servant. The servant and NIS logs look clean and I can successfully connect to the node via the Nanowallet which shows that delegated harvesting is active. Any ideas what I’m doing wrong?

Thank you.

Since the Remote public key has been changed, you need to enroll again. Since it is necessary to erase last time, please consult with @BloodyRookie

thanks

1 Like

@mizunashi is right, the delegated key changed so you need a new database entry. Please send a message to

NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3

with the new data from the account you used to enroll the old node…

1 Like

Forgot the public key was used during enrollment. Sent, thanks!

new entry:
https://supernodes.nem.io/details/781

Ah man I lost my proud 16th spot! :stuck_out_tongue: Thanks again!

If I put delegate private key in the config file, it means NIS will always harvest for that account without having manually activate it right? If so, is there a way to put multiple account private key in it? What would be the syntax?

hi, @awu25

Please read this document.

thanks

Thank you

Not the correct thread for this but its important if you are not aware BloodyRookie. Notice on polo - XEM is currently under maintenance or experiencing wallet/network issues. Deposits and withdrawals will remain disabled until a solution is found, which may require an update from the XEM team. Any updates must be tested and audited before enabling.

I don’t see that message.