NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

For local computer use "localhost".

- as I stated in my initial question: https://bitcointalk.org/index.php?topic=345619.msg3908105#msg3908105 , if I use localhost, I get "Matrix ...". Please, try yourself. And fix this bug.

Try

Code:

0:0:0:0:0:0:0:1

- 0:0:0:0:0:0:0:1 also gives "Matrix ...". 
Only * (in the allowedUserHosts param) allows  https://localhost:7875/ .
Please correct this bug.

Could u post the result of http://localhost:7874/nxt?requestType=getMyInfo, please?

[abctc]

For local computer use "localhost".

- as I stated in my initial question: https://bitcointalk.org/index.php?topic=345619.msg3908105#msg3908105 , if I use localhost, I get "Matrix ...". Please, try yourself. And fix this bug.

Try

Code:

0:0:0:0:0:0:0:1

- 0:0:0:0:0:0:0:1 also gives "Matrix ...". 
Only * (in the allowedUserHosts param) allows  https://localhost:7875/ .
Please correct this bug.

Could u post the result of http://localhost:7874/nxt?requestType=getMyInfo, please?

Thank you!  Figured out my mistake. I should write neither localhost, nor 127.0.0.0, but 127.0.0.1

[superresistant]

Remove all *.nxt files, download https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip, WAIT until ur soft catches recent blocks (blocks.nxt file not growing), unlock ur account.

This worked perfectly. Thanks a lot.

Here is what to do if you are lost :

- Remove .nxt files from nxt folder.
- Download https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip and put the new .nxt files in the nxt folder.
- Lauch the nxt client from a bat file containing a command line.
My command line on Windows 8 using java 64 bits is :
"C:\Program Files\Java\jre7\bin\java.exe" -Xms512m -Xmx1024m -jar start.jar
- Wait about one hour and check if the blocks.nxt file is not growing any more.
Mine stopped growing at about 4660Ko.
- Open your web browser and go to http://localhost:7874/
- Click on the lock icon and type your password to open your account.

[Come-from-Beyond]

- Wait about one hour and check if the blocks.nxt file is not growing any more.

Did it take 1 hour to download the blockchain?

[superresistant]

- Wait about one hour and check if the blocks.nxt file is not growing any more.

Did it take 1 hour to download the blockchain?

Well, I'm not sure. I was doing something else in the meantime. I did the same yesterday and it was not working when I waited less than 15 minutes.

[freigeist]

- Wait about one hour and check if the blocks.nxt file is not growing any more.

Did it take 1 hour to download the blockchain?

Well, I'm not sure. I was doing something else in the meantime. I did the same yesterday and it was not working when I waited less than 15 minutes.

Hello.

I see by the posts that
a lot of users have problems with this blockchain download and then they try to open
the client interface before the download has been completed which gives them errors.

Is it possible to know the size of the blockchain in advance and put some kind of
notification (message) in the command line output like
"Please wait! Downlaoding blockchain.... 5% of 100%" or something similar.

[Come-from-Beyond]

Is it possible to know the size of the blockchain in advance and put some kind of
notification (message) in the command line output like
"Please wait! Downlaoding blockchain.... 5% of 100%" or something similar.

I'm going to let to unlock accounts without waiting for the full blockchain.

[superresistant]

I'm going to let to unlock accounts without waiting for the full blockchain.

Good idea.

[Come-from-Beyond]

Full blockchain downloading took almost half an hour to complete jumping from one node to another (which adds a little overhead) on 1 Mbps connection.

There r 2 options for optimization:
- Switch to binary protocol instead of JSON-based (~3x improvement, I prefer to stick to JSON until we get some alt-clients, JSON greatly lowers entry threshold for new programmers)
- Add GZIP compression (~10x improvement)

Or we can leave it as is for the time being.

Any suggestions?

[Jean-Luc]

Full blockchain downloading took almost half an hour to complete jumping from one node to another (which adds a little overhead) on 1 Mbps connection.

There r 2 options for optimization:
- Switch to binary protocol instead of JSON-based (~3x improvement, I prefer to stick to JSON until we get some alt-clients, JSON greatly lowers entry threshold for new programmers)
- Add GZIP compression (~10x improvement)

Or we can leave it as is for the time being.

Any suggestions?

I also prefer to keep it JSON, and add a gzip filter on top. But why is it so slow to begin with? My blocks.nxt file takes 4.6M and transactions.nxt 0.5M. Is it because it is downloading it in way too many small pieces, one block at a time, and makes a new connection each time? If so, I would thing the biggest performance boost would come from downloading it in batches, many blocks in one go, rather than trying to compress each block download separately.

