NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

Code:

[2014-02-09 21:18:55.677] Scanning blockchain...
[2014-02-09 21:19:09.888] ...Done
[2014-02-09 21:19:09.891] NRS 0.7.2 started successfully.
[2014-02-09 21:22:02.461] DEBUG: Failed to accept block 12792071761809604839 at
height 62244 received from 88.198.142.92, blacklisting
[2014-02-09 21:22:02.462] DEBUG: Blacklisting 88.198.142.92 because of: Invalid
timestamp: 6657738 current time is 6657722, previous block timestamp is 6657684

what does this mean? It does not affect the forging,right?

Looks like one of u needs to set the correct time.

[1713566249]

1713566249

[1713566249]

1713566249

[salsacz]

In order to create a new internet the central infrastructure should probably be a peer to peer social network, e-mail, search engine, cloud storage, file sharing and cryptocurrency

Is it possible to transform us to the app with peer to peer social network, e-mail, search engine, cloud storage and file sharing?

Probably not us, but NXT for sure.

thank you, so we are looking for developers of "search engine, cloud storage and file sharing?"

Well, not exactly sure what you need.

Developers for evolving NXT or Developers for developing an app? The latter seems pre-mature because NXT needs another mechanism to handle multiple chains at once.

The social part is already in place. At least messaging. Not sure about other activities. But another blockchain and solved.

The file storage stuff should be the most interesting part. File sharing is 'just' a matter of access control on top of the file storage.

Search engine? Sounds more like an analysis client to me. Could only search for/mine data on the blockchains.

Email? Well, as far as the consensus goes, NXT core only reads/adds data from/to the blockchains. Sending emails could be done per pull principle. But don't see, why this needs NXT. In this case, I would rather recommend a more general service that is able to scan the chain and perform several actions if detecting certain patterns.

So we could host Wikileaks on decentralised Nxt web

[SZZT]

Code:

java.exe               memory:600.808K

on a win7 i3
is this normal?

edit:

So we could host Wikileaks on decentralised Nxt web

this can be so much win....

[punkrock]

SELLING BATTLEFIELD 4 - THREE KEYS LEFT!

I take NXT or BTC. Make your offer and send a PM.

[Sebastien256]

got that on 0.7.1

[2014-02-09 06:25:30.094] CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
        at java.io.BufferedReader.<init>(Unknown Source)
        at java.io.BufferedReader.<init>(Unknown Source)
        at nxt.peer.Peer.send(Peer.java:620)
        at nxt.peer.Peer$3.run(Peer.java:142)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-09 06:25:57.222] some threads didn't terminate, forcing shutdown
[2014-02-09 06:25:57.224] NRS 0.7.1 stopped.

[punkrock]

@Sebastien256: 0.7.2 -> https://bitcointalk.org/index.php?topic=345619.msg5033086#msg5033086

[l8orre]

Asset API needs to add volume to getAsset - (24 hour volume). Perhaps also the 24 hour high, 24 hour low, and last trade info.

.. better not. Client has to do that itself. 24hour is totally abritrary! Why not12h? 37days, 11hours, 12mins, 22secs? Careful, this is a slippery slope to unload ever more thinking to rigid 24h block thinking schemes..

[Sebastien256]

@Sebastien256: 0.7.2 -> https://bitcointalk.org/index.php?topic=345619.msg5033086#msg5033086

thanks, but still good to report as this bug might be in 0.7.2 too.

[opticalcarrier]

Release 0.7.2

After update to 0.7.2 I ended up now 3 times in a row on a fork with just one block in last 4 days and insane targets, I let it run for about an hour now and it does not seem to be able to recover from that.

Me too. I downloaded (almost) the entire chain from vps2.nxtcrypto.org. Could the admin of that node check it's ok?

Eithrr thatt vps is on correct chain or all my vps are on fork

[gimre]

Waoh, made the mistake and had a look at:
https://github.com/gimer/curve25519-sign-test/blob/master/src/nxt/crypto/Curve25519.java
My eyes are bleeding as does my computer science heart.

Mathematicians, physicists and cryptographists should NOT write code. Please! Pleeeease!  

