NXT :: descendant of Bitcoin - Updated Information

[Pablito89]

@CFB
This version seems really stable, isn't?

I think that now 512MB nodes could work better, without freezing.

I changed only a few lines of code. It should work as 0.4.0.

Ye but the Ddos protection is making the difference



P.S.
I think the 0.4.2 was a little flop

[1714211457]

1714211457

[1714211457]

1714211457

[1714211457]

1714211457

[1714211457]

1714211457

[1714211457]

1714211457

[omo]

Just trying to get some idea of sizing here and what is 'significant' in the world of NXT.  May be impossible to say right now with such crazy fluctuations; but what is a "big fish" in NXT?

I'm used to mining around 2 LTC/day.  If I have 10,000 NXT is that going to forge something worthwhile?  I'm hesitant to dump 1-2 more BTC in until everything stabilizes but I don't want to be a small player.

I have about 20k nxt,
mined for about 10 days and got nothing

[klee]

Just trying to get some idea of sizing here and what is 'significant' in the world of NXT.  May be impossible to say right now with such crazy fluctuations; but what is a "big fish" in NXT?

I'm used to mining around 2 LTC/day.  If I have 10,000 NXT is that going to forge something worthwhile?  I'm hesitant to dump 1-2 more BTC in until everything stabilizes but I don't want to be a small player.

I would think of it like this:

1) I want to buy LTC and/or
2) I want to buy GPUs

How much money would you invest? With NXT you will have both..

[laowai80]

what, a new version was released? I missed that, running to update everything  

[davidoski]

The client is what I see when going to localhost:7875, right? I have tried to delete blocks.nxt and transactions.nxt, and when I open the browser and unlock (creating another address...), most recent block is 23254 and it doesn't update from there.

By the term "client" I meant the program that you run in black window with java -jar command. Just unzip the 0.4.4 version of it in the new folder and run it from there.

[bitcoinrocks]

Cfb or others:

I'd like to run the Nxt server in a remote VPS for forging.  I'm concerned about the security of my passphrase.  My plan is to destroy/recreate the VPS whenever I need to unlock my account in order to minimize the risk.  Can my passphrase be stolen if my VPS is compromised *after* it is unlocked?

[S3MKi]

I'm frozen here
23888      4747512364439223888      24 Cнeжaнь 2013 18:12:11   
      
      0      0 + 0      0 B   
      
      1      10193357464858782652      863 %   
   

[lophie]

guys I am always frozen and I keep deleting and restarting with no avail. COMEONE I want to forge for god sake....

[mcjavar]

guys I am always frozen and I keep deleting and restarting with no avail. COMEONE I want to forge for god sake....

use the new version 0.4.4

[masterOfDisaster]

Wouldn't it be a perfect test NOT to use downloaded *.nxt files?
Or is it just too risky at the moment?

Not risky but inconvenient. Next time we should just upgrade one by one.

...I just used the *.nxt files from where 0.4.2 got stuck.
0.4.4 continued from there without further intervention. Restarting 0.4.2 could not fix that (I tried that repeatedly)!
Looks like an improvement and 0.4.4 is still up to date on a chain - maybe even the 'right' one

[omo]

I use a python cript to communicate with the client, checking its status,
whenever I run the script, I got the following messages.
which parameters should I set to make it not response to local requests?

Code:

2013-12-24 22:48:16.042:WARN:oejs.DoSFilter:qtp14109749-79: DOS ALERT: Request delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 22:48:17.390:WARN:oejs.DoSFilter:qtp14109749-78: DOS ALERT: Request delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 22:48:18.920:WARN:oejs.DoSFilter:qtp14109749-80: DOS ALERT: Request delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:06:50.792:WARN:oejs.DoSFilter:qtp14109749-124: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:06:52.540:WARN:oejs.DoSFilter:qtp14109749-124: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:06:54.078:WARN:oejs.DoSFilter:qtp14109749-124: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:07:15.305:WARN:oejs.DoSFilter:qtp14109749-124: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:09:15.310:WARN:oejs.DoSFilter:qtp14109749-125: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:09:39.602:WARN:oejs.DoSFilter:qtp14109749-125: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:11:07.456:WARN:oejs.DoSFilter:qtp14109749-135: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:11:25.750:WARN:oejs.DoSFilter:qtp14109749-138: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:11:39.625:WARN:oejs.DoSFilter:qtp14109749-135: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:11:51.354:WARN:oejs.DoSFilter:qtp14109749-135: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null

