NXT :: descendant of Bitcoin - Updated Information

[verymuchso]

JeanLuc

You probably already know this but still, the addListener and removeListener are on BlockchainProcessorImpl and TransactionProcessorImpl only and not on their interfaces.

Code is looking good! Thank you for implementing the features i asked for.

-Edit-

Sorry, just seen the Observable interface, never mind

[Passion_ltc]

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?

Why such hurry?

[Jerical13]

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 ..

Client issues are really not the issue. those kinds of problems are an inconvenience, but in the long term they are something that can be overcome. Honestly, to someone like myself who doesn't have a high level of knowledge when it comes to computers, the NXT client is difficult to operate, but that problem will be solved in time as the software is developed. The real problem is indicated by the reluctance of people to adopt NXT because of the method of dispersal. People don't want to commit to NXT because you have to invest in the currency and can't get NXT by mining in the way that Bitcoin and most other Cryptos are mined. People think that proof of stake is unfair to those who don't have a lot of stake and they don't want to run the client for the sake of the network with a decreased probability in receiving free coins. So what is going to happen when Bitcoin is mined out and there is NO chance of receiving coins for operating 1000 watt mining equipment. Are people still going to be willing to maintain the Bitcoin network then? There is an initial investment required to become a NXTER but once that investment is made, maintaining the network by running your client is not as much of a liability as running asic equipment, the return from forging is directly proportional to your investment, and forging is perpetual and you will never run out of coins to forge. People who support Bitcoin really don't support Bitcoin (most of them anyway). They support mining free Bitcoins, and eventually there are going to be no more Bitcoins to mine and running mining equipment will be an expense with no possibility of return. In that respect, Bitcoin is a sinking ship and when there are no more coins to mine, Bitcoin supporters will abandon the network like rats........ along with the long confirmation times and malleability problems........ and block chain downloading..........and overall lack of usable features Bitcoin is a walking dinosaur.

[SkillRoad]

https://localhost:7875/ not working - only http!

I also

[CIYAM]

https://localhost:7875/ not working - only http!

I also

Code:

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.

I am guessing that it ain't so simple to run it using HTTPS now although really if you are running it locally I don't think HTTP is a problem (if something running locally is sniffing your packets then I'd be surprised if it wasn't also logging your keystrokes).

[timmyd]

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?

Why such hurry?

agreed, is there pressure to release this source? Or are you asking for the release to gain a bit of help jean luc if its the latter then heck go for it. But if its just to please the like of fc etc then leave it until april as planned.

[Jean-Luc]

Code:

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.

I am guessing that it ain't so simple to run it using HTTPS now although really if you are running it locally I don't think HTTP is a problem (if something running locally is sniffing your packets then I'd be surprised if it wasn't also logging your keystrokes).

It is very simple to generate a self-signed certificate actually, just use the keytool command that comes with the JDK:
keytool -keystore keystore -alias nxt  -genkey -keyalg RSA
It will ask you to choose a password (that you will later need to enter in nxt.properties as nxt.keyStorePassword), and some mostly optional details for the certificate, and then generate a keystore file which you need to put in the nxt directory and point nxt.keyStorePath to it.

[wesleyh]

If someone could send some testnxt to 9875620683701552997 please, thanks!

[CIYAM]

It is very simple to generate a self-signed certificate actually, just use the keytool command that comes with the JDK:
keytool -keystore keystore -alias nxt  -genkey -keyalg RSA
It will ask you to choose a password (that you will later need to enter in nxt.properties as nxt.keyStorePassword), and some mostly optional details for the certificate, and then generate a keystore file which you need to put in the nxt directory and point nxt.keyStorePath to it.

Thanks - not all of us are Java developers (I know how to do a self-signed cert using openssl but had never come across "keytool" before).

I don't believe it's a big deal (as HTTP should be fine locally) but it does tend to *surprise* end users when something that "just worked" before now doesn't and apparently they have to "open the hood" and "do some wiring changes" to make it work again.

[MIG.fish]

NxtOk.com update
1.Add Personal Account Statistics: balance trend, transfer in/out and fee

https://bitcointalk.org/index.php?topic=470463.new#new

[martismartis]

