NXT :: descendant of Bitcoin - Updated Information

[klee]

Not particularly optimistic on Bitcoin future: Google official

"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian

Maybe he's already heard of Nxt 

Maybe Nxt is a Google's project

Oh shit! BCNext = Mike Hearn 

[Come-from-Beyond]

Not particularly optimistic on Bitcoin future: Google official

"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian

Maybe he's already heard of Nxt 

Maybe Nxt is a Google's project

Oh shit! BCNext = Mike Hearn 

Hm, let's ask him.

[pinarello]

Mem 2.40 GB

Is it memory consumed by java.exe process?

It returned to normal after restarting the client.

Pin

[klee]

Not particularly optimistic on Bitcoin future: Google official

"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian

Maybe he's already heard of Nxt 

Maybe Nxt is a Google's project

Oh shit! BCNext = Mike Hearn 

Hm, let's ask him.

Dumping my coins before it is too late... 

[ferment]

Starting to see these on a few nodes:

Code:

2013-12-16 21:13:54.744:WARN:oejh.HttpParser:qtp180753500-18: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@757e9b8e{r=1,a=IDLE,uri=-}

Have u ran 0.3.19e on these nodes? I changed nothing that could lead to "too much data after closed for HttpChannelOverHttp".

Restarted all 10 - no errors, but only 3 are connecting.

[idev]

This is from the last version.

Code:

java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:52.462:WARN:oejut.QueuedThreadPool:qtp2016627616-155:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:21.824:WARN:oejut.QueuedThreadPool:qtp2016627616-151:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:10:35.829:WARN:oejut.QueuedThreadPool:qtp2016627616-147:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:47.705:WARN:oejut.QueuedThreadPool:qtp2016627616-143:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:00.107:WARN:oejut.QueuedThreadPool:qtp2016627616-139:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:56.608:WARN:oejut.QueuedThreadPool:qtp2016627616-138:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:54.793:WARN:oejut.QueuedThreadPool:qtp2016627616-93:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:50.928:WARN:oejh.HttpParser:qtp2016627616-90: badMessage: 400 No Host for HttpChannelOverHttp@4be6e4c7{r=0,a=IDLE,uri=-}
2013-12-16 16:14:52.293:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:54.584:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
Exception in thread "qtp2016627616-90" java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:16:55.461:WARN:oeji.SelectorManager:qtp2016627616-12-selector-ServerConnectorManager@6f9bc97/0: Exception while notifying connection SslConnection@2863cb73{NEED_UNWRAP,eio=-1/-1,di=-1} -> HttpConnection@2fc1ffbc{IDLE}
java.lang.OutOfMemoryError: Java heap space

Try to set heap size:

Code:

java -Xms256m -Xmx1024m -jar start.jar

Cheers, I've now updated my public node to the latest version and set pushThreshold and pullThreshold parameters to 1.

[swansong]

Code:

2013-12-16 20:44:53.604:WARN:oejh.HttpParser:qtp180753500-18: badMessage: 400 Illegal character for HttpChannelOverHttp@6b073ba0{r=0,a=IDLE,uri=-}
2013-12-16 20:45:49.860:WARN:oejh.HttpParser:qtp180753500-19: badMessage: 400 Illegal character for HttpChannelOverHttp@13460a5b{r=0,a=IDLE,uri=-}
2013-12-16 20:52:50.693:WARN:oejh.HttpParser:qtp180753500-14: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@2d0aa021{r=5,a=IDLE,uri=-}

Any Jetty expert there?

You can talk to Jetty's coder @ irc.freenode.net #jetty his nickname is : joakime just a minute ago he helped me a lot he is a good guy.

[wesleyh]

New build of the mac client which includes the 0.3.20 release:

https://copy.com/YL2vVHK7vXza

And I'm happy to say that this seems to solve the memory issue that plagued earlier versions, at least on my system. (It appears to have been related to the 0.3.19 experimental build).

If other users can test this as well and report back. There should be no need to force quit the app the first time any more.

More info here: https://nextcoin.org/index.php/topic,708.msg5475.html

[xadidos]

New build of the mac client which includes the 0.3.20 release:

https://copy.com/YL2vVHK7vXza

And I'm happy to say that this seems to solve the memory issue that plagued earlier versions, at least on my system. (It appears to have been related to the 0.3.19 experimental build).