[davidoski]

Will the blocks.nxt and transactions.nxt files always get bigger and bigger?

[pinarello]

Running smooth 

   
23901      2576421397261863186      24-12-2013 16:29:22   
0      0 + 0      0 B   
1      1651332693446975601      648 %   

[pmabdsf]

Just trying to get some idea of sizing here and what is 'significant' in the world of NXT.  May be impossible to say right now with such crazy fluctuations; but what is a "big fish" in NXT?

I'm used to mining around 2 LTC/day.  If I have 10,000 NXT is that going to forge something worthwhile?  I'm hesitant to dump 1-2 more BTC in until everything stabilizes but I don't want to be a small player.

I have about 20k nxt,
mined for about 10 days and got nothing

Thanks...I'll consider that.  I spent 20 LTC to get my current 10k nxt; seems expensive but I want to get in early, no doubt..

[gbeirn]

@CFB
This version seems really stable, isn't?

I think that now 512MB nodes could work better, without freezing.

I think 512MB nodes could work all the time if we could restart the java process every once in a while. Is there any risk or blockchain corruption by scheduling a cron job to do that? Anyone know? If it is ok to do so, I can write up a guide for people on how to implement it.

My little node

• checks every minute (cron) if nxt is running and restarts it if not
• hourly restores chain from old nxtfiles.zip and reboots server

It is not forging, but making it working is more important to the network
I wrote about it here

@CFB
This version seems really stable, isn't?

I think that now 512MB nodes could work better, without freezing.

I think 512MB nodes could work all the time if we could restart the java process every once in a while. Is there any risk or blockchain corruption by scheduling a cron job to do that? Anyone know? If it is ok to do so, I can write up a guide for people on how to implement it.

my crontab script:

Code:

1 1 * * *  ps -ef|grep java|grep start|awk '{print $2}'|xargs kill -2

Thanks!

[DLXS]

Missclicked, sorry. Was sorted while writting

[Come-from-Beyond]

Guys, change numberOfConnectedPublicPeers in web.xml from 10 to 100 if u stuck. And try to disabled hallmark protection, this may also help.

Edit: The problem is that default value of numberOfConnectedPublicPeers is small and if none of the connected peers have recent blocks then u won't get them too.

[Come-from-Beyond]

I use a python cript to communicate with the client, checking its status,
whenever I run the script, I got the following messages.
which parameters should I set to make it not response to local requests?

Code:

2013-12-24 22:48:16.042:WARN:oejs.DoSFilter:qtp14109749-79: DOS ALERT: Request delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 22:48:17.390:WARN:oejs.DoSFilter:qtp14109749-78: DOS ALERT: Request delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 22:48:18.920:WARN:oejs.DoSFilter:qtp14109749-80: DOS ALERT: Request delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null
2013-12-24 23:06:50.792:WARN:oejs.DoSFilter:qtp14109749-124: DOS ALERT: Request
delayed=1000ms ip=0:0:0:0:0:0:0:1,session=null,user=null

In web.xml:

   <filter>
      <filter-name>DoSFilter</filter-name>
      <filter-class>org.eclipse.jetty.servlets.DoSFilter</filter-class>
      <init-param>
         <param-name>maxRequestsPerSec</param-name>
         <param-value>3000</param-value>
      </init-param>
      <init-param>
         <param-name>delayMs</param-name>
         <param-value>1000</param-value>
      </init-param>
      <init-param>
         <param-name>trackSessions</param-name>
         <param-value>false</param-value>
      </init-param>
      <async-supported>true</async-supported>
   </filter>

[laowai80]

Would other nodes be able to connect if allowedbothosts is set to localhost?
Does NXT now distinguish between dumb zombies' requests and valid host?

[laowai80]

Should hosts that are lucky to get into WellKnownPeers line turn on hallmark protection or off?