NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs

[BloodyRookie]

Take a look at my account from which I am donating XEM to harvesters:



It got less than 15k vested XEM. So with a pure POS algorithm the account would have a chance of about 15000 / 9000000000 = 0.0167%oo to harvest a block.
Yet it really has 0.8%oo which is 48 times higher. Seems POI likes what I am doing

[Come-from-Beyond]

I believe he pressed [Ignore] right after that post.

[zanzibar]

The last person you want involved with NEM is Smaragda.  His adderall induced posts are the antithesis of good marketing.  

Of course...  now they're coming back with their sock-puppets...  


@xtester

That's what you get for being a FUCKIN' HYPOCRITE...  

I have nothing against you personally, I just think your drug fueled rants are bad for a general thread.

[Come-from-Beyond]

Topic switcher

[punkrock]

Could you please answer the question instead of spamming this thread with this smeagol-stuff? Thanks. And thanks for the "ignore"-function reminder. Used it right now!

As a BTT-stakeholder, can I already claim my stake now or is there nothing new since launch?

[s11made]

https://docs.google.com/document/d/1TKTIakxUEotmTN4Et80EI7d-8XifgFZ4aBUGAukgLfY/edit?pli=1#heading=h.xchkdqowarsb

Interesting document. What percent of the total coins do the devs control? It's less than 50%, isn't it?

That's what I want to know. And possibly if the addresses are public so we can see what happens with the funds.
All coins not issued to individuals in the beginning should be able to trace as transparently as possible, so we know everything is okay.
As I see it at the moment, ~5.6billion coins (around 60% of the total coins are controlled by community fund manager + devs) And at the moment it is not very clear who these community fund managers are or will be, since there is no mention in the document.

But I am sure these questions have all been answered already. I'd appreciate a link to this information.
Thanks

[himmelsfaller2]

an hour ago I restartet my computer because NIS was not available. after that I tried to start NCC in browser and had a new wallet in my nem ncc directory böser dämon is the wallet called: B%C3%B6ser+D%C3%A4mon.wlt
and NIS is not available since then. Maybe I got hacked because how could be a wallet in my ncc directory, which is not my wallet?

[klintay]

Does the client have to be open and running on your PC to harvest?

[Tompa]

Does the client have to be open and running on your PC to harvest?

Not if you are doing remote harvesting...

http://blog.nem.io/how-to-use-delegated-harvesting/

[instacalm]

an hour ago I restartet my computer because NIS was not available. after that I tried to start NCC in browser and had a new wallet in my nem ncc directory böser dämon is the wallet called: B%C3%B6ser+D%C3%A4mon.wlt
and NIS is not available since then. Maybe I got hacked because how could be a wallet in my ncc directory, which is not my wallet?

Hi himmelsfaller! Sites like nodeexplorer.com expose your IP address. With this information anyone could try opening NCC over the web via http://xx.xx.xx.xx:8989/ncc/web/index.html.

Chances are someone accessed your NCC and created that new wallet. When running a public node, it's best not to have NCC running (running NIS with unlocked account is all you need to keep harvesting) or change its port to something unique only you know. I could imagine that NIS is not available because the same person specified a remote server (probably non-available one), which is why your NIS doesn't boot/refuses booting.

In NCC, go to Settings and see what is specified. Change it back to your previous settings (default is 127.0.0.1 and default port checked).

If you have harvesting activated, you can go ahead and close NCC. Then simply keep NIS running. It is actually kind of a flaw that NIS can easily be made unavailable simply via NCC's front page at this point. I wanted to point this out earlier but you reminded me. Hope that helps.

[Come-from-Beyond]

http://blog.nem.io/how-to-use-delegated-harvesting/

This reminded me that the issue related to completely trust-free harvesting is still there. By protecting every single participant you make the whole system more vulnerable. If automatic fee transfering was removed then small fish would start to care whom they give the power of delegated harvesting to. I haven't seen an explanation why it's not an issue yet.

[himmelsfaller2]

an hour ago I restartet my computer because NIS was not available. after that I tried to start NCC in browser and had a new wallet in my nem ncc directory böser dämon is the wallet called: B%C3%B6ser+D%C3%A4mon.wlt
and NIS is not available since then. Maybe I got hacked because how could be a wallet in my ncc directory, which is not my wallet?

