Latest client:
Note: Since version 7.x you don't longer need the .nxt- & .nxt.bak-files. Version 7.x is working with an internal database. If you start the client for the first time, just wait some minutes. It will take a while to download the complete database (~112 MB). For updates: Do not delete the nxt_db directory.
STABLE CLIENT
Download: NRS 0.7.4 (Mirror)
SHA-256: 847c70f734a3954159af99e0241d448369d4833067076570671324946a835245 (nxt-client-0.7.4.zip) *updated 2014-02-13*
To verify a SHA-256 checksum you can use MD5 & SHA Checksum Utility (
Virustotal)
Change log 0.7.4:
Another bugfix in the transition to Transparent Forging, starting from
block 67000. Upgrade before this block, because there will be a fork.
This release drops support for the old getMilestoneBlockIds protocol.
Clients older than 0.7.3 will not be able to request blocks from 0.7.4
nodes. Everybody needs to upgrade to 0.7.4 anyway, before block 67000.
Some optimizations in the database queries used during unlock account,
let's see if this helps Raspberry users.
Minor other improvements.
EXPERIMENTAL CLIENT (use with caution!)
Download: NRS 0.7.0e (Mirror)
SHA-256: aa778bade323d2b3f4cf13c925aa7b541d57f0853a5828385b72254ac92010bc (nxt-client-0.7.0e.zip) *updated 2014-02-06*
To verify a SHA-256 checksum you can use MD5 & SHA Checksum Utility (
Virustotal)
Change log 0.7.0e:
This is the first release using an embedded java database (H2) to store
the blockchain, instead of serialized java object files. Because this is
a major change, this version is to be considered experimental.
The blocks.nxt and transactions.nxt and .bak files are no longer used.
Furthermore, they will not be loaded at startup, when you start with
empty database the very first time it will need to download the full
blockchain from the network.
The database is stored under the nxt_db directory, as of now it will
take around 100 MB when downloaded. If anything goes wrong and you need
to start fresh, it is safe to delete that nxt_db directory, it will be
recreated.
There are no changes in the web.xml file compared to 0.6.1. I will add
parameters to tweak database settings later, if needed.
The database will use 50% of the memory available to java for its cache.
The actual value is printed out at startup.
Currently only blocks and transactions are stored in database tables,
everything else such as accounts, aliases, assets, orders, messages,
is loaded at startup and then kept in memory. The amount of memory
those take is still small, relative to what was needed for all blocks
and transactions.
At startup, the blockchain scan takes a bit longer, this is normal.
If anything else is unusually slow, I will look into profiling and
optimizing it.
There are no new user-visible features compared to 0.6.1, the code is
kept in sync now (including the critical bugfixes). Having both 0.6.1
and 0.7.0e nodes on the network should not result in forks. I will
maintain both the 0.6.x and 0.7.x branches for some time, until all
major database related issues are discovered and fixed. Please report
bugs, including the stack traces.
Latest NXT-files:
Blocks.nxt & Transactions.nxt: nxt-files-2014-02-07.zip (89,3 MB)
*2014-02-07*
Tutorial:
You need Java Runtime Environment (32 Bit / x86) on your computer.
Download | (Mirror)
1. Download the latest client (see above)
2. Unzip the file with 7zip
3. Switch to the unzipped "nxt"-folder and create a .bat-file (
Right-Click -> New -> Text Document)
4. Open the new .bat-file with Notepad++, paste the following stuff into it and save the file
"C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar start.jar
if Java is not installed on this path, search for the file
Java.exe and use the correct path
5. Start the file
start.bat with a doubble-click
6. Now open with Firefox the page https://localhost:7875 and accept the "untrusted" SSL-Certificate
7. To create your own account, click on the lock-icon on the top left.
8. Now the really important step. Your passphrase IS you account so create passphrase with a minimum of 70 characters (Uppercase and lowercase letters, numbers and special characters). Never ever use a passphrase which someone might use too - he (or she) will steal all your Nextcoins for sure! Notice: Everyone who uses your passphrase has access to your account!
9. Once you have opened your account using your secret password, your client begins with the work, the so-called
forging - unlike in Litecoin, where we are talking about "mining". You should leave the page open in your browser to verify that current block to be loaded ("Recent Blocks").
10. An overview of your NXT account you can find in the so-called NXT Block Explorer. Put in your account number there and click on "GO".
Security:
- Use a password that's at least 70 characters and contains never forget it! I recommend Keepass as a password manager.
- Use NXT exclusively on your own PC and not on a VPS.
- NXT uses port 7874 (TCP). This is the only port that should be open.
- NXT also uses the port 7875 for the web interface and port 7876 for the API commands. You should close these ports at your router to prevent access from the outside.
More:
If you get any errors, go to the folder
NXT -> webapps folder -> root -> WEB-INF and edit the file
web.xml for example with Notepad++.
In line 26 put in your IP-Address. Save the file
web.xml and run the NXT server again by opening the
start.bat.
Thanks for supporting NXT!
