[ANN] [NFDv2] - NFD Coin - Thread locked

[Nxtblg]

NFD reached block 200'000 yesterday - and the forger who forged the lucky block got a prize of 200'000 NFD!

Congratulations to Account NFD-HJGQ-W4PY-YM3P-682XB! And thanks to everyone who's forging.

[1714050322]

1714050322

[1714050322]

1714050322

[1714050322]

1714050322

[1714050322]

1714050322

[raimch89]

miracle!!! all sold at 0.00000002

[Nxtblg]

miracle!!! all sold at 0.00000002

I saw that - and the miracle means I've had to scramble to adjust my terms for the three NFD Assets I'm maintaining. The next post has the details.

[Nxtblg]

Just an announcement: since the three NFD alias type of Assets I run - NFDNxtty, NFDSupeNet and NFDMMNxt - all have their prices calculated by using an implied price for Nxt in NFD terms using the low ask for NFD, NFD's recent rise to 3 has made me adjust the terms for each.

• For NFDMMNxt, whose announcement post is here, I've lowered the static offering price from 3300 NFD per unit to 2030. Details here.
• For NFDNxtty, whose announcement post is here, I've lowered the orderpair considerably to reflect the higher implied price of Nxt in NFD terms. Details here.
• I've done the same for NFDSupeNet, whose announcement post is here. Details in this post.

Of course, I'm happy that NFD has finally climbed up to 3 But its rise did mean some big changes in the numbers for each of my Assets on the NFD AE. I'm posting this announcement in part to notify and in part to show you I'm still on the ball.

[btc2nxt]

NFD reached block 200'000 yesterday

Great!

[lcharles123]

How to access from my computer, a wallet in VPS? what ports may be opened?

[Nxtblg]

How to access from my computer, a wallet in VPS? what ports may be opened?

8876 gives you access to the Web wallet. I think the other port is 8874.

[MaWo]

How to access from my computer, a wallet in VPS? what ports may be opened?

There are several ways to use a wallet in a vps.

1) Have a open wallet with or without SSL:
nxt.apiServerHost=0.0.0.0
nxt.allowedBotHosts=<your static home ip> or * for public access
and open port 8876

2) Use a VPN tunnel to your vps API port on vps localhost:8876.
Linux:
screen -S vpstunnel  ssh vps.host.tld -L 8876:localhost:8876 vmstat 1
CTRL-A D
This command starts a ssh with port forwarding of all incoming on local port 8876 is send to vps port 8876 through the tunnel.
You can connect to your vps at http://localhost:8876/

The safer method is a vpn tunnel to your vps.

[lcharles123]

How to access from my computer, a wallet in VPS? what ports may be opened?

There are several ways to use a wallet in a vps.

1) Have a open wallet with or without SSL:
nxt.apiServerHost=0.0.0.0
nxt.allowedBotHosts=<your static home ip> or * for public access
and open port 8876

2) Use a VPN tunnel to your vps API port on vps localhost:8876.
Linux:
screen -S vpstunnel  ssh vps.host.tld -L 8876:localhost:8876 vmstat 1
CTRL-A D
This command starts a ssh with port forwarding of all incoming on local port 8876 is send to vps port 8876 through the tunnel.
You can connect to your vps at http://localhost:8876/

The safer method is a vpn tunnel to your vps.

I try to open port 8876 in vps but dont work

Code:

 iptables -L | grep 8876
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8876
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8876
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8876flags: FIN,SYN,RST,ACK/SYN

Support said there is no other firewall barring ports.
The vpntunel returns [detached from 3056.vpstunnel]
This means it works, right?

But should that needs to the port 8876 open.

[MaWo]

How to access from my computer, a wallet in VPS? what ports may be opened?

There are several ways to use a wallet in a vps.

1) Have a open wallet with or without SSL:
nxt.apiServerHost=0.0.0.0
nxt.allowedBotHosts=<your static home ip> or * for public access
and open port 8876

2) Use a VPN tunnel to your vps API port on vps localhost:8876.
Linux:
screen -S vpstunnel  ssh vps.host.tld -L 8876:localhost:8876 vmstat 1
CTRL-A D
This command starts a ssh with port forwarding of all incoming on local port 8876 is send to vps port 8876 through the tunnel.
You can connect to your vps at http://localhost:8876/

The safer method is a vpn tunnel to your vps.

I try to open port 8876 in vps but dont work

Code:

 iptables -L | grep 8876
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8876
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8876
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8876flags: FIN,SYN,RST,ACK/SYN

Support said there is no other firewall barring ports.
The vpntunel returns [detached from 3056.vpstunnel]
This means it works, right?

But should that needs to the port 8876 open.

