Topic: NXT :: descendant of Bitcoin - Updated Information - page 594. (Read 2761626 times)

lol, java long is an integer data type not float. That is java basic: http://www.tutorialspoint.com/java/java_basic_datatypes.htm

James I used to work with 3 computers voting for chemical plant control, what we did there was if one computer got confused and was continually voting wrong it would take an update from one of the others and verify it with the other one and if both updates agreed it would reload itself with that copy.

I.e. the continually 'wrong' node would update itself by cloning one of the other 2 (which were agreeing) and verifying itself with the one it didn't clone from, as the other two were agreeing they should be identical and therefore after the clone all 3 are then in sync again.

Don't know if that helps you resolve the confused state.

If you ever get in the state that all 3 nodes do not align then this is a critical state and requires human intervention but I'm sure you know this.

Something like a NXT secretary, scribe, or archivist?

How much was the fatal flaw worth? I guess that money can be sent to community fund now? (Or used for crypto audit)

Ok cfb now that source dis released, what was the fatal injected flaw, and how couldyou have killed it in under a day

Are you gonna use floating point?

In fact, all people who are coordinating with exchanges needs to make the exchange they are dealing with awareo of to not just trytotrack transactionId for outgoing transactions.  Orsuffer mtgox fate (that is, if malleability really is the issue that took them down, im still not 100 percent convinced they didnt just take the money

You forgot some links.

There is a very hot place in Hell for overquoters.

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


Changelog
-Compatibilty fixes for NRS 0.8.x
-Implemented Curve25519 algorithm:
  * NXT Solaris is now a bit like "Electrum for NXT" (a thin client that does not download the complete blockchain, connecting to untrusted NRS nodes)
  * It is now safe to connect to public NRS nodes (except for forging).
  * As default, NXT Solaris no connects to a random public node.
  * Currently a static list of public nodes that allow API calls from anyone from the text file public_nodes.txt is used.
  * NRS and Java are now longer distributed with NRS Solaris.
  * You will get a warning in the secret input dialog if the secret is transmitted over http to the remote NRS node (only with start/stop forging).
  * If you want to forge, run your own NRS instance locally and set up NXT Solaris to connect to your instance.
-Since there is no batch mode in the NRS API:
  * Details for peers are no longer retrieved as default
  * A maximum of 50 (yet unkown) transactions per account are fetched from the NRS node whenever there is a new block
-Fixed null exchange rates when www.cryptocoincharts.info is down


Download
64-bit Version: NXTSolaris-v2.1-64bit.zip (29.6 MB) – Download here
SHA256 checksum for NXTSolaris-v2.1-64bit.zip: C01599EA51599AD4E2EE8D0B1762686EB7EC274118658C43F76983957F76B0D7

32-bit Version: NXTSolaris-v2.1-32bit.zip (27.5 MB) – Download here
SHA256 checksum for NXTSolaris-v2.1-32bit.zip: EAE75B046577E771CC2C8F57D2A4B8D9AF9F87F92FE5CD400DDE9F9755589957

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 2.1 is NOT compatible with the previous versions. Please delete any existing files and extract the zip archive to a new directory.

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 [DONE]
6.) Release source-code for FireMonkey Windows version (February 16th, 2014 latest) [DONE]
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
-Arbitrary message encryption
-Offer a simple and advanced GUI, with the simple GUI targeted at new users
-Implement client side Curve25519 encryption/signing



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

Go ask on nextcoin how they solve malleability issue for btc, nxt, and any other crrency they plan on adding

Are you sure thats a bug?  That tells me that the nrs instance returning that api has, just prior to that api request, processed a sedMoney request from that account for 3.00 nxt, and that transaction has just not yet been written to a block

This is what I plan to do next:

1. In 0.8.4 I am adding the ability to easily switch between real net and test net. First, this will allow anyone to use the test network with just a single change in nxt.properties, no need for a different client (of course for features like Asset Exchange one will have to use Wesley's client, but the Nxt core code will be the same). This will allow many more people to participate in testing. Second, by having the test network and the real network run exactly the same code, with the only difference being at which block height features like AE and Voting become enabled, there will be no risk of additional bugs introduced in porting, or any need for porting of code from test server code to main code.

2. We need to get the Asset Exchange feature rolled out. There is one remaining critical bug, the wrong calculation of unconfirmed asset balances, which I have tried to fix in the latest 0.8 code, but haven't been able to test yet because the test net was still on 0.7.6. Thus the importance of the previous point about having test net in code sync with the main one.

3. Before actually enabling Asset Exchange, I need to make the transition from storing transaction amounts and fees in Nxt to nano-Nxt (0.000000001 Nxt), or whatever fits in a Java long, given that the max possible balance or transaction amount is 1000000000 Nxt. I previously thought about adding a new transaction type, but this will be more complicated and ugly in the long run, so better do it right. At first this is just about increasing the precision at which amounts are stored, enabling actual usage of fractional amounts and fees will be done at a later step. But this has to be finished before the AE is turned on, it will be much more difficult after that. And it will have to be very well tested, so again we need a reliable test network.

4. I need to move the remaining classes that are still stored in memory only - Account, Alias, Asset, Order... into the database. It is not critical yet, because they don't take much space, but has to be done before it becomes a problem, especially with the Asset Exchange that currently needs to keep all open orders and trades in memory.

Really?

Now seriously.

wait what on earth is this? i dont like lists with everyone's name except mine.

Cryptsy Update (I've been keeping up since we met with them in Miami)

- Getting there
- Connection methods in place
- Working on integration of deposits/withdrawals

- CIYAM knows how we will implement fully TF
- source code made available today (1 month earlier)
- James' Doge Gateway is running

What are we celebrating?





_______________________________________________________________________________ _________________________________
Next Coin Lite - Fair Distribution

Good point. Discussion about parallel chain is neglected yet.

Is there any concerted effort being made to compile information to a single, comprehensive source? there are a lot of places to find info, and a lot of people putting out info, it may be a good idea and a good time for there to be an effort to consolidate and reorganize usable information to a single and definitive source and to coordinate this effort between the people who are working on it. There is so much info out there in so many sources, and in so many forms and styles that it is kind of confusing and really a lot of work to self educate on NXT; And there is no form of cohesion or method to its structure. There IS no single article, blog, interview, podcast, forum thread or any other media source that does it justice as a stand alone source of info. Anon136 was posting last night about how he felt he had given a bad interview on NXT, but that only stands to reason, as the nature of NXT makes it impossible to be educated on in a brief info session, and the lack of cohesiveness in the information that is available only serves to magnify this. It may be a good time to start a coordinated effort to supply a source of info that is more unified, accurate, and complete and is organized in a way as to accommodate specific targeted audiences (technical information seekers, and basic information seekers). I think it would serve the community better and make it seem like we had our stuff together a little more to pursue this. I have come into the community just recently and have spent a lot of time looking, and bugging people with questions to learn about NXT, and this has made me aware of this chink it the NXT armor. I think there is a lot of good info out there, and a lot of talented people who know a lot about NXT and care a lot. But with the way that NXT has grown and with the way that info about it is dispersed as a result of that growth it might be a good Idea to supply a more easy to access, consolidated source of info. Get everyone on the same page so to speak. If there were a group effort, coordinated and outlined for that purpose I think it would be beneficial to the growth of NXT, and would not burden one person with such a daunting task.

if there is an effort to do so, I would like to help if there is help needed. If there has not been such an effort I would like to suggest it and offer help.