NXT :: descendant of Bitcoin - Updated Information

[Eadeqa]

bitcoin sucks bigtime, it ruined my CPU.

didnt opened my wallet for some time and blockchain download took ages.

CPU overheated 3 times during blockchain download with result every time laptop turned itself off.

I realy don"t see it in bitcoin honestly.

The common user doesn't have to download the entire bitcoin blockchain. Use lightweight client like Electrum ..

[EvilDave]

SWARM NEEDED

Here is the reddit post, please everyone sign up at Bittrex.

Hello NXT community,

I solicited feedback on another thread about which coins we should support on our exchange before our public launch. NXT was overwhelmingly recommended.

Before we make the final decision, we're providing a special invite code for NXT users to experience our site first hand. Go to https://bittrex.com/Account/Register and use SUPPORT_NXT as the invite code. This gets you past the invite code queue. Place some trades, enabled 2FA, or try any of our other features to help us stress the site before the final launch. If you find a bug, we're handing out bug bounties as well. Having a great exchange helps us but also helps the NXT community.

If we get 100 signs ups using that code and active on our site, we'll add NXT before our public launch.

Please let me know if you have any questions or feedback, Bill

Signed up

Everyone remember to add SUPPORT_NXT as the invite code so we get NXT added

Signed up and sealed, looks like a good exchange, so git yr asses over there......

[verymuchso]

@CfB, @JeanLuc anyone on dev team

"Account Control" was mentioned. Could someone give a brief explanation of this feature.

Thanks

bump.

JeanLuc

Could you possibly add a way to determine if an account is forging. You can turn on forging on the Generator class but you cant determine if an account is forging since the hasmaps are private on that class. Something like Generator.isForging(Account account)

Also. Could you please add a way to set the database and config file locations, since now the java current directory is used desktop client users must navigate to the actual folder that contains the jar (or executable launcher in my case) in order for NXT to reference the correct (relative) database location.

