NFDcoin /

Filename Size Date modified Message
1.5 KB
jetty 9.2.9
246 B
merge with nfd-1.3.5
366 B
25.9 KB
85 B
create startable jar file
1.1 KB
Merge tag '1.3.5' into nxt-1.3.5-merge
46 B
renamed file to NFD_Wallet.url
5.6 KB
315 B
Merge remote-tracking branch 'upstream/master' into nxt-1.3.4-merge
86 B
107 B
169 B
use unpacked class files in classes subdirectory instead of the nxt.jar file
60 B
added mac osx nfd client start file
574 B
added forging tests, refactoring, run each test in a new jvm
382 B
577 B
Merge remote-tracking branch 'upstream/master' into nxt-1.3.4-merge
46 B
use unpacked class files in classes subdirectory instead of the nxt.jar file
54 B
use unpacked class files in classes subdirectory instead of the nxt.jar file
260 B
Merge tag '1.3.5' into nxt-1.3.5-merge
377 B
use unpacked class files in classes subdirectory instead of the nxt.jar file
Running the NFD software:

Dependencies: Java 7 or later needs to be installed first. Only the Oracle JVM
has been tested by NXT team.

There is no installation needed. Unpack the package and open a
shell in the resulting NFD directory. Execute the script if using Linux,
or run.bat if using Windows. This will start a java server process, which will
begin logging its activities to the console. The initialization takes a few
seconds. When it is ready, you should see the message "NFD server 1.0.0 started
successfully". Open a browser, without stopping the java process, and go to
http://localhost:8876 , where the NFD UI should now be available. To stop the
application, type Ctrl-C inside the console window.

Warning: It is better to use only latin characters and no spaces in the path
to the NFD installation directory, as the use of special characters may result
in permissions denied error in the browser, which is a known jetty issue.


There are many configuration parameters that could be changed, but the defaults
are set so that normally you can run the program immediately after unpacking,
without any additional configuration. To see what options are there, open the
conf/ file. All possible settings are listed, with
detailed explanation. If you decide to change any setting, do not edit directly, but create a new conf/ file
and only add to it the properties that need to be different from the default
values. You do not need to delete the defaults from, the
settings in override those in This way,
when upgrading the software, you can safely overwrite
with the updated file from the new package, while your customizations remain
safe in the file.

How to contribute?

There are many ways to contribute to Nxt. Here are some examples:

 * create pull requests
 * review pull requests
 * review existing code
 * create issues (aka feature ideas, bug reports, documentation etc.)
 * answer issues

Technical details:

The NFD software is a client-server application. It consists of a java server
process, the one started by the script, and a javascript user interface
run in a browser. To run a node, forge, update the blockchain, interact with
peers, only the java process needs to be running, so you could logout and close
the browser but keep the java process running. If you want to keep forging, make
sure you do not click on "stop forging" when logging out. You can also just
close the browser without logging out.

The java process communicates with peers on port 8874 tcp by default. If you are
behind a router or a firewall and want to have your node accept incoming peer
connections, you should setup port forwarding. The server will still work though
even if only outgoing connections are allowed, so opening this port is optional.

The user interface is available on port 8876. This port also accepts http API
requests which other NFD client applications could use.

The blockchain is stored on disk using the H2 embedded database, inside the
nfd_db directory. When upgrading, you should not delete the old nfd_db
directory, upgrades always include code that can upgrade old database files to
the new version whenever needed. But there is no harm if you do delete the
nfd_db, except that it will take some extra time to download the blockchain
from scratch.

The default NFD client does not store any wallet-type file on disk. Unlike
bitcoin, your password is the only thing you need to get access to your account,
and is the only piece of data you need to backup or remember. This also means
that anybody can get access to your account with only your password - so make
sure it is long and random. A weak password will result in your funds being
stolen immediately.

The java process logs its activities and error messages to the standard output
which you see in the console window, but also to a file nfd.log, which gets
overwritten at restart. In case of an error, the nfd.log file may contain
helpful information, so include its contents when submitting a bug report.

In addition to the default user interface at http://localhost:8876 , the
following URLs are available:

http://localhost:8876/test - a list of all available http API requests, very
useful for client developers and for anyone who wants to execute commands
directly using the http interface without going through the browser UI.

http://localhost:8876/test?requestType=<specificRequestType> - same as above,
but only shows the form for the request type specified.

http://localhost:8876/doc - a javadoc documentation for client developers who
want to use the Java API directly instead of going through the http interface.

http://localhost:8876/admin.html - some more commonly used commands, using the
http interface.


The source is included in the src subdirectory. It is also available at . To compile it on linux, just
run the enclosed script. This will compile all java classes and
put them under the classes subdirectory, which is already in the classpath
used by the startup script. The compiled class files can optionally be
packaged in a nfd.jar file using the enclosed script, and then nfd.jar
should be included in the classpath instead of the classes subdirectory.