NEM Supernode Rewards Program

@bloodyrookie I have a computer with enough CPU power (Intel Xeon processor) and 8GB RAM (and enough RAM laying around to upgrade) and my uplink is good enough to participate as a supernode. Though, im a little confused about the required minimum of 3 million XEM I need to have to participate. 1 XEM is currently €1,45,- So If I buy 3 million XEM i have to pay €4.350.000,- wich is about $5.254.264,-

Am I missing something? I read all those things about NEM being fare and all compared to bitcoin (Who has the most powerfull computer wins). But if you need to pay more then 5 million dollar just to participate, then ending up to earn about 320XEM a day. It takes about 9375 days (almost 26 years) before you make a profit (since you need to have the 3million XEM in your wallet at all times).

Im really confused. I am definitely missing something…

No, you are not missing something. When the supernode program started, xem was very cheap.
We didn’t change the requirements since we already have 500+ supernodes that form a very stable network.
That doesn’t mean the requirements are set in stone but for now they will not change.

You don’t need to wait 26 years to make a profit. You can withdraw from the program and pull out your 3m xem anytime so they are not lost. So it doesn’t cost you 3m xem, it’s just a stake or deposit if you will.

Hi @BloodyRookie - wanted to add my new super node in.

My enroll txHash is 5ebe99863cb73aa963307b888a2f4ad62278729762532e7f3bde366dbb9b71e5 and 3af81bc695d089d040a549a1fbe690cc500996c9a7a5aebeef3e382a1e08a834, can you please check if the TX is fine? These listed here(https://nemnodes.org/nodes/), but not listed here(https://supernodes.nem.io/map).

message has those strange chars in it which makes the bot reject the message:

enrollâ 133.130.113.123â egl01â 7d6ed3307e18175da0378920cc6679c9fff23dadd7e2426e59ea948c4e16c24b

Same here:

enroll 150.95.136.248 ika01â f715ef6b06aa13c36dc5cc68f3741f1550ccb3c8cb1b4fac36f569e1aed652ad

1 Like

hello. please change ip for my two supernodes.

name supernode Vince More. message: Change ip 84.200.16.83 to 192.169.7.145
multisig transaction: http://chain.nem.ninja/#/multisig/1d05eceba93faffafe58d6c23b6dc59c4bc98b2c3e3bf5279f44719d1e0aa609

name supernode Vince More 1. message: Change ip 84.200.210.132 to 192.169.7.134
multisig transaction: http://chain.nem.ninja/#/multisig/a0a7c9d78fa839933faaab7c445590bd8797d649d13a77e82aac315e14373a12

Hello, BloodyRookie!

I changed the values of -Xms and -Xmx to 2800M both. Have passed few rounds but again have the same problem with chain height. My last round is a

https://supernodes.nem.io/archive/839/2967

How i can solve that problem? I havent stable passes for 2 weeks.(

Thanks for yours replying.

How much RAM is the java process consuming? I mean, what is the task manager (top) showing?

Done.

Java consuming 3.060g of RAM by top.

So how long ago did you make the changes? The displayed rounds are always behind.

Just 1 day ago… It’s a very short period, right? Should wait more?

Yea, i would wait a bit longer.

Is there an API I can use to check if my supernode pasts the last round of test?

there is the /node/testResults POST request which needs a json object as body:

{
“alias”: “your_supernode”,
“roundFrom”: 123,
“numRounds”: 10
}

The returned result must be interpreted as bits:

Bit 0: nodeVersionOk
Bit 1: chainHeightOk
Bit 2: chainPartOk
Bit 3: responsivenessOk
Bit 4: bandwidthOk
Bit 5: computingPowerOk
Bit 6: pingOk
Bit 7: nodeBalanceOk

1 Like

Any reason why only reponsiveness test is failing only once in a whole week? All other tests are fine.
This is the result of the test:
Responses/Requests: 0/10
Total time: 427 ms

Total time seams ok, but no responses

Please always mention which supernode you own, there are way to many for me to remember all :wink:

https://supernodes.nem.io/history/search/Amazing-Meyns

Round 989390 and 974884

I will investigate, maybe there is a way to optimize.

Hello, i got 6-8 passes, after I changed java xms and xmx, but failed last three times with the same mistakes.

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

How i can optimize that?