NXT :: descendant of Bitcoin - Updated Information

[nexern]

Good morning, guys. Someone is attacking the network trying to disrupt it. Read my post - https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526

have had the same problems with nxt-bce last night.

badMessage: java.lang.IllegalStateException: too much data after closed for ...
badMessage: 400 Illegal character for HttpChannelOverHttp@235eb171{r=0,a=ID ...

the explorer was also flooded with bot api requests, not from local fetcher.
changed to 0.3.14. and now it seems better. i tried to bind allowedBotHosts
to localhost but this doesn't work. is there any additional tag i have to set?
(otherwise i could solve this via iptables)

ps: cfb, anything we can do to support you against the hackers?

[1714045121]

1714045121

[Jean-Luc]

Good morning, guys. Someone is attacking the network trying to disrupt it. Read my post - https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526

Yes, and seems like our networking is too dependent on the bootstrap nodes. Last night fluke.airdns.org crashed with the java process exceeding the 1024 number of open files limit. At that point it had more than 400 active peers. I increased the open files limit to 16384 and restarted, this morning it had crashed again. Right now it is at 200 active peers, will see how long it lasts.

[jackyrozario]

localhost/7875    does not connect ,so I deleted the *.nxt files and rename *.bak to *.nxt.   but stll the same ,

I am Running 0.3.14 with newest JRE on W8.

Try http://localhost:7874 or https://localhost:7875

http://localhost:7874 connects but 8000 more NXtcoins are not there but rest of the coins are there....,plz help.

[nexern]

Good morning, guys. Someone is attacking the network trying to disrupt it. Read my post - https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526

Yes, and seems like our networking is too dependent on the bootstrap nodes. Last night fluke.airdns.org crashed with the java process exceeding the 1024 number of open files limit. At that point it had more than 400 active peers. I increased the open files limit to 16384 and restarted, this morning it had crashed again. Right now it is at 200 active peers, will see how long it lasts.

yes, have raised ulimit too, running with 300+ peers fine now.
do you have any additional/usefull port restrictions to protect your node?

[Come-from-Beyond]

Good morning, guys. Someone is attacking the network trying to disrupt it. Read my post - https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526

have had the same problems with nxt-bce last night.

badMessage: java.lang.IllegalStateException: too much data after closed for ...
badMessage: 400 Illegal character for HttpChannelOverHttp@235eb171{r=0,a=ID ...

the explorer was also flooded with bot api requests, not from local fetcher.
changed to 0.3.14. and now it seems better. i tried to bind allowedBotHosts
to localhost but this doesn't work. is there any additional tag i have to set?
(otherwise i could solve this via iptables)

ps: cfb, anything we can do to support you against the hackers?

Use http://myserver.com:7874/nxt?requestType=getMyInfo, put value of "host" into allowedBotHosts.

PS: I'm preparing a long post about 0.3.15, will post it very soon. 0.3.15 is a "migration" version to prepare the network for 0.3.16 that will have a special defense against cancer nodes.

[Jean-Luc]

yes, have raised ulimit too, running with 300+ peers fine now.
do you have any additional/usefull port restrictions to protect your node?

Not really, it is behind a vpn which effectively acts as a firewall, the only ports forwarded are 7874 and 7875. And there is nothing but Nxt running on it, with -Xmx3584M.

[Come-from-Beyond]

Good morning, guys. Someone is attacking the network trying to disrupt it. Read my post - https://bitcointalk.org/index.php?topic=345619.msg3856526#msg3856526

Yes, and seems like our networking is too dependent on the bootstrap nodes. Last night fluke.airdns.org crashed with the java process exceeding the 1024 number of open files limit. At that point it had more than 400 active peers. I increased the open files limit to 16384 and restarted, this morning it had crashed again. Right now it is at 200 active peers, will see how long it lasts.

Aye, we depend on bootstrapping nodes. Luckyly if a node got a list of other public nodes it doesn't depend on the bootstrappers anymore. In the future I'm planning to implement a special fallback mechanism that will let to connect to nodes unreachable from the Internet.

[bybitcoin]

Any update on when the 3.15 will be release?
Totally locked with 3.14, stuck at block 9157, only generates incorrect blocks and the balance is sometimes 0 and sometimes the actual one

[Come-from-Beyond]

Version 0.3.15 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip

Some major changes, so read it carefully.


The list of well-known peers is not hardcoded in 0.3.15. Look at "wellKnownPeers" in nxt/webapps/root/WEB-INF/web.xml. Feel free to change it.


Added "myHallmark" in web.xml. If u r an owner of non-trivial amounts in NXT u should run ur own node(s) accessible on the Internet to protect the network. Hallmark is used to mark such nodes. More on this below:

1. Launch ur node.

2. Do http://88.198.210.245:7874/nxt?requestType=getMyInfo request to any other node to get ur host value. The request must be sent from the host that runs Nxt soft. U can bypass this step if u already know ur host.

3. Do such a request: http://localhost:7874/nxt?requestType=markHost&secretPhrase=MY_SECRET&host=MY_HOST&weight=HOST_WEIGHT&date=CURRENT_DATE

MY_SECRET should be replaced with the secret phrase of ur account (more coins it has - better it is)
MY_HOST - ur host
HOST_WEIGHT - "weight" of the host, u can have a lot of hosts marked with the same account, weight defines what part of the balance will be used (weight/Sum_of_all_weights). If u have only 1 node then it will use 100% of the balance
CURRENT_DATE - a date in "yyyy-mm-dd" notation. Use the same date for all ur nodes. If u use other date then all hallmarks set in the past will be invalidated.

An example:
http://localhost:7874/nxt?requestType=markHost&secretPhrase=123&host=88.198.210.245&weight=1000&date=2013-12-07

4. Copy hallmark value into "myHallmark" in web.xml.

U can decode ur hallmark by doing such a request: http://localhost:7874/nxt?requestType=decodeHallmark&hallmark=HEX_STRING. The hallmark does NOT contain ur private key (only public one and signature).

NB: U should update to 0.3.15 within next 2 days!

[salsacz]

great job, as always

[klee]

Hey CfB can you clarify something please?

If u r an owner of non-trivial amounts in NXT u should run ur own node(s) accessible on the Internet to protect the network.

So if I run a local client should I make all these steps?
If I use a bootstrap node am I more vulnerable to attacks?

[bybitcoin]

Do we need to attach the same nxtfiles.zip file into this new 3.15 too? Or it can work independently?

About the hallmark do I really need it even if my account is usually offline and not much of in the mining mode?

[Come-from-Beyond]

So if I run a local client should I make all these steps?
If I use a bootstrap node am I more vulnerable to attacks?

Is ur local client visible from the outside? Does it have static IP or domain? If "yes" then "yes".
What do u mean "If I use a bootstrap node"?

[Come-from-Beyond]

Do we need to attach the same nxtfiles.zip file into this new 3.15 too? Or it can work independently?

About the hallmark do I really need it even if my account is usually offline and not much of in the mining mode?

0.3.15 supplied with the most recent *.nxt files. But u should always rewrite them with ur own ones (if u have any).

It doesn't matter if u account offline. If u have a node visible on the Internet then u should "mark" it. Doing so will increase stability of ur own node as well.

[starik69]

Sorry, didn't understand a bit What is Hallmark? What are weights? What should i do if i own >1M NXT, want to mine but i am behind NAT?

[Jean-Luc]

Is there an API to verify whether a node has been marked, and with what account? Or to retrieve the node hallmark?

The node on which an account is unlocked (in order to mine) doesn't need to be marked, and a marked node doesn't need to have the account unlocked, correct?

If one marks a node, which is not behind a vpn, an attacker can correlate the marking account with the node IP, thus compromising your anonymity, correct?

[Come-from-Beyond]

Sorry, didn't understand a bit What is Hallmark? What are weights? What should i do if i own >1M NXT, want to mine but i am behind NAT?

If u behind NAT then u can do nothing atm.

Hallmark is used to set weights to nodes according to amounts tied to them. It's like a reputation system based on proof-of-stake. A hacker can run thousands of nodes but without a big amount of coins in his possession such nodes will be ignored.

[Come-from-Beyond]

Is there an API to verify whether a node has been marked, and with what account? Or to retrieve the node hallmark?

No. I'll add it into 0.3.16. PM me with the details if u wish.

The node on which an account is unlocked (in order to mine) doesn't need to be marked, and a marked node doesn't need to have the account unlocked, correct?

Marked node doesn't need an unlocked account. But a node with unlocked account doesn't get a hallmark automatically (in current implementation).

If one marks a node, which is not behind a vpn, an attacker can correlate the marking account with the node IP, thus compromising your anonymity, correct?

What do u mean "correlate"? Soft checks real host of a peer. An attacker can't just say "I am 88.198.210.245".

Got it. Yes, this compromises anonymity.

[starik69]

Got it. Yes, this compromises anonymity.

And without hallmark is there any mechanism to know which account mines from which ip?

[Come-from-Beyond]

Got it. Yes, this compromises anonymity.

And without hallmark is there any mechanism to know which account mines from which ip?

Yes, if u own the most part of the nodes. If u worry about ur anonymity then use Tor.