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

Hey CfB - has the testnet been restarted on 0.8.3

If so, please give me hint regwarding the GET - POST settings, I seem to not have the right ones, because I get a  ...

Thanks,
l8orre

Will be disclosed after the 3rd of April.

What if the "three" were Service Providers?    

Suggested NIP (Nxt Improvement Proposal)

Adding "meta information" to Arbitrary Messages.

As AMs are going to become a key communication tool for various other parts of the Nxt system (including NIPs themselves) I suggest that we decide on one of the two ways of providing minimal "meta" information for AMs.

This could be done in the following 2 ways:

1) Encode them as URIs (making it simple for web apps to handle different kinds of things).

...

Not sure how one guy would be in charge of three INDEPENDENT gateways. This is what I have been saying. We need to find three different, independent, separate, not the same guy, gateway operators.

I would like to have the nodecoin-qt take this form!
It would require forging to be enabled to "mine" nodecoins.
It will also be monitoring the NXT blockchain so it can perform peer reviews of gateway balances, NXTcash, etc.

I will be making a small C library that can be linked or compiled into anything, but I dont do GUI,so I need someone to add the user friendly installation and these tray icon things.

I open this project to bids. If you are able to do this, submit your bid on how much it will cost and if I like it, then the project is yours. It needs to be open source and either multiplatform (unix, mac, windows) or three different versions.

James

No matter if there are 3 or more servers running the gateway stuff, it is centralized (since 1 guy could be in charge of these servers). I think no one can change that. So we have one centralized gateway. With full transparency, but it is still centralized.

If there would exist many of these gateways (N) from different people/companies/entities, we could foster some decentralization and, therefore, trust in the Nxt ecosystem. The result is that we would have N different Assets for a coin. Now the free market can value each asset for a coin differently because its different trust in these gateways. We saw an example of this in the last weeks/days as people wanted to trade their goxBTC with other BTC.

Conclusion: We need a nice paper on how these gateway servers work and make it public with a big bang.

You got it!

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

This will be big! Moontime...

I have made the current source code repository public:

https://bitbucket.org/JeanLucPicard/nxt/

Master branch is still 0.7.6, develop is 0.8.3 plus latest unreleased changes.

no. who wants to try to keep up with 100 threads? and miss all the jokes and dev conversations!

KEEP IT ALIVE!

It's not hard to start Nxt on VPS.

The problem is to keep Nxt running after some exception or detecting fork blockchain. Or when you have
And new update comes in ...