If other users can test this as well and report back. There should be no need to force quit the app the first time any more.

More info here: https://nextcoin.org/index.php/topic,708.msg5475.html

Add pls NXT icon (for dashboard)..

[opticalcarrier]

Version 0.3.20 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip
...now total supply of NXTs can be determined by invoking http://localhost:7874/nxt?requestType=getBalance&account=1739068987193023818 (someone should tell this to the coinmarketcap owner)...

that shows a balance of 200300, should that just be subtracted from 1000000000 or was that the wrong account?

[Come-from-Beyond]

Version 0.3.20 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip
...now total supply of NXTs can be determined by invoking http://localhost:7874/nxt?requestType=getBalance&account=1739068987193023818 (someone should tell this to the coinmarketcap owner)...

that shows a balance of 200300, should that just be subtracted from 1000000000 or was that the wrong account?

U should looks at it in 0.3.20 version.

[opticalcarrier]

Important note

"pushThreshold" and "pullThreshold" r set to 0 by default, but everyone who run a public node should mark their nodes with at least 1 NXT, coz in the future these parameters may be set to non-zero values.

so for now, just 1 works, regardless of the amt of nxt in the account?

And peers.nxt no longer exists, I guess theres never a need anymore to clear all peers by erasing that file?

Also, I updated the coinmarketcap thread and asked them to use the absolute val that the new API returns for that account.

[DiCE1904]

my blocks arnt updating, all i see is the 0 block. Do you still need to download the nxtfiles and put them in the nxt folder? Tryn to get scum nodes back online

[Come-from-Beyond]

so for now, just 1 works, regardless of the amt of nxt in the account?

If u set 850 then only peers with 850+ weight r allowed.

And peers.nxt no longer exists, I guess theres never a need anymore to clear all peers by erasing that file?

Correct.

Also, I updated the coinmarketcap thread and asked them to use the absolute val that the new API returns for that account.

Don't forget that API returns 100-fold value (in cents).

[Come-from-Beyond]

my blocks arnt updating, all i see is the 0 block. Do you still need to download the nxtfiles and put them in the nxt folder? Tryn to get scum nodes back online

U can download blockchain from scratches. Check ur list of well-known peers.

[laowai80]

0.3.20 is running good so far.

[wesleyh]

New build of the mac client which includes the 0.3.20 release:

https://copy.com/YL2vVHK7vXza

And I'm happy to say that this seems to solve the memory issue that plagued earlier versions, at least on my system. (It appears to have been related to the 0.3.19 experimental build).

If other users can test this as well and report back. There should be no need to force quit the app the first time any more.

More info here: https://nextcoin.org/index.php/topic,708.msg5475.html

Add pls NXT icon (for dashboard)..

An icon will be added soon! thx

[pinarello]

New build of the mac client which includes the 0.3.20 release:

https://copy.com/YL2vVHK7vXza

And I'm happy to say that this seems to solve the memory issue that plagued earlier versions, at least on my system. (It appears to have been related to the 0.3.19 experimental build).

If other users can test this as well and report back. There should be no need to force quit the app the first time any more.

More info here: https://nextcoin.org/index.php/topic,708.msg5475.html

Add pls NXT icon (for dashboard)..

An icon will be added soon! thx

Better use the icon that wins the vote in couple of days.


Pin

[wesleyh]

New build of the mac client which includes the 0.3.20 release:

https://copy.com/YL2vVHK7vXza

And I'm happy to say that this seems to solve the memory issue that plagued earlier versions, at least on my system. (It appears to have been related to the 0.3.19 experimental build).

If other users can test this as well and report back. There should be no need to force quit the app the first time any more.

More info here: https://nextcoin.org/index.php/topic,708.msg5475.html

Add pls NXT icon (for dashboard)..

An icon will be added soon! thx

Better use the icon that wins the vote in couple of days.


Pin

You are right, I will wait, although I do like the icon on thenxtcoin.com

In other news, another new mac client version:

https://copy.com/eZeM1dlEur3z

This one adds fullscreen support, and links to the forum and the wiki in the menu bar.

More info here for newcomers: https://nextcoin.org/index.php/topic,708.15.html

[Syth]

Why are the confirmations so slow?
Been waiting 70 hours now to get started on mining, and I've only got 48 confirmations so far, even got down to 47 now.
If I need 900 confirmations I'll need to wait an additional 53 days.

Any way to speed this up?