You want us to audit but reading this is like reading a best-seller that has been injected grammar errors and typos each in every sentence. So, how to find the errors in content if you can barely tell them apart from the former ones.

I really get the impression that programmed cryptography is not so difficult in the end; except when people having no idea how to write it down write it down.  

Sorry for being emotional.

But you are aware, that this is almost exactly the same file, as used in NRS... :>

[Meizirkki]

Release 0.7.2

After update to 0.7.2 I ended up now 3 times in a row on a fork with just one block in last 4 days and insane targets, I let it run for about an hour now and it does not seem to be able to recover from that.

Me too. I downloaded (almost) the entire chain from vps2.nxtcrypto.org. Could the admin of that node check it's ok?

Eithrr thatt vps is on correct chain or all my vps are on fork

Okay good

@Sebastien256: 0.7.2 -> https://bitcointalk.org/index.php?topic=345619.msg5033086#msg5033086

thanks, but still good to report as this bug might be in 0.7.2 too.

Afaik 0.7.2 fixed that exact bug

[gimre]

I hope that u won't create a "solution" that leaks private key bits. I'm against the changes until I see a formal proof, so u better talk to Jean-Luc.

Well, I understand math behind the change. (Please, spend 5 min, to read original BloodyRookie's post).

The ONLY difference to original sign is that (x-h) is represented correctly.
(and it WON'T leak keys, attacker would STILL need to solve DLP problem in that group:
 or in other words, if s is priv key, what is the difference between a*s and a'*s)

I'm going to run NRS with patched Curve from now on.

edit: some more explanation here: https://nextcoin.org/index.php/topic,3915.0.html

[ChuckOne]

Waoh, made the mistake and had a look at:
https://github.com/gimer/curve25519-sign-test/blob/master/src/nxt/crypto/Curve25519.java
My eyes are bleeding as does my computer science heart.

Mathematicians, physicists and cryptographists should NOT write code. Please! Pleeeease!  

You want us to audit but reading this is like reading a best-seller that has been injected grammar errors and typos each in every sentence. So, how to find the errors in content if you can barely tell them apart from the former ones.

I really get the impression that programmed cryptography is not so difficult in the end; except when people having no idea how to write it down write it down.  

Sorry for being emotional.

But you are aware, that this is almost exactly the same file, as used in NRS... :>

You see what I mean? 

Bugs hidden up.

[gimre]

Waoh, made the mistake and had a look at:
https://github.com/gimer/curve25519-sign-test/blob/master/src/nxt/crypto/Curve25519.java
My eyes are bleeding as does my computer science heart.

Mathematicians, physicists and cryptographists should NOT write code. Please! Pleeeease!  

You want us to audit but reading this is like reading a best-seller that has been injected grammar errors and typos each in every sentence. So, how to find the errors in content if you can barely tell them apart from the former ones.

I really get the impression that programmed cryptography is not so difficult in the end; except when people having no idea how to write it down write it down.  

Sorry for being emotional.

But you are aware, that this is almost exactly the same file, as used in NRS... :>

You see what I mean?  

Bugs hidden up.

Yeah, this piece is far from beauty, but keep in mind few things:

• curve itself and calculation of priv key is done the way, that djb did it
• it was optimized for speed
• once you know what all the strange APIs (mula_small, mula32, divmod) are doing, it's not that hard to follow, what's going on
• sign&verify, was done by xmath @ sci.crypt list: https://groups.google.com/forum/#!topic/sci.crypt/J_7OGDf9cJE
• it's hard to tell, if the bug was present in original C implementation*, or was it introduced, when code was ported to Java

* if some would have the copy of that C implementation, I'd be really thankful, to have look at it.

[marcus03]

Here is version 1.7 of my Windows NXT client "NXT Solaris".

The (future) open-source version now has the everything implemented that the closed-source version has (except for the blockchain explorer which won't be available in the open-source version).


Changelog
Changed for v1.7
-OS version: Designed data grids
-OS version: Added market graphs
-OS version: Added visual styles (not persistent between application starts yet)
-NRS 0.7.2 is now included


Download
64-bit Version: NXTSolaris-v1.7-64bit.zip (108 MB) – Download here
SHA256 checksum for NXTSolaris-v1.7-64bit.zip: F85AB521CD5A00C40BDC6280A6DF943DC5A0DD930D48F610DE44970ADA8BB62F

32-bit Version: NXTSolaris-v1.7-32bit.zip (104 MB) – Download here
SHA256 checksum for NXTSolaris-v1.7-32bit.zip: 480F90CBCFE3FA3FE8FA68FC9087FAF817BDAF637C23544881BEAE6490600F66


Screenshot
In the open-source version you can now select different visual styles, so the personal account management now can look like this:



The visual styles available still need a bit of tweaking.

For more screenshots and everything else please visit: http://nxtsolaris.wordpress.com/


Installation
Simply unzip the archive and run the NXTSolarisStarter.exe file.

The current version 1.7 is compatible with the previous version 1.6, but not compatible with version 1.5 and before.

If you are updating from version 1.6 simply replace all files with the files in the version 1.7 zip archive.

Roadmap
1.) Move current version of my code to XE5 and release closed source 32-bit and 64-bit versions for Windows. [DONE]
2.) Refactor code to a MVC architecture, so that I can create separate GUIs while using the same version of the business logic code. [DONE]
3.) Create new GUIs for Windows and OS X using the same business logic, but based on the cross-platform Firemonkey libraries. [DONE]
4.) Release Windows version (32 and 64 bit) based on FireMonkey. [DONE]
5.) Implement new features from the TODO list
6.) Release source-code for FireMonkey Windows version (February 16th, 2014 latest)
7.) Implement new features from the TODO list
8.) OSX compatibility changes
9.) Release OSX version based on FireMonkey.
10.) Release source code for FireMonkey OSX version.

