Check my public nodes at NEMNO.DE

Technical Discussion
#21

But I shut down my node out of other reasons anyway. Unless I find someone who borrow me 3m xem. I would pay for VPS 10 Euro a month just to run the node. But I won't buy 3m xem for the node reward program.


You know that those 3m could pay off...
(Unfortunatelly nothing indicates that reward program will start this month).

btw for 10eur/mo, I hope you had at least 2G ram + 40G disk space, anything below would be expensive...
#22

I added a new node and changed the host for the EU-node. Please restart your delegated harvesting.

My current public nodes:

EU.NEMNO.DE (Port 7890 | Germany, Frankfurt)
US.NEMNO.DE (Port 7890 | USA, California)

UPDATES
For more infos check the status site [url=http://nemno.de]NEMNO.DE

#23

Biggest issue on harvesting on someone else's node is you don't know if it has been restarted and you have to restart harvesting too.


Exactly! This is actually the biggest problem about delegated harvesting and it needs to be fixed in some way. I created an account on Twitter for this. [url=https://twitter.com/NEMnode]@NEMnode - I will tweet, if I restart one of the nodes. Maybe I will set up a mail-newsletter, too.
#24


Biggest issue on harvesting on someone else's node is you don't know if it has been restarted and you have to restart harvesting too.


Exactly! This is actually the biggest problem about delegated harvesting and it needs to be fixed in some way. I created an account on Twitter for this. [url=https://twitter.com/NEMnode]@NEMnode - I will tweet, if I restart one of the nodes. Maybe I will set up a mail-newsletter, too.



That's only an issue if you allow random people to harvest on your node. If not, you should just set nis.additionalHarvesterPrivateKeys.


But for reasons pat mentioned, you should really try to keep nis.unlockedLimit set to a low number (so as to not encourage people to stop running their own nodes).
#25

Yes, we discussed this on Telegram. I will add harvester's private keys, if they contact me. I also will publish a short video with some infos about delegated harvesting.

#26

I made a short video-tutorial about delegated harvesting:

[url=https://www.youtube.com/watch?v=ojxGI9xHJeM]

#27

I added a new node and changed the host for the EU-node. Please restart your delegated harvesting.

My current public nodes:

EU.NEMNO.DE (52.28.120.70 | Port 7890 | Germany, Frankfurt)
US.NEMNO.DE (52.8.163.104 | Port 7890 | USA, California)

UPDATES
For more infos check the status site [url=http://status.nemno.de]http://status.nemno.de



US.NEMNO.DE don't work also status site [url=http://status.nemno.de]http://status.nemno.de link is broken
#28

The US node works. Enter US.NEMNO.DE in your NCC as host and not the IP. IPs sometimes changes. The host US.NEMNO.DE is always routed to the correct IP.

I deactivated STATUS.NEMNO.DE - everything is visible directly at [url=http://nemno.de]NEMNO.DE

Please follow us on Twitter to get more updates. [url=https://twitter.com/nemnode]@nemnode

#29

Due to the high utilization of our nodes we increased the number of available slots from 15 to 30. Both nodes rebooted. Please restart delegated harvesting. Provide me your REMOTE private key and ask me to add it for auto-harvesting. After I added your REMOTE private key, you'll always start harvesting automatically if nodes were rebooted. Please donate for more nodes: NAEAFV-QXARWI-HTNUCE-MAXHDZ-SQCREE-PJR25G-NODE

#30

Thumbs up for your project :slight_smile:

#31

Thanks. I'm still working on the homepage [url=http://nemno.de]NEMNO.DE to make it much better. The most important thing for me right now is, to get some live infos about NEM-price, nodes-status, node-usage / free slots and other API-stuff of NEM.