NEM Supernode Rewards Program

Blog Posts
#404

The following nodes have been disabled due to extensive failure:

#405

Yay, after supernoding for about two months, I got my first payout today!

#406

@teletobi75: won’t be the last one :slight_smile:

#407

In the last test of my new supernode nr 182 (penter) is failing only balance.
Seems to me a wrong key is entered somewhere and doesn’t see the actual balance of the main account. I double checked this however and it should be the correct key entered. Anything else I could be missing?

Also my other supernode (nr 96 meyns) apparently the delegeted keys have changed since I began the supernodes program, if I look at the delegated keys, they are different then when I first entered them in the supernode config file). Is this possible?
Also I am not harvesting any block, althout delegated harvesting is active.

#408

There is indeed no balance on that account:

http://alice2.nem.ninja:7890/account/get/forwarded/from-public-key?publicKey=b1965872a5a46ebec386b18dbe173983b6140d9d61f3754ac600aef56326f738

Check the public key you have supplied again

I don’t think that is possible and aside from that, the node points to an account with enough balance:

http://alice2.nem.ninja:7890/account/get/forwarded/from-public-key?publicKey=02dc16066e8a4694ccae1d73547d76c27dcfa1df74e41f92a0bd36730db4b48f

#409

Am I looking at the wrong data then?

Edit:
According to nembex my delegated harvesting account is not the same as the one that the client is giving me: http://chain.nem.ninja/#/search/NAQ7AC-UBA6PL-KPDWOJ-FMZN7T-RXS7UM-EEM6O7-JD6J

#410

Yea, i checked on nembex and there seems to be a problem with the delegated key. Did you re-import your account into a new wallet? Then the delegated key changes.

#411

I installed the latest version 0.6.77 over the old version 0.6.75 without uninstalling.
Edit: No i reĂŻmported the address previously. Tried that again and it does change the delegated adress.

#412

@meyns: so you supplied the wrong delegated key for the new node. You can either deactivate delegated harvesting and 6 hours later reactivate it again (it will then use the delegated key that the wallet is using for the account), Or i can deactivate the node in the db and manually add a new entry with the correct delegated public key. But in the latter case you would have to change the config and use the old delegated private key in the config. Not sure if you still have that key.
I think the former (deactivate/activate delegated harvesting) is safer.

#413

Damn, I thought that having the private key of the main account, you would also have the data available of the delegated account.
Deactivating right now.

#414

How does it happen that 70k divided by daily payout is most the time a double instead of int? Are you rounding?

#415

@haggis: yes, rounded to integer type. I mean 70k/#nodes is rounded.

#416

BloodyRookie, Can you update the delegated public key to: (for server “penter”)
3f3e0d79a42997257ce8a492d4fc2078d72e0b905087c70e2426c0513e0121db

#417

@meyns: i thought you simply deactivated/activated the delegated harvesting on that account? how come it got a new public key?

#418

Probably because I tested when a new delegated account is created, so I deleted the account and imported it again using the private key. So I got a new delegated account (which is different than my screenshot).

I did deactivate/activate delegated harvesting, with the new imported account.
Thats the public key of the new delegated account.

#419

@meyns: ok, since the pub key changed i need to deactivate the old node and add a new entry manually in the db.

#420

Ok, thx

#421

@meyns: done

#422

What happened with round 736, I failed it and strangest thing was fail with version. I’m sure I’m running the latest, as other round went through without any problem? Supernode http://supernodes.nem.io/details/14

#423

@martismartis: not sure what was wrong with round 736. Maybe the data center where your vps lives had problems?