TODO list
-Offer a simple and advanced GUI, with the simple GUI targeted at new users
-Asset exchange support
-Implement client side Curve25519 encryption/signing
-Arbitrary message encryption


Donations
I hope you like my client and I’d be extremely happy to see some donations for the future of this project!

NXT: 1758531264253431177

[SZZT]

Here is version 1.7 of my Windows NXT client "NXT Solaris".

nice & Sleek!
running it now!

[newsilike]

@marcus03
Looks so cool and runs really smooth 

About time to get some newbies on board 

I'm not up to date with the community fund distribution but I think marcus03 should definitely get a chunk of it.
Especially since he's building an open source client as well now

[drsnuggles]

Here is version 1.7 of my Windows NXT client "NXT Solaris".

The (future) open-source version now has the everything implemented that the closed-source version has (except for the blockchain explorer which won't be available in the open-source version).

That GUI look really good! Only thing I don't like is that there is a closed-source version which has more options. Is there a way to make just one version and make it open source?

[wesleyh]

I like the docs at http://localhost:7874/docs - but is there any way to see method arguments (for nxt.http) - Perhaps I'm missing something but I don't see them. Only the function name and what it extends and some other non-important information.

[lophie]

I hope that u won't create a "solution" that leaks private key bits. I'm against the changes until I see a formal proof, so u better talk to Jean-Luc.

Well, I understand math behind the change. (Please, spend 5 min, to read original BloodyRookie's post).

The ONLY difference to original sign is that (x-h) is represented correctly.
(and it WON'T leak keys, attacker would STILL need to solve DLP problem in that group:
 or in other words, if s is priv key, what is the difference between a*s and a'*s)

I'm going to run NRS with patched Curve from now on.

edit: some more explanation here: https://nextcoin.org/index.php/topic,3915.0.html

Well since you understand this math and stuff, how about you make us MPK like functionality and we will reward you handsomely for it.

NAME THE PRICE, If it was reasonable I will PAY, I will use escrow as well, I will also rally for more funds for this.

Basically I need you to implement BIP0032 for NXT, or at least tell us if and why it is not possible to do so.

A link to show you what I am trying to accomplish here: https://github.com/genjix/bips/blob/master/bip-0032.md, It was implemented in Electrum bitcoin thin client. For me it will suffice if you make the appropriate working address generation in Java.

This is an open request and prize.

- Lophie