[Jean-Luc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.8.0e

http://download.nxtcrypto.org/nxt-client-0.8.0e.zip

sha256: 12ea7642953934b4b36cb833c500afefc9d1521776a298e3a6b6473cb0303a0c


Change log:

This release introduces a major change in the Nxt server architecture.
Instead of being a servlet run by Jetty, Nxt is now a standalone
application which itself launches Jetty servlets, when needed.
This should make it easier to use as a Java library, as it no longer
needs to be run inside a servlet container.

The Nxt configuration has been made more flexible, both for the end user
and for application developers. Nxt no longer uses web.xml, or any xml
files for that matter. Instead, a user-friendly properties file is used.

The layout of the distribution has been changed and simplified. Unpacking
the zip file will produce the following directory structure:

nxt/conf/
This is where the configuration files are kept. All default properties
are in conf/nxt-default.properties. You should never edit this file,
unless you are a packager or client developer who needs different
defaults for his distribution.
All default values are reasonable, so Nxt can just be started without
any configuration. If however the end user wants to customize some
parameters, the way to do that is to create another properties file,
conf/nxt.properties, containing ONLY the properties that need to be
different from the defaults. Nxt will read both nxt-default.properties
and nxt.properties, and the values in nxt.properties will override those
in nxt-default.properties.

nxt/html/
This contains the html files needed for the NRS javascript based client,
under html/nrs, the html-based tools such as admin.html and update.html
under html/tools, and the javadoc documentation for the Java API under
html/doc.

nxt/lib/
This is where all required Java libraries are kept - Jetty, H2 database,
and the JSON-simple library. All Jetty libraries that are not used by Nxt
are no longer included, which also results in a smaller distribution
package.

nxt/nxt.jar
This jar contains all compiled Nxt classes.

nxt/run.sh
This script is the simplest way to start Nxt, under Linux:
java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt
As you can see, the classpath needs to include nxt.jar, all the jars under
lib, and the conf directory.

Notably missing are start.jar, webapps, and the Jetty configuration
directories, which are no longer needed.

In addition to the switch to embedded Jetty, significant refactoring of the
code has been done, which may be of interest to users of the Java API. The
changes are too many to describe here, but can be easily seen by comparing
the javadoc of 0.8.0 with that of the 0.7 branch. Most notably, interfaces
have been defined for the Block and Transaction classes, the Blockchain
class has been split into several classes, and the Peer and User classes
have also seen some clean up.

Client developers using the Java API can override any of the default
properties by submitting a custom Properties object to Nxt.init().

The configurable properties in nxt-default.properties are all documented in
the comments in that file. Some additional details about those:

Nxt will start up to three different Jetty servers, if needed.

The peer networking server accepts http requests from peers. It is only
started if nxt.shareMyAddress=true (which is the default). If you are behind
a firewall and don't have an externally visible IP, you can set this to false
to disable it.

The port and host interface of the peer server are configurable. If you set
a non-default port in nxt.peerServerPort, this will be appended to the address
you announce to peers (this address should be set in nxt.myAddress). Using
non-default peer networking port hasn't been tested much though.

For a machine with multiple network interfaces, now you can specify on which
interface to bind each server. By default, nxt.peerServerHost=0.0.0.0 so the
peer networking server listens on all interfaces.

There are no hardcoded nxt.wellKnownPeers in the default properties files.
You are supposed to set those to your own preferred peers in nxt.properties.
However, if none are set, a random selection of nxtcrypto.org and nxtbase.com
public nodes will be used.

The DoS Filter is enabled for the peer server only.

The API server accepts http/json API requests. By default, now it runs on port
7876, and listens on the local 127.0.0.1 interface only. If you run a public
node and want to accept API requests from anyone, set nxt.apiServerHost to
0.0.0.0, and nxt.allowedBotHosts to * (or empty).

The nxt.apiResourceBase points to a directory of static html files that are
also served by the API server. Developers of clients using the http/json API
will want to customize this to point to their client html and javascript files.

The Jetty Cross Origin Filter can be enabled for the API server by setting
nxt.apiServerCORS=true (disabled by default).

The UI server is used for the NRS javascript client UI. By default it runs on
port 7875 and accepts requests from localhost only. Client developers using
the same API calls as the NRS client (not the http/json ones) should customize
nxt.uiResourceBase to point to their client html and javascript files instead.

SSL can be enabled for both the API server and the UI server (default disabled).
If this is done, the corresponding ports will accept https requests only. There
is no way currently to have both http and https supported at the same time, but
this can be added, I just didn't see the need for it.
If you enable SSL, you need to set nxt.keyStorePath and nxt.keyStorePassword,
and obviously you need to have your own SSL certificate (self-signed or signed
by a CA) in a keystore file. I have only tested this with a self-signed
certificate.

Client developers using the Java API will probably want to disable both the
API server and the UI server, and for users without a visible IP address
even the peer server.

Debugging output is now disabled by default, but can be enabled by setting
nxt.debug=true. Exception stack traces will still be logged, as long as
nxt.enableStackTraces=true. I hope there will be none of those.

The connection to the database can be completely customized, as the full
jdbc url used to connect to it is exposed in the properties file and can be
modified. Client developers that insist on being able to access the database
from a separate process, while Nxt is running, can do so by appending
;AUTO_SERVER=TRUE to the jdbc url, which will enable automatic mixed-mode.
This is disabled by default, but if you enable it and write to the database
while Nxt is running, expect things to break.

It is also possible to have the database in a different location, not just
in the current working directory, if you change the jdbc url accordingly.

To change the amount of memory used for the database cache, use the
nxt.dbCacheKB parameter, in kilobytes. If set to 0, by default 50 % of the
memory available to the JVM is used for database cache.

There have been no changes to the database schema, you should use your
existing nxt_db directory with this release too, instead of downloading
the blockchain from scratch.

This release is labeled experimental, but please try it. In particular, the
client developers and packagers should test it well, and if there are no
major issues, expect the 0.7 branch to become obsolete soon.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJTCIslAAoJEFOhyXc7+e2AnuoP/08xD1mjeNmv8/vBkSq39MhH
z+FToey65bbg2gQOSxMSdnr35C8oucS5kwBltCVvcXNyoyAEPZfsFfig3a1m5m2H
5TaJOywdH88ve9M1RouV2jdCo3Y7WAXC5uP8iHzp5YYVaR3XlhIwYW74uk62qQqn
NICuvmDhutDDcDGq+IkdR80x7XjqaReuXGZ44MHr2xNlQetkKLvB6kVcB7JhuZYt
KmufeCSC5qcFFdVsfZHN3xP5Mg+65VCGZayKDiJT0+uP5wfwlAPFqak25sLerfHn
fEi349W7afKw3FES1uvTIPBxnO4CShmhCzOvK4Yy3K5I4INSTWqQumEEDRL7STM2
wqhph5ewGEqJ0W+3yQN+j6AG33aawGoICLevkY2+g3+aaZ/cy1KjIiAns/ed33XB
nm2prnkvO2jNipNxcRUH5AP+o6+2k6LAfDxAzTHFWXboSQgr8RFWdwQP+R4Lvvbm
jaGiaqIvLzwyFboWgpkXwBZuhmVe1+L+icbUscUMW7gXm5XNpLgyOmPz3wuHUAe1
tqcpdW6EoiKIbHPgDkKyyRNugXuG18LdqHEW4RqpwuQIlBRoMkQ5Gzo7GSk7eLko
I+YNAktBiRv2W4dl1R1ngltwsoYCK4FBU4nWRhHjMzgjHrSCfaehi0rS42SbPfJE
cFUk+6MeaSGu+q35NOSD
=Zrbu
-----END PGP SIGNATURE-----

[zorke]

SWARM NEEDED

Here is the reddit post, please everyone sign up at Bittrex.

Hello NXT community,

I solicited feedback on another thread about which coins we should support on our exchange before our public launch. NXT was overwhelmingly recommended.

Before we make the final decision, we're providing a special invite code for NXT users to experience our site first hand. Go to https://bittrex.com/Account/Register and use SUPPORT_NXT as the invite code. This gets you past the invite code queue. Place some trades, enabled 2FA, or try any of our other features to help us stress the site before the final launch. If you find a bug, we're handing out bug bounties as well. Having a great exchange helps us but also helps the NXT community.

If we get 100 signs ups using that code and active on our site, we'll add NXT before our public launch.

Please let me know if you have any questions or feedback, Bill

Signed up

Everyone remember to add SUPPORT_NXT as the invite code so we get NXT added

Signed up and sealed, looks like a good exchange, so git yr asses over there......

I just managed to sign up as well. They had some email verification problems couple of hours ago, but now everything seems to be working fine.
So people get over there and lets get NXT to another exchange!

[DrearyUrbanite]

Is it good time to buy Nxt? I noticed the price just declined.

It is always a good time to buy NXT. I have been buying what I can, when I can since the first week of December, regardless of price. I feel that a year or two from now any current price differences will just look like quibbling.

[Jean-Luc]

"Account Control" was mentioned. Could someone give a brief explanation of this feature.

Ask CfB, I know nothing about it.

Could you possibly add a way to determine if an account is forging. You can turn on forging on the Generator class but you cant determine if an account is forging since the hasmaps are private on that class. Something like Generator.isForging(Account account)

There is Generator.getGenerator(secretPhrase) in 0.8.0, and a corresponding getForging http api request. The secretPhrase is required for privacy reasons, you shouldn't be able to find out which accounts are forging on a node unless you own that account.

Also. Could you please add a way to set the database and config file locations, since now the java current directory is used desktop client users must navigate to the actual folder that contains the jar (or executable launcher in my case) in order for NXT to reference the correct (relative) database location.

The full jdbc url is configurable now, and the nxt.properties file just needs to be in the classpath. Or you can completely substitute it with your own Properties object in Nxt.init() (this is not tested at all).

Yes, and I added the fullReset feature. It however increases the size of the database temporarily, until a compact is run at shutdown.

[SkillRoad]

Is it good time to buy Nxt? I noticed the price just declined.

I suppose it's a bargain now under 0.0001 compared to what it might be few months from now. And I think nxt may have value regardless of bitcoin already. Now that bitcoin fell there was a price correction for nxt from 7500 to 9000+. But this is just guessing.  
Heck what do I know. Have you ever looked at your Dgex-history, how dump can I be, D'ough!

-Quick Buy 8890 NXT at 0.00001350 each
-Sell 5000 NXT at 0.00001790 each

If I only knew then...

I guess I should just buy 20k at current price, if the price drop further, I'll get more.
The price will pump up in months, right?

Think first price will drop even further.

Bitcoin price will fall, the price will fall too Nxt

[verymuchso]

"Account Control" was mentioned. Could someone give a brief explanation of this feature.

Ask CfB, I know nothing about it.

Could you possibly add a way to determine if an account is forging. You can turn on forging on the Generator class but you cant determine if an account is forging since the hasmaps are private on that class. Something like Generator.isForging(Account account)

There is Generator.getGenerator(secretPhrase) in 0.8.0, and a corresponding getForging http api request. The secretPhrase is required for privacy reasons, you shouldn't be able to find out which accounts are forging on a node unless you own that account.

Also. Could you please add a way to set the database and config file locations, since now the java current directory is used desktop client users must navigate to the actual folder that contains the jar (or executable launcher in my case) in order for NXT to reference the correct (relative) database location.

The full jdbc url is configurable now, and the nxt.properties file just needs to be in the classpath. Or you can completely substitute it with your own Properties object in Nxt.init() (this is not tested at all).

Yes, and I added the fullReset feature. It however increases the size of the database temporarily, until a compact is run at shutdown.

Excellent ;-)

