NEM Supernode Rewards Program

[KloNEM]

Hi, neverminded, was the change (to -Xms3G -Xmx3G) successful for you ? There is absolutely the same problem by me – I have “rock solid” node, passed all the test for couple of months, 16GB RAM (just on Linux), and last week I have repeatedly troubles with Height and Chain part in the measuring (and thus my node is failing the tests). Upgrade from 0.6.93 to 0.6.95 doesn’t solve the situation.

[BloodyRookie]

Hi, neverminded, was the change (to -Xms3G -Xmx3G) successful for you ?

I guess it was since he didn’t state the opposite

[BloodyRookie]

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

My enroll txHash is d795a292f97f9108301868090cbb54d166a351ec7929c80a0808fc967ddfe6e6, can you please check if the TX is fine?

I added the new entry:

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

[janikjan]

Hi @BloodyRookie I have just sent to your NEM account message to change my NEM supernode ip.
So please change ip 185.185.41.105 to 185.185.40.67

Thanks!

[BloodyRookie]

Hi @BloodyRookie I have just sent to your NEM account message to change my NEM supernode ip.

So please change ip 185.185.41.105 to 185.185.40.67

Was changed automatically by the bot.

[BloodyRookie]

Version 0.6.95 is available:

NEM Beta 0.6.95

Happy New Year to everyone NEM Beta 0.6.95 Changes: 1) Merged pull request from Alvin: adds some new API Ids to nem.core so you can use those requests programatically. upgrades bouncy castle library version from 1.50 to 1.58. upgrades HttpAsyncClient version from 4.1.1 to 4.1.3. 2) Namespaces / Mosaics: fix various bugs in the NIS Api for retrieving namespaces / mosaics. fix bug that let mosaics disappear if associated root namespace was renewed during the grace period. 3) Spam Filter: sepa…

Please upgrade your supernode to have at least 4GB RAM. Generally the more RAM the supernode has, the better it is. Also don’t forget to adjust the java startup params. If you have 4GB available for the node you should set

-Xms2800M -Xmx2800M

in the startup script (which is nix.runNis.sh by default)

[ninjaboon]

My enroll txHash is d795a292f97f9108301868090cbb54d166a351ec7929c80a0808fc967ddfe6e6

@BloodyRookie

New enroll txHash is 29023810ddc98dfadaa89d3ad7ad444ef21387b7cdcf25024a2e3a45fd784d59 for another new node ninja2016, can you please check if the TX is fine?

• thanks for the earlier addition for ninja3. it works.

[BloodyRookie]

new node ninja2016, can you please check if the TX is fine?

New entry is

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

[himmelsfaller]

@BloodyRookie
Hey BR. My 103.192.177.252 has also only 2 GB RAM and is failing again and again
I just asked HostUS to give me another node with 4 or 8 GB.
It may take a day until it is paid and running and I’ve a new IP.
Thanks

[romawi]

Please upgrade your supernode to have at least 4GB RAM. Generally the more RAM the supernode has, the better it is. Also don’t forget to adjust the java startup params. If you have 4GB available for the node you should set

-Xms2800M -Xmx2800M

in the startup script (which is nix.runNis.sh by default)

I thought that was the nisStart.sh. Then I know why this does not work for me

[BloodyRookie]

I thought that was the nisStart.sh. Then I know why this does not work for me

i don’t know about your setup on your supernode. How do you start NIS?

[hoorai]

Hello, how i can solve the problem with Chain height?
I have that problem 4 times in a row. And last time https://supernodes.nem.io/archive/839/2960 i had really strange value of Chain height. But last check of chain height in logs looks like
2018-01-04 09:27:21.510 INFO block height: 1444724 (org.nem.nis.service.PushService m)
2018-01-04 09:27:21.510 INFO isLastBlockParent? true; last block height: 1444723; hash: 012e6ff56ef3434575ecd1df0b04c701b69028eabcde83fd9b6f7d2bd0d732e6 (org.nem.nis.BlockChain a)

What i did wrong>?

[BloodyRookie]

Hello, how i can solve the problem with Chain height?

See my post above:

Please upgrade your supernode to have at least 4GB RAM. Generally the more RAM the supernode has, the better it is. Also don’t forget to adjust the java startup params. If you have 4GB available for the node you should set

-Xms2800M -Xmx2800M

in the startup script (which is nix.runNis.sh by default)

[Ezzar]

@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…

[BloodyRookie]

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.

[awu25]

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.

[HamTaro]

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).

[BloodyRookie]

5ebe99863cb73aa963307b888a2f4ad62278729762532e7f3bde366dbb9b71e5

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

enrollâ 133.130.113.123â egl01â 7d6ed3307e18175da0378920cc6679c9fff23dadd7e2426e59ea948c4e16c24b

3af81bc695d089d040a549a1fbe690cc500996c9a7a5aebeef3e382a1e08a834

Same here:

enroll 150.95.136.248 ika01â f715ef6b06aa13c36dc5cc68f3741f1550ccb3c8cb1b4fac36f569e1aed652ad

[Vince_More]

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

[hoorai]

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.