Hi himmelsfaller! Sites like nodeexplorer.com expose your IP address. With this information anyone could try opening NCC over the web via http://xx.xx.xx.xx:8989/ncc/web/index.html.

Chances are someone accessed your NCC and created that new wallet. When running a public node, it's best not to have NCC running (running NIS with unlocked account is all you need to keep harvesting) or change its port to something unique only you know. I could imagine that NIS is not available because the same person specified a remote server (probably non-available one), which is why your NIS doesn't boot/refuses booting.

It is actually kind of a flaw that NIS can easily be made unavailable simply via NCC's front page at this point. I wanted to point this out earlier but you reminded me. Hope that helps.

thanks that helps a lot. I will do what you recommend. thanks again!

[iaminitnow06]

an hour ago I restartet my computer because NIS was not available. after that I tried to start NCC in browser and had a new wallet in my nem ncc directory böser dämon is the wallet called: B%C3%B6ser+D%C3%A4mon.wlt
and NIS is not available since then. Maybe I got hacked because how could be a wallet in my ncc directory, which is not my wallet?

Hi himmelsfaller! Sites like nodeexplorer.com expose your IP address. With this information anyone could try opening NCC over the web via http://xx.xx.xx.xx:8989/ncc/web/index.html.

Chances are someone accessed your NCC and created that new wallet. When running a public node, it's best not to have NCC running (running NIS with unlocked account is all you need to keep harvesting) or change its port to something unique only you know. I could imagine that NIS is not available because the same person specified a remote server (probably non-available one), which is why your NIS doesn't boot/refuses booting.

In NCC, go to Settings and see what is specified. Change it back to your previous settings. If you have harvesting activated, you can go ahead and close NCC. Then simply keep NIS running.

It is actually kind of a flaw that NIS can easily be made unavailable simply via NCC's front page at this point. I wanted to point this out earlier but you reminded me. Hope that helps.

This is a problem. Please view this youtube video- https://www.youtube.com/watch?v=cbFiWeeMUDI. And then block the port 8989 to be rather safe than sorry. Everybody should block the port 8989 in the inbound and outbound rules.

[ciappa]

an hour ago I restartet my computer because NIS was not available. after that I tried to start NCC in browser and had a new wallet in my nem ncc directory böser dämon is the wallet called: B%C3%B6ser+D%C3%A4mon.wlt
and NIS is not available since then. Maybe I got hacked because how could be a wallet in my ncc directory, which is not my wallet?

Hi himmelsfaller! Sites like nodeexplorer.com expose your IP address. With this information anyone could try opening NCC over the web via http://xx.xx.xx.xx:8989/ncc/web/index.html.

Chances are someone accessed your NCC and created that new wallet. When running a public node, it's best not to have NCC running (running NIS with unlocked account is all you need to keep harvesting) or change its port to something unique only you know. I could imagine that NIS is not available because the same person specified a remote server (probably non-available one), which is why your NIS doesn't boot/refuses booting.

In NCC, go to Settings and see what is specified. Change it back to your previous settings. If you have harvesting activated, you can go ahead and close NCC. Then simply keep NIS running.

It is actually kind of a flaw that NIS can easily be made unavailable simply via NCC's front page at this point. I wanted to point this out earlier but you reminded me. Hope that helps.

Changing the port, i become this error:

ERROR 305

The NEM Infrastructure Server (NIS) is not available. Try to restart the NEM software. If you are using a remote NIS, check your configured host for typing errors or use another remote NIS.


as soon as i turn back to default port, nis turns available...

[amytheplanarshift]

an hour ago I restartet my computer because NIS was not available. after that I tried to start NCC in browser and had a new wallet in my nem ncc directory böser dämon is the wallet called: B%C3%B6ser+D%C3%A4mon.wlt
and NIS is not available since then. Maybe I got hacked because how could be a wallet in my ncc directory, which is not my wallet?

Someone did the same to me because I had port 8989 open. Close this port and you should be fine. As long as you have a strong wallet password you are safe anyway, but it's best to close this port.

[instacalm]

Changing the port, i become this error:

ERROR 305

The NEM Infrastructure Server (NIS) is not available. Try to restart the NEM software. If you are using a remote NIS, check your configured host for typing errors or use another remote NIS.


as soon as i turn back to default port, nis turns available...

