Thanks for prompt suppor 
Anyway, even missing server name, enroll process is no problem?
I wonder my delegated public key register properly or not?
So far it was no problem, but we will change that to enforce the name to be more than nothing / whitespace
OK, Thanks for confirmation.
Did you restart the nodes with that memory configuration?
Probably. The arguments for java in the NIS start script should be something like
-Xms640M -Xmx640M
Done. Can you test it now?
We will in a few days if the problems still occur.
are there plans to increase the reward again?
The reward is about to go sub 400 very soon.
I don’t think so.The network is strong enough imo.
BR- can you please check my supernode SydNem, i have no idea it keeps on failing.
I’ve set it up the same way i setup my other nodes.
Supplied public key when enrolling was
5cc8cfb8270b9da0e2b2d2feb34439acafbc59790a7c6fb3f93cd53836840c3c
Public key seen from NIS and servant is
f9157353f8d179931eec85e873ad6f85dcad6ae2d35c5a298ffc32d4bf296560
Please check.
The key used for both servant and enrol is:
5cc8cfb8270b9da0e2b2d2feb34439acafbc59790a7c6fb3f93cd53836840c3c
i have no idea how or why the other one is seen?
did you use the delegated private key in the config for NIS and servant?
argghh - i screwed up. i actually used my own public key.
can you please change the enrolment to this one instead:
f9157353f8d179931eec85e873ad6f85dcad6ae2d35c5a298ffc32d4bf296560
i will make the changes on my end to the config file.
no need to change the config as it already is showing the pub key
f9157353f8d179931eec85e873ad6f85dcad6ae2d35c5a298ffc32d4bf296560
So this is the real delegated public key?
yes correct. If you can change the enrolment to that key should be fix.
thanks alot. very fast response time.
You guys rock. This solidify the reason im buying more xem as the price drops.
Expect more supernodes to appear from Aus.