[ImmortAlex]

- Add GZIP compression (~10x improvement)

I think this can be selectable via request parameter.
In Java GZIP is part of standard library and is not a problem at all.

But right now traffic is not a problem. It download full blockchain incredibly slow even on very good internet connection. Block by block, 0.5s for each.

[ImmortAlex]

JSON greatly lowers entry threshold for new programmers

... and badly documented API cut off inexperienced noobs

[Come-from-Beyond]

Full blockchain downloading took almost half an hour to complete jumping from one node to another (which adds a little overhead) on 1 Mbps connection.

There r 2 options for optimization:
- Switch to binary protocol instead of JSON-based (~3x improvement, I prefer to stick to JSON until we get some alt-clients, JSON greatly lowers entry threshold for new programmers)
- Add GZIP compression (~10x improvement)

Or we can leave it as is for the time being.

Any suggestions?

I also prefer to keep it JSON, and add a gzip filter on top. But why is it so slow to begin with? My blocks.nxt file takes 4.6M and transactions.nxt 0.5M. Is it because it is downloading it in way too many small pieces, one block at a time, and makes a new connection each time? If so, I would thing the biggest performance boost would come from downloading it in batches, many blocks in one go, rather than trying to compress each block download separately.

Blocks r feeded in 128 Kb chunks (4 blocks min). I put in todo list to check why it's so slow.

[Come-from-Beyond]

In Java GZIP is part of standard library and is not a problem at all.

This can be a problem for non-Java clients.

[ImmortAlex]

This can be a problem for non-Java clients.

Is GZIP not a part of HTTP standard?
I'm even thinking that it can be released transparently through any HTTP client library, isn't it?
And I don't believe that in 21st century anyone will write client using pure OS API anyway...

In worst case you can always add parameter to request, to switch gzip on/off, or use different port for compressed traffic.

[Sharky444]

Full blockchain downloading took almost half an hour to complete jumping from one node to another (which adds a little overhead) on 1 Mbps connection.

There r 2 options for optimization:
- Switch to binary protocol instead of JSON-based (~3x improvement, I prefer to stick to JSON until we get some alt-clients, JSON greatly lowers entry threshold for new programmers)
- Add GZIP compression (~10x improvement)

Or we can leave it as is for the time being.

Any suggestions?

I would compress.

[Come-from-Beyond]

NEWS

On the 3rd of January the source code of basic features will be published for peer review. BCNext decided to make it more interesting to do a review, so the code will contain 3 security flaws - serious, critical and fatal ones. The 1st person who reports one of these flaws in a special thread will get a reward (1'000, 10'000 and 100'000 NXT accordingly). There will be SHA256 hashes of flaw descriptions published, the descriptions will be revealed after the flaws r reported. If some unreported ones left after 3 months, BCNext may decide to reveal them at any time.

PS: This has a nice side-effect, copycats have to wait for full disclosure or do their own research.

[Come-from-Beyond]

This can be a problem for non-Java clients.

Is GZIP not a part of HTTP standard?
I'm even thinking that it can be released transparently through any HTTP client library, isn't it?
And I don't believe that in 21st century anyone will write client using pure OS API anyway...

In worst case you can always add parameter to request, to switch gzip on/off, or use different port for compressed traffic.

Aye, I'm going to add a parameter or just increment "protocol" value.

[salsacz]

I think we should watch Quark, their strategy and reaction of people about it's premining thing:

"I agree that Quark is out of control, but only because of it's currency supply curve. Early blocks accounted for 90%+ of the total currency supply, mined in a very short period. A multimillion USD market cap is scary with such rapid reward halving in the coin by design. Quark was intentionally designed for severe wealth inequality.
90%+ of the currency supply goes to creators/early miners, and this has already occurred. This is important to note for cryptotraders who might see this as an opportunity to "ride the wave" and will further inflate this bubble. The only opportunity this coin provided was for the early miners (if that was even made possible by the creators) and that opportunity is long gone.
PSA- Always consider the following when trying to weed out pump & dump altcoins:
Age of coin
Total coins in existence now
Total currency supply
If it's really new and 90%+ mined already, seems a prime candidate for market manipulation and dumping.

PSA- Always consider the following when trying to weed out pump & dump altcoins:
Age of coin
Total coins in existence now
Total currency supply"

[salsacz]

- Add GZIP compression (~10x improvement)

I think this can be selectable via request parameter.
In Java GZIP is part of standard library and is not a problem at all.

But right now traffic is not a problem. It download full blockchain incredibly slow even on very good internet connection. Block by block, 0.5s for each.

it took me 3 hours a few days ago