Hi,
Just like NXT, I'm going to make a Public NEM node. It'll be accessible by it's standard ports, as well as via port 80 (using HTTP Proxy).
I know I read somewhere NEM distribution mentioning there'll be rewards for Public NEM nodes.
1. Have those rewards already started?
2. If now, when public nodes will be rewarded?
3. To get rewarded as Public node, is there anything needs to be done? example: giving or submitting Public node info to NEM admins or devs etc, so that public node gets rewarded?
I'll be creating this Public node on 1GB RAM VPS.
4. Do you think 1 GB RAM will be enough to run NEM Node? In my experience NXT node is running fine on 1 GB RAM VPS.
5. What are NEM experts opinion on allowing multiple harvesting on Public NEM Node? I can configure NEM node to allow multiple accounts to harvest.
6. Is there any recommended number to allow multiple harvesting on Public NEM Node?
On my NXT Node, I added hallmark generated for my NXT address.
7. Is there anything related to "hallmark" in NEM. To my little experience with NEM, I don't think so. But, still it's good to confirm to make better NEM Node.
8. Can you point me to any recommended Public Node post, thread, guide or how to?
Right now I just have some idea to tweak and optimize Java, and opening ports of NIS/NCC.
Cheers!
Satinder 
We have a forum especially for nodes here
https://forum.ournem.com/vps-nodes/
Not much there yet, but it sounds like you have experience. Maybe you could add something.
Node rewards have not been implemented yet. Sometime soon I hope.
NEM uses more memory than NXT. 1G is fine if you have enough swap memory. 1G swap is good.
I spoke to gimre today about multiple accounts harvesting on a node. At this time, it is suggested to limit to ten accounts.
The bootKey is your hallmark. This is a sha256sum hash or your accounts priv-key
Never use your real private key on a VPS.
Enable remote harvesting, it takes about 6 hours to be in effect. The click on the little cog next to your account name.
You have the option of getting your remote account private key. Use that as a boot key.
The remote account has nothing in it, but it has the full POI of your real account.
Access the VPS by the settings on the first page of NCC
I have made a few scripts that make it easy to set up a linux node. I will be changing the script today because of some changes in the nis server. But they still work well.
Thanks @jadedjack!
I have setup my VPS. Dedicated to NEM only.
I just checked every NEM account also has another set of NEM Address/Public Key/Private Key specially for remote. Like my original NEM account wears a mask go went dancing in public without any risk of losing XEMs!! (Please correct me if I don't get it right).
That's a damn good feature! I didn't understood it before setting up. Now I got it a bit.
So, I have setup my Remote Priave Key on VPS NIS Node, booted NIS successfully with it.
And clicked on 'Activate Deligate Harvesting', and waiting for 6 hours to complete.
So, that means when I click on "Start Deligate Harvesting" when that button will be available, it will just start the harvesting on my remote server? If so, that's sweet!!! :D
Also, I'll have some experience troubleshooting and stabilizing my pubic node by the time NEM community decides and starts rewarding NEM Public nodes! ;)
Just one more question.
Does a stable online public node of NEM helps improving Importance of an account??
That'd be awesome if it does! ;D
Cheers :)
Does a stable online public node of NEM helps improving Importance of an account??
That'd be awesome if it does! ;D
Cheers :)
Nope.
Theoretically it will once node rewards have started because your balance will increase but it's not like Proof of Network or whatever people are calling it.
Does a stable online public node of NEM helps improving Importance of an account??
That'd be awesome if it does! ;D
Cheers :)
Nope.
Theoretically it will once node rewards have started because your balance will increase but it's not like Proof of Network or whatever people are calling it.
right.
node rewards won't actually be a part of the POI at all, but the end result will be the same as the proof of network or whatever it is called these days. Run a node = get a nice bonus. (which as Pat said will probably indirectly help your POI a little)
Thanks for clearing that up.
It's been more than 6 hours now, and my account has started showing "Start Deligated Harvesting" button.
I'm getting an error starting up harvesting using that button. It's giving me error 306.
Here's what happened:
* I did setup VPS on remote location when I was in office. Just setup NIS on VPS, and NCC on my office computer.
* Connected by office NCC to VPS NIS. The port is not default of NIS due to firewall restrictions in office, so NIS connects on port 8080. There's no redirection etc on server, it's just configuration change in NIS.
* I also updated maximum allowed harvesting accounts on NIS through configuration and that's set to 3.
* The NEM account which I imported to Office computer NCC has also Remote Account Address/Public Key/Private Key. I configured the Remote Private Key in VPS NIS server to boot it up using that and NIS boots successfully.
* VPS NIS node is set to false to auto start harvesting with the configured private key account.
* I already had my NEM account setup at home computer, and it was already harvesting locally. So, when I imported my NEM account's private key to Office NCC client I did not start "local harvesting". I just clicked on 'Activate Deligated Harvesting" as it was connected to remote NIS server. My Office computer is off since I came home.
* Now, after 6 hours at my home computer my account now shows button "Start Deligated Harvesting as expected. At home computer I have both NIS and NCC local.
* I clicked on "Start Deligated Harvesting" gave my password and getting this error:
Oops!
ERROR 306
An error occurred that the development team did not have foreseen. Apologies for this, maybe a retry might help. Otherwise, please open up an issue within the NEM NIS/NCC community.
* Thought it's because I'm not connected to remote server which I setup and started with my Remote Private Key, I connected NCC to my VPS NIS Node and again tried to start deligated harvesting, and again I got the same error.
* I also tried stoping my home computer's NIS and connecting NCC to VPS NIS node and started deligated harvesting. Again that same error.
Could you please help me troubleshoot it? At which step I did mistake?
I can't spot an error on your side. Of course its clear that you should connect to your remote NIS (your VPS) first, before you start delegated harvesting. Otherwise your local NIS will do the harvesting and that is not what you want.
To give us more information, it could be helpful to see your NIS config.properties (you can just delete a big part of your bootkey).
And it could also help to see your NIS log. But for now, I have no idea what it could be. Of course you could try to just restart NIS on your VPS, but that wouldnt help us to spot the reason probably 
the two main things I check for is that the firewall and router are both open.
other problems might be your antivirus.
really with so many kinds of internet connections it is hard to know.
it also can take 5-10 minutes to see your name on Nembex sometimes too