Hi, i noticed that my enrollment public key harvesting is not the same as my public key harvesting because is changing in different version of wallet and since i have switched to a new ip and new installation i don’t have my enrollement prive key harversting… why different wallet version change the harvesting key ? so i have to process a new enrollement ? @BloodyRookie thank you
I had this problem in the beginning. Your delegated private key is not linked to your normal private key in the wallet. The wallet will generate a delegated public key upon loading or making the account private key. You then send a transaction making the delegated private key the harvester for the account private key. Every time you reload the private key into a new wallet you will generate a new delegated private key.
The original delegated private is however linked into the blockchain with the transaction you have made.
If you lost your original delegated private key only solution is disable delegated harvesting and send a new transaction linking the new delegated private key to the private key.
Thank you for your explanation, good i have found the original delegate key and private so now it would be ok i have sent a msg to change the ip with the new ip and same public key would be ok i hope
Nothing to do… please update the ip @BloodyRookie thank you
@BloodyRookie Hi BloodyRookie. I need some help on supernode https://supernodes.nem.io/details/787 . The supernode is failing for quite some time. From the logs, there are no memory/connection issues. Is there any other ways I can check for possible failure issues? Thank you in advance
Ok, which supernode is yours?
Can you paste the tx hash of the enroll message for the new entry?
Looks like it is not failing any test in round 5525. Did you restart NIS?
Why is so slow to get support on this channel?node https://supernodes.nem.io/details/621
Changed your ip manually in the db.
@BloodyRookie Hi BloodyRookie.
This node has been deactivated since they are failing every single test for a long time.
but it has satisfied the requirement again now. so, please activated again.
Thank you very much!
Hi @BloodyRookie .
please change IP of these supernodes.
change ip 126.96.36.199 to 188.8.131.52
change ip 184.108.40.206 to 220.127.116.11
I already sent enroll message to NAFUND address,
the tx hash:
Have the technical requirements for a supernode that will run on the Catapult chain been finalized yet?
No, not yet.
ip change 18.104.22.168 to 22.214.171.124
There will be a database maintenance in 2019-11-24. That means the noderewards master will be down for a while.
Sorry for the dealy, maintainance will be now