Well, this is because your NIS booted with the default port. Now you're trying to connect to a different port but nothing's there. If you want to boot NIS with a port other than default, you have to change the config file @ path-to-nem/nis/config.properties. You'll find nem.httpPort = 7890 and nem.httpsPort = 7891 in that file. Change the values, then restart NIS.

BUT you probably wanted to change the port of NCC, did you? head over to path-to-nem/ncc/config.properties, change nem.httpPort = 8989 and nem.httpsPort = 9090 to the port(s) you wish to use & reboot the NEM software.

OR to simply restrict outside access to port 8989, do as amytheplanarshift suggested above, block the port.

@ciappa: Entschuldige, falls das verwirrend wirkt. Wenn du lediglich nicht möchtest, dass jemand "von außen" dein NCC aufrufen kann, dann blockiere via Firewall den Port 8989 (der Port über den der Nem-Community-Client standardmäßig läuft).

[iaminitnow06]

thx instaman, now I actually understand this software some more...
frankly I didn't get what nis and ncc is or mean earlier or why this seperation exists in the first place (lol, i'm not the tech savviest around).
I didn't know NIS is enough to be harvesting. now I know
but I think many new users will just be running nis+ncc on default port. isn't that a real issue for the network? I mean you said if ncc can be accessed then nis can be crashed!? you guys should fix that somehow.
 

It is a problem but rather a small one  . Please view this youtube video- https://www.youtube.com/watch?v=cbFiWeeMUDI. And then block the port 8989. This will ensure that nobody can remote access your NCC. Everybody should block the port 8989 in the inbound and outbound rules.

[klintay]

Changing the port, i become this error:

ERROR 305

The NEM Infrastructure Server (NIS) is not available. Try to restart the NEM software. If you are using a remote NIS, check your configured host for typing errors or use another remote NIS.


as soon as i turn back to default port, nis turns available...

Well, this is because your NIS booted with the default port. Now you're trying to connect to a different port but nothing's there. If you want to boot NIS with a port other than default, you have to change the config file @ path-to-nem/nis/config.properties. You'll find nem.httpPort = 7890 and nem.httpsPort = 7891 in that file. Change the values. Then restart NIS and do the same you tried earlier: change the port in your NCC according to what you just specified.

BUT you probably wanted to change the port of NCC, did you? head over to path-to-nem/ncc/config.properties, change nem.httpPort = 8989 and nem.httpsPort = 9090 to the port(s) you wish to use & reboot the NEM software.

OR to simply restrict outside access to port 8989, do as amytheplanarshift suggested above, block the port.

@ciappa: Entschuldige, falls das verwirrend wirkt. Wenn du lediglich nicht möchtest, dass jemand "von außen" dein NCC aufrufen kann, dann blockiere via Firewall den Port 8989 (der Port über den der Nem-Community-Client standardmäßig läuft).

good tip, i just changed my default ports too 

[Tompa]

thx instaman, now I actually understand this software some more...
frankly I didn't get what nis and ncc is or mean earlier or why this seperation exists in the first place (lol, i'm not the tech savviest around).
I didn't know NIS is enough to be harvesting. now I know
but I think many new users will just be running nis+ncc on default port. isn't that a real issue for the network? I mean you said if ncc can be accessed then nis can be crashed!? you guys should fix that somehow.
 

It is a problem but rather a small one  . Please view this youtube video- https://www.youtube.com/watch?v=cbFiWeeMUDI. And then block the port 8989. This will ensure that nobody can remote access your NCC. Everybody should block the port 8989 in the inbound and outbound rules.

Thanks. Blocked 8989

[greentea]

thx instaman, now I actually understand this software some more...
frankly I didn't get what nis and ncc is or mean earlier or why this seperation exists in the first place (lol, i'm not the tech savviest around).
I didn't know NIS is enough to be harvesting. now I know
but I think many new users will just be running nis+ncc on default port. isn't that a real issue for the network? I mean you said if ncc can be accessed then nis can be crashed!? you guys should fix that somehow.
 

It is a problem but rather a small one  . Please view this youtube video- https://www.youtube.com/watch?v=cbFiWeeMUDI. And then block the port 8989. This will ensure that nobody can remote access your NCC. Everybody should block the port 8989 in the inbound and outbound rules.

Thanks. Blocked 8989

how to block port 8989 on a Mac?