Check my public nodes at NEMNO.DE

[url=http://www.nemno.de]

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

that's pretty cool !


[img width=350 height=120]http://picload.org/image/ioocorg/nemnode.png[/img]



Hi,


now I use your nemnode for delegated harvesting. I stopped my two nodes at the moment.


FireF



I had some issues when too many people were on my node, so there are 10 slots available at the moment. If I had some money for a bigger VPS, I would do it. But it's better than nothing. I'll keep you guys updated, if I restart the node or s.th. else happens.

Now I try to get status.nemno.de online.

Updates:

- The status-page is now online and will be connected to the API soon for automatic updates
- Amazon changed the IP of the node so, please restart your delegated harvesting


Updates:

- The status-page is now online and will be connected to the API soon for automatic updates
- Amazon changed the IP of the node so, please restart your delegated harvesting



NIS wasn't available (block's weren't  uptodate) today. So I switch back to my own node.




FireF

You need to restart delegated harvesting, after a node restarts. Last restart was today, because I changed the available slots from 5 to 15. Check status: [url=http://status.nemno.de/]http://status.nemno.de/

Hi,
very nice public node. It is a good way , when the own node is down for a short time.
Send some for pizza, bier or vinyl,  vinyl maybe ea80.  ;D
I hope it helps a bit !

garm

Wow! Big thanks!  :o

Next vinyl will be something from Chefdenker! :slight_smile:

Hi punk,


I'm back to use your NODE now.


So I see how it works this time and if it's good I will quite my own node.


FireF


Hi punk,


I'm back to use your NODE now.


So I see how it works this time and if it's good I will quite my own node.


FireF


This is could turn into a real problem with the remote node thing. I thought the potential trust issues would be enough for people to not jump at others nodes but it seems I was wrong :/


Hi punk,


I'm back to use your NODE now.


So I see how it works this time and if it's good I will quite my own node.


FireF


This is could turn into a real problem with the remote node thing. I thought the potential trust issues would be enough for people to not jump at others nodes but it seems I was wrong :/


As long as we use nodes just for remote harvesting there are no trust issues.
If we start to really use XEM for anything else we will need trusted nodes.

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. If you are smart you  can work it out...


Hi punk,


I'm back to use your NODE now.


So I see how it works this time and if it's good I will quite my own node.


FireF


This is could turn into a real problem with the remote node thing. I thought the potential trust issues would be enough for people to not jump at others nodes but it seems I was wrong :/



Wasn't it by design of NEM that NCC uses NIS some where on the Internet?
As far as I understood the "Mobile Clients" should also use some NIS in the Internet? So I have to have trust to node to a degree anyhow.


Since I don't now if the NCC does some integrity  checks on the data it receives. I assume that it blindly trust the value the NIS sends too it.
So the remote node could show me that I've received XEM I never received or could hide TX I did, so I may resend a TX.
But I could always use nembex to double check.
Since I use delegated harvesting, no harm for me in this case.


If punkrock or someone else could manage to get many remote harvester, it could be a Risk for the Network, but I don't see this at the Moment.


It is not easy for me to use someone else NODE because I'm paranoide, but I've to practice to work with NEM like it was designed.
And since I should my VPS down at the end of the month anyway I'll have to find a other way. One would be to run NIS on my local Computer. But since its a Macbook it's often


I shut down my host, cause I can't apply to node reward programm (don't have 3m XEM) and it doesn't feel right fro me to run a node with out any gains for me, when other will gain xem.


FireF


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. If you are smart you  can work it out...



Easy script.


[font=Verdana][size=78%]1. Connect to NIS and ask for Account status (Locked/Unlocked / No Response) of delegated Account[/font]
[font=verdana, arial, helvetica, sans-serif]If it's unlock everything is fine, if not send Mail to my self. [size=78%][/font]

[font=verdana, arial, helvetica, sans-serif]I've could write this in ruby. But currently I simply check it manually. [size=78%][/font]

[font=verdana, arial, helvetica, sans-serif]FireF[size=78%][/font]








Hi punk,


I'm back to use your NODE now.


So I see how it works this time and if it's good I will quite my own node.


FireF


This is could turn into a real problem with the remote node thing. I thought the potential trust issues would be enough for people to not jump at others nodes but it seems I was wrong :/


As long as we use nodes just for remote harvesting there are no trust issues.
...


That's true. At least until that person gets shitload of people to harvest on his nodes and starts  harvesting on his private chain which is what CfB has pointed out.



Hi punk,


I'm back to use your NODE now.


So I see how it works this time and if it's good I will quite my own node.


FireF


This is could turn into a real problem with the remote node thing. I thought the potential trust issues would be enough for people to not jump at others nodes but it seems I was wrong :/



Wasn't it by design of NEM that NCC uses NIS some where on the Internet?
As far as I understood the "Mobile Clients" should also use some NIS in the Internet? So I have to have trust to node to a degree anyhow.


Since I don't now if the NCC does some integrity  checks on the data it receives. I assume that it blindly trust the value the NIS sends too it.
So the remote node could show me that I've received XEM I never received or could hide TX I did, so I may resend a TX.
But I could always use nembex to double check.
Since I use delegated harvesting, no harm for me in this case.


If punkrock or someone else could manage to get many remote harvester, it could be a Risk for the Network, but I don't see this at the Moment.


It is not easy for me to use someone else NODE because I'm paranoide, but I've to practice to work with NEM like it was designed.
And since I should my VPS down at the end of the month anyway I'll have to find a other way. One would be to run NIS on my local Computer. But since its a Macbook it's often


I shut down my host, cause I can't apply to node reward programm (don't have 3m XEM) and it doesn't feel right fro me to run a node with out any gains for me, when other will gain xem.


FireF


Yes, that was by design and it's a good idea and necessary for mobile clients.
It becomes a problem when people shut down their nodes because they can simply use someone elses and then only a handfull of individuals run all nodes in the network and the rest of the users just piggyback on those.

Yes, that was by design and it's a good idea and necessary for mobile clients.
It becomes a problem when people shut down their nodes because they can simply use someone elses and then only a handfull of individuals run all nodes in the network and the rest of the users just piggyback on those.



Full Ack :-)
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.


FireF

Hi,
maybe the public node is open for a limited period only for every one.

garm

I love this website. And I think it's exactly a preview of the things to come.

Node rewards should help to take care of some of this. Deposits were added because it was very important to make sure one person was running hundreds of nodes as they could someday attack the network and we would have essentially paid them to do so. On the other hand we wanted to be paying enough to make sure there are lots and lots of open nodes so mobile clients can harvest.  So it's s fine balance of getting the formula right.

Eventually the free market can sort this out and a person running a nose and website might only harvest for people that tip a little bit.


Eventually the free market can sort this out and a person running a nose and website might only harvest for people that tip a little bit.


Jabo, you are obsessed by noses! :D