If you use the vpn tunnel, you only need a working ssh. You don't have to change nxt.apiServerHost, nxt.allowedBotHosts or iptables rules.
Please check your current open ports on your PC with
lsof -i -n
If you see a ssh listen on port 8876 then the vpn tunnel is working.
You should be able to access your vps at http://localhost:8876/

detached from 3056.vpstunnel is good.
You can reattach with "screen -rd"

[l8orre]

hey was I lucky! I just went to the repo to DL NFD and saw that MaWo had added NFD1.3.5 just half an hour ago  

looks like I stumbled in there when MaWo was updating- is it safe to use already?!

[MaWo]

hey was I lucky! I just went to the repo to DL NFD and saw that MaWo had added NFD1.3.5 just half an hour ago 

Hehe 

New NFD client release nfd-client-NFD-1.3.5.zip

This is the first release which stores most objects in the embedded SQL H2 database, instead of keeping them in memory.
This version will perform an initial build of the objects tables, which on a fast machine takes about 10 minutes,
but may take longer depending on your hardware. A VPS usually needs much longer! The database size will grow
during this rescan, but after shutdown it should shrink to around 560 MB. The memory usage of the client will increase.

This version is the first version which includes a checkpoint check at every 720th block height. It's triggered during
block download. Checkpoints are hard coded blockId checks. Only blockIds and heights in the blockchain until the time of the release are recognized.
You can manually force a check by starting a scan with validation (nxt.forceScan=true and nxt.forceValidate=true) at startup.
If the check detect that you are on a fork, it will pop off all blocks until last valid one.

This version has also a rewritten UPnP component. Now it takes care about myAddress on its own. UPnP is enabled by default.
Please add nxt.enableUPnP=false to your conf/nxt.properties to disable UPnP mapping.

With this version we introduce a simple client. Please use it with caution, it's still in experimental state.
http://localhost:8876/simple.html

Other important changes:
Blacklist peers with version older than 1.2.0.
Limit peer networking request and response sizes to prevent out of memory attacks
Insecure SSLv3 protocol disabled for API.
Improved digital good store UI.
Forced validation is disabled again.
Improved test page http://localhost:8876/test
Access to the H2 database at runtime http://localhost:8876/dbshell (only with nxt.enableDebugAPI=true)

Limit total number of known peers merged from NXT 1.4.10:
To prevent overloading a node with invalid peer addresses, the maximum total number of known peers is
limited to nxt.maxNumberOfKnownPeers (default 2000).
Once this number has been reached, new peer addresses are not added, and peers
that have been last connected to more than a week ago are removed from the known
peer list, provided the node has enough connected public peers, until the number
of known peers is again reduced to below nxt.minNumberOfKnownPeers (default
1000).

Also included are all new API calls, bug fixes and other improvements from NXT 1.3.5 and before.
Please see NXT changelogs for more details:

• changelogs/nxt-client-1.3.0.changelog.txt
• changelogs/nxt-client-1.3.1.changelog.txt
• changelogs/nxt-client-1.3.2.changelog.txt
• changelogs/nxt-client-1.3.3.changelog.txt
• changelogs/nxt-client-1.3.4.changelog.txt
• changelogs/nxt-client-1.3.5.changelog.txt

[MaWo]

hey was I lucky! I just went to the repo to DL NFD and saw that MaWo had added NFD1.3.5 just half an hour ago  

looks like I stumbled in there when MaWo was updating- is it safe to use already?!

Yes it is!

I suggest to set nxt.forceScan=true and nxt.forceValidate=true for the first start.
This allows the client to detect forks and popOff not valid blocks.

This will look like this:

Code:

2015-02-01 21:45:51 INFO: Checkpoint passed at block height 151200
2015-02-01 21:45:52 FINE: nxt.NxtException$NotValidException: Checkpoint not passed, blockId check failed at block height 151920. Expected 17295753430469899037 but found 4007331579693324843
nxt.NxtException$NotValidException: Checkpoint not passed, blockId check failed at block height 151920. Expected 17295753430469899037 but found 4007331579693324843
        at nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:945)
        at nxt.BlockchainProcessorImpl$6.run(BlockchainProcessorImpl.java:400)
        at nxt.util.ThreadPool$2.run(ThreadPool.java:114)
2015-02-01 21:45:52 FINE: Applying block 4007331579693324843 at height 151920 failed, deleting from database
2015-02-01 21:46:31 INFO: ...done at height 151919
2015-02-01 21:46:31 INFO: Fork isssue detected, resolving.
2015-02-01 21:46:31 FINE: Rollback from 151919 to 151200
2015-02-01 21:46:31 FINE: Running 2 final tasks...
2015-02-01 21:46:31 INFO: Started peer networking server at 0.0.0.0:8874
2015-02-01 21:46:31 INFO: Started API server at 127.0.0.1:8876
...

