Windows Installer 0.7.2 Test release:
This version will Uninstall previous versions of my installer, check for Java and install it, and now it checks the SHA256 of the downloaded nxt-client-0.7.2.zip against the checksum given by the developers. If it doesn't match, setup will exit. The client zip can still be left behind after the install for manual verification that I'm not doing anything funny. This also is the first release of the Nxt Installer that uses the database backend. So far I haven't had any issues from that. The database download is about 36MB compressed, so not a whole lot bigger than Blocks.nxt and Transactions.nxt.
If the directory c:\nxt exists before the installer is run, it will be renamed to nxt.bak.
Download is here:
http://www.mediafire.com/download/u5q3ia3zjigcmoq/Nxt_0.7.2_Web_Setup.exe
SHA256: 4B5FBCB506EB611C24A57AD18CD9E20613889FB4C026DEE2B9350F4263564B9F
This became a lot more complicated than I would've liked, so please test and let me know if you encounter any issues.
Tested so far on Win7 x64 and Win8 x64.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 989. (Read 2761635 times)
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.
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.
definitely possible, but currently, I don't think, you would be able to use derived keys -- that is, not until, there will be APIs that CfB mentioned here:
How does one sign a transaction on the client side instead of sending the password in the clear to the server? Any info on this?
I'm working on this. The workflow will look like:
1. U use prepareTransaction API call that returns raw bytes
2. U sign the bytes and inject the signature into them
3. U use broadcastTransaction to send the transaction
Also I think it might be possible, to use bit different scheme, than the one described in BIP.
(out of curiosity, why would you want that, cause maybe there's other way to do it in case of NXT?)
Here is version 1.7 of my Windows NXT client "NXT Solaris".
Holy shit marcus03, looking good!
I planned to stop using the official java client until nexern's client comes out... but you make me reconsider
So we could host Wikileaks on decentralised Nxt web
Yeah, in principle. But, I think we should concentrate on the basics right now. As you can see, the building blocks aren't reading now.
- 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
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).
The os version has visual styles which the cs version doesn't have. On the other hand, the cs version has the block chain explorer, that won't be available in the os version for technical reasons. If blockchain pruning is implemented the whole block chain explorer won't make much sense anyway.
As long as technical possible, all features will be available in both versions.
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.
The documentation is all auto-generated with javadoc. My plan is to add descriptions of the http request parameters expected, and the json object returned, as javadoc comments for all request processing classes in nxt.http, but I haven't done it yet. This way hopefully the http api documentation will stay in sync with the code, if whoever changes the code bothers to update the comment too. 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
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.
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? 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).
@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
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
Here is version 1.7 of my Windows NXT client "NXT Solaris".
nice & Sleek!
running it now!
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
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
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
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.
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.
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.
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.
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
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.
Eithrr thatt vps is on correct chain or all my vps are on fork
thanks, but still good to report as this bug might be in 0.7.2 too.
Afaik 0.7.2 fixed that exact bug 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.
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... :>
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.
Eithrr thatt vps is on correct chain or all my vps are on fork
thanks, but still good to report as this bug might be in 0.7.2 too.
Jump to: