NEM Supernode Rewards Program

Blog Posts
#1513

Hello, I changed my account for supernode completely because on old one I used a brain wallet and it’s not secure. I sent a new message to NAFUNDBUKIOSTMD4BNXL7ZFE735QHN7A3FBS6CMY with my new delegated harvesting key “enroll (46.243.6.112) (Cryptobank1) (ab5a77f3c4455cb0477e4890064c66214906c9baa8b1d2b430f78d7d28c477c6)”. I also changed config files and restarted a node on a server. Could you please check my node status? Is everything ok?

#1514

What provider is hosting the node?
How much RAM does it have?

#1515

i will wait until the new delegated key is activated and then make a new entry in the database for your supernode.

#1516

Thanks. It already shows me that a delegated key is active. And also it shows harvesting status as active.

#1517

New db entry is

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

#1518

Hi,

Previously I have https://supernodes.nem.io/details/515

After that i made multisig acc and enroll node again with new name “xem1xem1xem”, but it was not added in the list, could you please check it.

http://chain.nem.ninja/#/multisig/2addb7cffada463cfca33285eea961279019fc799397f95163578f129447efe4

#1519

add it manually to the db:

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

#1520

Hi, what is the best way to increase computing power requirement for SN. Is it to increase RAM or CPU?

#1521

i am using this provider to setup the africa server … https://www.clickworks.co.za/

Then, i think i used 2 GB ram for the server.

Sorry for the late reply. :slight_smile:

#1522

the requirement is not that high, any 1 core vps should pass the test. Is your vps failing?

#1523

2GB should be enough. If the node continues to make trouble, maybe change provider? I use zappie host for my vpses in South Africa.

1 Like
#1525

Okay thanks :+1:

#1526

Hi, it does occasionally (recently) fail a computer power test where it goes above 5000. It’s been running fine for almost a year since I set it up, but only within the last two weeks has it failed once a week.

#1527

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

System doesn’t see balance of multisig account, how to fix it?

Thanks in advance

#1528

seems the public key you have given is not correct?

http://chain.nem.ninja/#/multisig/2addb7cffada463cfca33285eea961279019fc799397f95163578f129447efe4

public key: c3106ff669b9f7da83df317edef0ad89f476d3fa3794beb9b2b83c1ca72670a5

but there corresponding main account is empty:

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

#1529

I see different public delegated keys.

  1. Main multisig acc - public delegated key1
  2. 1st cosig of main --> manage delegated account of multisig accounts --> public delegated key2
  3. 2nd cosig of main --> manage delegated account of multisig accounts --> public delegated key3
  4. 3th cosig of main --> manage delegated account of multisig accounts --> public delegated key4

I have 4 different public delegated keys, which one should specify?

Thanks

#1530

@BloodyRookie
why my 2 suppernodes show as “deactivated”?

http://52.42.99.254:7890/node/extended-info
"name":“opensesame”

http://52.2.187.5:7890/node/extended-info
"name":“bue.twitter”

{“node”:{“metaData”:{“features”:1,“application”:null,“networkId”:104,“version”:“0.6.93-BETA”,“platform”:“Oracle Corporation (1.8.0_101) on Linux”},“endpoint”:{“protocol”:“http”,“port”:7890,“host”:“52.42.99.254”},“identity”:{“name”:“opensesame”,“public-key”:“0f44e209db7d2d668111020986b069353b2cd7ac3905415716a466072961f549”}},“nisInfo”:{“currentTime”:76784429,“application”:“NEM Deploy”,“startTime”:76142023,“version”:“0.6.93-BETA”,“signer”:null}}

#1531

Main account’s public delegated key.

#1532

when i deactivated them, they had the old version 0.6.91 and thus failed.
I activated them again.

#1533

So I specified correct public delegated key.

how to fix it?)