Btw. Am i still on the correct test net http://holms.cloudapp.net:6874/ it could be on my side (just did a major refactoring) but peers seem to be blacklisted constantly (at least the two peers available) so no blocks are downloaded. I will be integrating 0.8.0e immediately so lets see if troubles remain.

[verymuchso]

JeanLuc

Does the dev team (mostly you i guess) use an irc channel?

[Jean-Luc]

What do the Nxt stakeholders think about releasing the current source code earlier than April 1st?

We discussed this with CfB some time ago, as a way to get more developers involved and make it easier for client developers, not having to rely on decompiled code to see the Nxt internals. The copycats are already decompiling the Nxt classes, so there aren't any hidden secrets. I thought I would at least wait until I finish the 0.8.0 refactoring, but now that this is also released, it may be a good time to think about making the source open earlier, say March 1st?

[salsacz]

enterprise: so without transparent forging?

[Damelon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.8.0e

Thank you

[xyzzyx]

What do the Nxt stakeholders think about releasing the current source code earlier than April 1st?

We discussed this with CfB some time ago, as a way to get more developers involved and make it easier for client developers, not having to rely on decompiled code to see the Nxt internals. The copycats are already decompiling the Nxt classes, so there aren't any hidden secrets. I thought I would at least wait until I finish the 0.8.0 refactoring, but now that this is also released, it may be a good time to think about making the source open earlier, say March 1st?

I'm in favor of opening up the source earlier than April 1st.

[Jean-Luc]

Btw. Am i still on the correct test net http://holms.cloudapp.net:6874/ it could be on my side (just did a major refactoring) but peers seem to be blacklisted constantly (at least the two peers available) so no blocks are downloaded. I will be integrating 0.8.0e immediately so lets see if troubles remain.

I don't know, I admit I have never used the test net. CfB deals with updating the test net, and handling the AE bugfixes, I am not even sure what version the test net server is on currently.

[Jean-Luc]

enterprise: so without transparent forging?

The TF changes will be applied and released as they come from BCNext, even I don't know when and what the next steps are.

[BitcoinForumator]

What do the Nxt stakeholders think about releasing the current source code earlier than April 1st?

We discussed this with CfB some time ago, as a way to get more developers involved and make it easier for client developers, not having to rely on decompiled code to see the Nxt internals. The copycats are already decompiling the Nxt classes, so there aren't any hidden secrets. I thought I would at least wait until I finish the 0.8.0 refactoring, but now that this is also released, it may be a good time to think about making the source open earlier, say March 1st?

Release the Kraken.

[bitcoinpaul]

What do the Nxt stakeholders think about releasing the current source code earlier than April 1st?

We discussed this with CfB some time ago, as a way to get more developers involved and make it easier for client developers, not having to rely on decompiled code to see the Nxt internals. The copycats are already decompiling the Nxt classes, so there aren't any hidden secrets. I thought I would at least wait until I finish the 0.8.0 refactoring, but now that this is also released, it may be a good time to think about making the source open earlier, say March 1st?

Well, what about BCNext's 3rd plan - would an earlier release of the source code change anything?

[Jean-Luc]

JeanLuc

Does the dev team (mostly you i guess) use an irc channel?

No, I use jabber, when I don't forget to turn it on, but CfB doesn't use it... we communicate by email only.

[rickyjames]

NXT FUNDING COMMITTEE VOTE IS COMING MARCH 1

Eligible nominees:

^[GS]^, 2Kool4Skewl, abuelau, Allwelder , Anon136
Arckam_(frmelin), bitcoinpaul, bloodyrookie, brooklynbtc, buybitcoinscanada
Chanc3r, ChuckOne, CIYAM Open, Cointropolis_JustabitTime, Come-from-Beyond
Damelon, davethetrousers, drevil, EmoneyRu, EvilDave
ferment, Fry, hughmanwho, Jean-Luc, brooklynbtc
jl777, Joefox, Kattywampus, Klee, l8orre
landomata,laowai80, Mario123, msin, mww
nextern, opticalcarrier, Pandaisftw, Passion_ltc, PeercoinEnthusiast
pinarello, Pouncer, rickyjames, Ricot, salsacz
SecondLeo, smaragda, Asian Prepper, TwinWinNerD, Uniqueorn
Utopianfuture, VanBreuk, Wesleyh, Zahlen, ZeroTheGreat


If you are on this list and want to be on a NXT funding committee, go here:

https://bitcointalk.org/index.php?topic=479167.msg5280476#msg5280476

Background:

https://bitcointalk.org/index.php?topic=345619.msg5280786#msg5280786

Good luck to these nominees who have declared themselves candidates:


NXTmarketingfund: allwelder, Damelon,  Mario123
NXTtechdevfund: EmoneyRu
NXTinfrastructurefund: rickyjames