NXT :: descendant of Bitcoin - Updated Information

[Jean-Luc]

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.

[1714151241]

1714151241

[1714151241]

1714151241

[1714151241]

1714151241

[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).

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 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.

[freigeist]

• 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

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

[ChuckOne]

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.

[achimsmile]

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   

[gimre]

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.

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?)

[Mistafreeze]

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.

[lophie]

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.

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?)

Signing on the client side is already implemented in the android client and the code is open source. The only problem is the desktop client communicates over browser so the signing should be java script, But anyway I honestly don't know how this is related.

With MPK you can have one public key that is able to generate other public keys without touching the private keys. Because they are linked from the seed in a certain way, Both chains (Private key chain, public key chain), will generate corresponding keys in a sequence.

A very good example is AcceptBit.com which is a private key free POS system.

The MPK functionality is VERY important to my new exchange, Also I believe it to be a key element in the automation of decentralized markets, At gateway level.

- Lophie

p.s: There is no way to do this in NXT, I am lacking proper knowledge to surpass the dam of different curve functions between Bitcoin and NXT...

[freigeist]

Is there any public node or test node running the latest NRS version that allows
api calls?

Is this documentation at http://www.thenxtwiki.org/wiki/Nxt_API#Description
already obsolete as there were already several daily updated  from 0.5.11 to 0.7.2?

[Come-from-Beyond]

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

There are 2 options:

1. Patch Curve25519 class
2. Patch Crypto class

Option 1, unlike option 2, may lead to problems u can't even imagine. I would patched Crypto...

[BloodyRookie]

I've made repo with test:
https://github.com/gimer/curve25519-sign-test

I've also added class files to the repo, so it's enough to replace "nxt-0.7.2\webapps\root\WEB-INF\classes\nxt\crypto\Curve25519.class" with file from the repo and it should work.

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.

I don't want to be offensive, but it seems that the curve25519.java file is a black box for you. Talking about leaking private key bits from those changes is ridiculous.
But if BCNext, Jean-Luc and you refuse to make changes to that file then we just have to live with a (in my opinion annoying) every now and then failing signature/verification system.

[joefox]

Is this documentation at http://www.thenxtwiki.org/wiki/Nxt_API#Description
already obsolete as there were already several daily updated  from 0.5.11 to 0.7.2?

The documentation for the high-level API is still current (minus a few recent changes that are yet to be updated).  Same API calls that worked on 0.5.11 also work in 0.7.2.

[wesleyh]

More work has to be done to find someone to do a crypto review.. This really is essential and more pressing than any other development in Nxt.

[bitcoinpaul]

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

There are 2 options:

1. Patch Curve25519 class
2. Patch Crypto class

Option 1, unlike option 2, may lead to problems u can't even imagine. I would patched Crypto...

+1

I'm no dev, but please don't touch curve.

[bitcoinpaul]

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).

...

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

Nice!

[Fatih87SK]

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).

...

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

Nice!

Awesome!

[Come-from-Beyond]

I don't want to be offensive, but it seems that the curve25519.java file is a black box for you. Talking about leaking private key bits from those changes is ridiculous.
But if BCNext, Jean-Luc and you refuse to make changes to that file then we just have to live with a (in my opinion annoying) every now and then failing signature/verification system.

Common sense doesn't work in cryptography. The problem is easily solvable by another way, so everyone who uses ur fix is just looking for troubles.

The statement that changes in Curve25519 can't lead to private key leakage still require a proof. If u can't provide the math, then u should prove that current implementation was incorrectly translated into Java from the original.

[bitcoinpaul]

I've started a section on the wiki for organizing our projects. In particular, check out the List of Proposals and Bounties page. I'm thinking we could link to stuff that is "active" there. That could be links to forum threads, google docs, or other wiki pages where projects are being discussed and hashed out, and project statuses are being updated.

For a good example of this, check out the wiki page for the new address format using Reed-Solomon encoding that NxtChg started a long time ago. Very clearly organized.

My thinking is to use the Discussion pages for throwing around ideas, criticisms, suggestions, etc, and use the main pages for summary of the proposal/project status.

Not enough folks are using Discussion pages . Click on this tab more often:



James, this could be the right place for you to put up your (many, many!) ideas for comment. EvilDave, you could put your carbon offset proposal here too. Lots more projects that I don't remember (this is why we need to put all of them in a convenient place).

Pin, maybe it could be easier if you got everyone to post their projects on the wiki instead? Then you can just go through a list of links.

Don't worry about messing things up, it's a wiki, everything can be reversed. And don't worry if you don't know wiki formatting, just type/copy and paste. Other people can help you clean things up. If there's demand, I'll put up a quick guide to simple wiki editing.

I'll be technical support. Anyone has a problem, e.g. getting errors, can't figure out how to do something, ask me and I'll troubleshoot.

+1000

At least, put all your ideas and projects into this wiki. We need this! Nxt needs this!

absolutely the right thought,
but maybe this:  List of Proposals and Bounties page
is interfering with:  http://wiki.nxtcrypto.org/wiki/Planned_Features

I think we should have ONE place not to waste much time for synchronizing it later?
What do you think?

cheers

But we have

- planned features (http://wiki.nxtcrypto.org/wiki/Planned_Features)
- a big think box which contains all ideas with their possible consequences, and thoughts about target audiences (http://wiki.nxtcrypto.org/wiki/List_of_Proposals)

First one should be more clear and short, the second is more a collection and discussion point which can change several times daily.

We should keep both. What do the others think?

And:
What do others think in general about a / this place for discussion about possible features, service providers and target audiences?

[martismartis]

NXTsolaris doesn't run in PC at all. Even I cannot close it in normal way.

EDIT: running finally.

[fmiboy]

Is this documentation at http://www.thenxtwiki.org/wiki/Nxt_API#Description
already obsolete as there were already several daily updated  from 0.5.11 to 0.7.2?

The documentation for the high-level API is still current (minus a few recent changes that are yet to be updated).  Same API calls that worked on 0.5.11 also work in 0.7.2.

some are missing, but once you start using them more often, you will figure out from error messages what each query/API call needs.