and after start up:

Code:

2015-02-01 21:46:31 FINE: Starting 8 background jobs
2015-02-01 21:46:31 FINE: Starting 2 delayed tasks
2015-02-01 21:46:31 INFO: Initialization took 512 seconds
2015-02-01 21:46:31 INFO: NFD server NFD-1.3.5 started successfully.
2015-02-01 21:46:31 FINE: Known peers: 96
2015-02-01 21:46:47 INFO: nxt.apiServerEnforcePOST = "true"
2015-02-01 21:47:22 INFO: Checkpoint passed at block height 151200
2015-02-01 21:47:23 INFO: Checkpoint passed at block height 151920
2015-02-01 21:47:27 INFO: Checkpoint passed at block height 152640
2015-02-01 21:47:28 INFO: Checkpoint passed at block height 153360
2015-02-01 21:47:29 INFO: Checkpoint passed at block height 154080
2015-02-01 21:47:35 INFO: Checkpoint passed at block height 154800
2015-02-01 21:47:35 INFO: received block 155000
...

Just to say don't worry. The client is only solving a fork situation.

[l8orre]

Thank You for the update!

I will download the blockchain tomorrow, need to go to bed now!

[lcharles123]

The tunnel works now, thanks!

Now as to client 1.3.5, the interface default and simple appears disfigured when I try to access it.



There are some additional configuration to be done?

Edit: this is because the ssh listen, on my local PC only

[MaWo]

The tunnel works now, thanks!

Now as to client 1.3.5, the interface default and simple appears disfigured when I try to access it.



There are some additional configuration to be done?

Normally it should work out of the box.

Which browser version do you use? Windows Firefox? Which version?

Could you also please try the online wallet?
https://nfdcoin.com/wallet/simple.html

[lcharles123]

The tunnel works now, thanks!

Now as to client 1.3.5, the interface default and simple appears disfigured when I try to access it.



There are some additional configuration to be done?

Normally it should work out of the box.

Which browser version do you use? Windows Firefox? Which version?

Could you also please try the online wallet?
https://nfdcoin.com/wallet/simple.html

Firefox 35.0.1 in Linux Mint 17 MATE 64bit
This happens because of the connection through ssh.
When I access the wallet from VPS, it functions properly.

[MaWo]

The tunnel works now, thanks!

Now as to client 1.3.5, the interface default and simple appears disfigured when I try to access it.

...
There are some additional configuration to be done?

Normally it should work out of the box.

Which browser version do you use? Windows Firefox? Which version?

Could you also please try the online wallet?
https://nfdcoin.com/wallet/simple.html

Firefox 35.0.1 in Linux Mint 17 MATE 64bit
This happens because of the connection through ssh.
When I access the wallet from VPS, it functions properly.

Are you able to access/read   http://localhost:8876/css/bootstrap.min.css ?

[lcharles123]

The tunnel works now, thanks!

Now as to client 1.3.5, the interface default and simple appears disfigured when I try to access it.

...
There are some additional configuration to be done?

Normally it should work out of the box.

Which browser version do you use? Windows Firefox? Which version?

Could you also please try the online wallet?
https://nfdcoin.com/wallet/simple.html

Firefox 35.0.1 in Linux Mint 17 MATE 64bit
This happens because of the connection through ssh.
When I access the wallet from VPS, it functions properly.

Are you able to access/read   http://localhost:8876/css/bootstrap.min.css ?

I can read this link.

I accessed through the putty using windows 7 and Firefox, and it worked properly.

The problem is access using Linux Mint, or ssh through the terminal.

[MaWo]

The tunnel works now, thanks!

Now as to client 1.3.5, the interface default and simple appears disfigured when I try to access it.

...
There are some additional configuration to be done?

Normally it should work out of the box.

Which browser version do you use? Windows Firefox? Which version?

Could you also please try the online wallet?
https://nfdcoin.com/wallet/simple.html

Firefox 35.0.1 in Linux Mint 17 MATE 64bit
This happens because of the connection through ssh.
When I access the wallet from VPS, it functions properly.

Are you able to access/read   http://localhost:8876/css/bootstrap.min.css ?

I can read this link.

I accessed through the putty using windows 7 and Firefox, and it worked properly.

The problem is access using Linux Mint, or ssh through the terminal.

I can not reproduce the ssh tunnel issue.
When I remove bootstrap.min.css then I see a similar screen.

Do you also have the same problem with google chrome?
If so, could you please do a right mouse click and chose "Inspect Element".
As next click on "Network", reload page and check whether a file is not accessible through the ssh tunnel.