Public node on Android is running, can connect only locally. Can't connect from outside. Both api nxt.allowedBotHosts and NRS nxt.allowedUserHosts set to *

What more I should do? Ports 7874 and 7875 forwarding is done on router.

[CryptKeeper]

I am guessing that it ain't so simple to run it using HTTPS now although really if you are running it locally I don't think HTTP is a problem (if something running locally is sniffing your packets then I'd be surprised if it wasn't also logging your keystrokes).

Good thought, thanks for pointing this out!

So not much use locally, but if you want to connect remotely, HTTPS gives you extra security.

[Jean-Luc]

agreed, is there pressure to release this source? Or are you asking for the release to gain a bit of help jean luc if its the latter then heck go for it. But if its just to please the like of fc etc then leave it until april as planned.

There is no pressure, I was just putting it up for discussion.

I don't feel I need help, yet, because many of my changes are still so fundamental that I am changing code all over the place and this type of work will be difficult to coordinate when there are many developers. CfB has to re-read the code and figure it out again every time I make some drastic refactoring like the last one. But eventually the code will stabilize and it will be possible to have several developers contributing at the same time. I also don't want to slow down the developers of clients and installers who want to peek into the source.

Should we create a poll and vote for it...

[Jean-Luc]

Public node on Android is running, can connect only locally. Can't connect from outside. Both api nxt.allowedBotHosts and NRS nxt.allowedUserHosts set to *

What more I should do? Ports 7874 and 7875 forwarding is done on router.

Try setting nxt.apiServerHost=0.0.0.0 and nxt.uiServerHost=0.0.0.0 to allow those servers to listen on all interfaces. The default is 127.0.0.1 only.

[verymuchso]

agreed, is there pressure to release this source? Or are you asking for the release to gain a bit of help jean luc if its the latter then heck go for it. But if its just to please the like of fc etc then leave it until april as planned.

There is no pressure, I was just putting it up for discussion.

I don't feel I need help, yet, because many of my changes are still so fundamental that I am changing code all over the place and this type of work will be difficult to coordinate when there are many developers. CfB has to re-read the code and figure it out again every time I make some drastic refactoring like the last one. But eventually the code will stabilize and it will be possible to have several developers contributing at the same time. I also don't want to slow down the developers of clients and installers who want to peek into the source.

Should we create a poll and vote for it...

Code is perfectly readable in the decompiler.

-Edit- I use this one http://jd.benow.ca/

[martismartis]

Public node on Android is running, can connect only locally. Can't connect from outside. Both api nxt.allowedBotHosts and NRS nxt.allowedUserHosts set to *

What more I should do? Ports 7874 and 7875 forwarding is done on router.

Try setting nxt.apiServerHost=0.0.0.0 and nxt.uiServerHost=0.0.0.0 to allow those servers to listen on all interfaces. The default is 127.0.0.1 only.

Vuala! Working now http://217.17.88.5:7875/

Thank you Jean-Luc.

P.S. How to access admin.html from client? localhost:7875/admin.html not found, also html/tools/admin.html

[allwelder]

all of us,please come here vote for Nxt to let the btc38(an exchange platform of China) add Nxt to their database.

http://www.coin38.org/forum.php?mod=viewthread&tid=1672

It is a good chance for Nxt promotion.
Nxt is on the 18 floor.

edit:new user need to change the avatar first.
TKS.

[Jean-Luc]

P.S. How to access admin.html from client? localhost:7875/admin.html not found, also html/tools/admin.html

Try http://localhost:7876/admin.html . Those tools use the API server which is now on port 7876, this is why I made the html files also served from that port.

[abctc]

If someone could send some testnxt to 9875620683701552997 please, thanks!

- 10k testNXT sent.

[opticalcarrier]

https://localhost:7875/ not working - only http!

I also

Code:

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.

I am guessing that it ain't so simple to run it using HTTPS now although really if you are running it locally I don't think HTTP is a problem (if something running locally is sniffing your packets then I'd be surprised if it wasn't also logging your keystrokes).

Also, if we enable https,  will the update tool we have that requires non-https cease to work?

Ive wiki'ed a howto for ssl on current codebase,  ill get it ipdated before the 0.7 train obsoletes.