NXT :: descendant of Bitcoin - Updated Information

[gbeirn]

Hmmm, can you? I never tried that. I assumed it had to be a IP address not a FQDN

yeah, it'll work. but the IP resolved by the dynamic dns must still be visible to the world, must not be behind NAT/router.

Are you sure? I just tried it here using both IP address and host name and came up with two different hallmarks:

fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac34140063686970686 56164732e676f74646e732e636f6d640000008a2d33015cd65b85d9388aa2235ac84e33a833cdda e1c954db12edb44374c470cef372b2066cf8da20d7e96f7fad1523e76a1dab2cd36259aaa3673b2 6ad668691c19369a9

fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac340d0032342e31333 12e3137322e3334640000008a2d33010a7def9f4266dc3061fb9c6d41a1651b164d28b1a9b6832a cfdeb8f46145d7780a4abfd5766127515b588492b557b8e19c2bce24b4e93bec79fa2c250a06336 203

Clearly the data inputted in the fields if different, but would both hallmarks still be vaild?

And it could be behind a NAT as long as the ports are open/forwarded.

[Come-from-Beyond]

Ripple is No. 2 on Coinmarketcap  

They put Mastercoin to push Nxt back, now they has put Ripple, what's nxt?

[laowai80]

Hmmm, can you? I never tried that. I assumed it had to be a IP address not a FQDN

yeah, it'll work. but the IP resolved by the dynamic dns must still be visible to the world, must not be behind NAT/router.

Are you sure? I just tried it here using both IP address and host name and came up with two different hallmarks:

fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac34140063686970686 56164732e676f74646e732e636f6d640000008a2d33015cd65b85d9388aa2235ac84e33a833cdda e1c954db12edb44374c470cef372b2066cf8da20d7e96f7fad1523e76a1dab2cd36259aaa3673b2 6ad668691c19369a9

fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac340d0032342e31333 12e3137322e3334640000008a2d33010a7def9f4266dc3061fb9c6d41a1651b164d28b1a9b6832a cfdeb8f46145d7780a4abfd5766127515b588492b557b8e19c2bce24b4e93bec79fa2c250a06336 203

Clearly the data inputted in the fields if different, but would both hallmarks still be vaild?

And it could be behind a NAT as long as the ports are open/forwarded.

put domain in myaddress in web.xml and put hallmark you generated against that domain.

then sign up at dynamic dns service provider, and have it resolve your domain to your dynamic ip.


both hallmarks are valid, but what you put in myaddress parameter must coincide with the hallmark.

[NxtChoice]

Try to set it up on a dynamic dns service, and tell us if it reliably works.

http://freedns.afraid.org/
http://www.noip.com/

Well no the problem is the IP address must be used to create the hallmark. This would help for a well-known peer.

You can put the domain in the hallmark generation form,
and set the domain in the MyAddress parameter, no?

Hmmm, can you? I never tried that. I assumed it had to be a IP address not a FQDN
[/quote]

The real case is that I have my wireless router, and I use Nxt client in my computer through the wifi connection, and I also forge at RaspPI 24/7 through wire connection with the router.

My router is a PPP dialing.

[laowai80]

The real case is that I have my wireless router, and I use Nxt client in my computer through the wifi connection, and I also forge at RaspPI 24/7 through wire connection with the router.

My router is a PPP dialing.

yeah, so you're behind a router, it's not just dynamic ip issue, but more complicated

[Come-from-Beyond]

if i send a payment on an orphaned chain how do i get it back?

*edit* /get it over to the right chain

When blocks become orphaned their transactions r being returned to unconfirmed transactions pool.

[Come-from-Beyond]

Does the DDoS cause the nodes to max out their transmit bandwidth or receive bandwidth?

Former

[davethetrousers]

Using portforward, a dyn DNS service and updating hallmark and address in the config on every IP change should work... Inconvenient, but doable.

[Come-from-Beyond]

I am currently trying to get it running on my raspy, but when I access the frontend I get: java.lang.NullPointerException

I can click the message away but after unlocking everything is empty, no blocks, no transactions and so on.

This is due to corrupted files. Delete *.nxt and do it again.

[gbeirn]

Hmmm, can you? I never tried that. I assumed it had to be a IP address not a FQDN

yeah, it'll work. but the IP resolved by the dynamic dns must still be visible to the world, must not be behind NAT/router.

Are you sure? I just tried it here using both IP address and host name and came up with two different hallmarks:

fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac34140063686970686 56164732e676f74646e732e636f6d640000008a2d33015cd65b85d9388aa2235ac84e33a833cdda e1c954db12edb44374c470cef372b2066cf8da20d7e96f7fad1523e76a1dab2cd36259aaa3673b2 6ad668691c19369a9

fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac340d0032342e31333 12e3137322e3334640000008a2d33010a7def9f4266dc3061fb9c6d41a1651b164d28b1a9b6832a cfdeb8f46145d7780a4abfd5766127515b588492b557b8e19c2bce24b4e93bec79fa2c250a06336 203

Clearly the data inputted in the fields if different, but would both hallmarks still be vaild?

And it could be behind a NAT as long as the ports are open/forwarded.

put domain in myaddress in web.xml and put hallmark you generated against that domain.

then sign up at dynamic dns service provider, and have it resolve your domain to your dynamic ip.


both hallmarks are valid, but what you put in myaddress parameter must coincide with the hallmark.

Thanks that totally makes sense!

[freigeist]

When I last looked (probably v0.4.0), it appeared that the code sent to a set of nodes sequentially, which could presumably be very fast or very slow (depending on the connect/read timeouts configured, and the state of the other nodes at the time). Is there any reason why this can't be done as parallel tasks?

Yes, parallelization is more sophisticated. Current implementation is called Nxt Reference Software. We could optimize networking by using binary protocol instead of JSON, but this would increase entry barrier for newbie programmers. The same is applied to other parts of NRS.

Maybe it would be good to have 2 types of protocols JSON for local communication
and binary for remote communication or maybe use
data compression while sending data.
For example you or the developer that would continue work on the project
could create a procedure or library to convert JSON data to binary data.
What are your thoughts about this?!

[laowai80]

Does the DDoS cause the nodes to max out their transmit bandwidth or receive bandwidth?

Former

hm, why is it vice versa here now

[msin]

Ripple is No. 2 on Coinmarketcap  

They put Mastercoin to push Nxt back, now they has put Ripple, what's nxt?

Well, I guess the company that owns Ripple is rich now.

[killver]

I am currently trying to get it running on my raspy, but when I access the frontend I get: java.lang.NullPointerException

I can click the message away but after unlocking everything is empty, no blocks, no transactions and so on.

Did you use my all-in-one pack? What does the server daemon say on startup? Any exceptions there?

Yes, I am using your pack.

It seems that there is a problem here:

[2013-12-26 15:51:14.713] Nxt 0.4.7e started.
[2013-12-26 15:51:14.751] "blockchainStoragePath" = "blockchain.nrs"
[2013-12-26 15:51:14.915] "myScheme" = "http"
[2013-12-26 15:51:14.935] "myPort" = "7874"
[2013-12-26 15:51:14.953] "myAddress" = ""
[2013-12-26 15:51:14.955] "shareMyAddress" = "true"
[2013-12-26 15:51:14.963] "myHallmark" = ""
[2013-12-26 15:51:14.965] "wellKnownPeers" = "109.230.224.65; 78.46.63.221; 95.85.22.142"
[2013-12-26 15:51:15.039] "maxNumberOfConnectedPublicPeers" = "5"
[2013-12-26 15:51:15.052] "connectTimeout" = "2000"
[2013-12-26 15:51:15.058] "readTimeout" = "5000"
[2013-12-26 15:51:15.062] "enableHallmarkProtection" = "true"
[2013-12-26 15:51:15.071] "pushThreshold" = "0"
[2013-12-26 15:51:15.082] "pullThreshold" = "0"
[2013-12-26 15:51:15.089] "allowedUserHosts" = "127.0.0.1; 192.168.178.21; localhost; 0:0:0:0:0:0:0:1;"
[2013-12-26 15:51:15.092] "allowedBotHosts" = "127.0.0.1; localhost; 0:0:0:0:0:0:0:1;"
[2013-12-26 15:51:15.100] "blacklistingPeriod" = "300000"
[2013-12-26 15:51:15.119] "communicationLoggingMask" = "0"
[2013-12-26 15:51:15.132] Loading transactions...
[2013-12-26 15:51:53.401] 10: java.io.EOFException

It seemed to work before I added an IP address to the alloweduserhosts, but dunno what I did wrong.

[gbeirn]

Using portforward, a dyn DNS service and updating hallmark and address in the config on every IP change should work... Inconvenient, but doable.

Nope, no need. As I just learned, create the hallmark using your Dyn DNS service host name and put that hallmark along with the hostname (not IP) into web.xml, not the IP address.

[msin]

Can someone post a "wget" link to 0.4.8 for VPS?  Thanks.

[laowai80]

Using portforward, a dyn DNS service and updating hallmark and address in the config on every IP change should work... Inconvenient, but doable.

there is no need to update hallmark and address on every ip change,
you generate hallmark against a domain, you put domain as myaddress and that hallmark into config, that's all.

[Anon136]

im not getting any connections. i probably should update my "wellKnownPeers" parameter in web.xml right? if so can anyone tell me a couple of good strong nodes to set "wellKnownPeers" with?

[Come-from-Beyond]

What are your thoughts about this?!

I proposed similar way but BCNext said that everything must be as simple as possible. He even refused to add gzip compression.

[laowai80]

im not getting any connections. i probably should update my "wellKnownPeers" parameter in web.xml right? if so can anyone tell me a couple of good strong nodes to set "wellKnownPeers" with?

95.85.46.233; 162.243.140.133; 146.185.129.54; 162.243.117.63; 192.241.155.44; 162.243.214.68; 95.85.46.164; 162.243.216.55; 162.243.143.15; 95.85.46.249; 93.190.92.74; 37.209.120.192; 93.190.92.75; 85.25.134.59; 93.190.92.76; vps1.nxtcrypto.org;  vps2.nxtcrypto.org;  vps3.nxtcrypto.org;  vps4.nxtcrypto.org;  vps5.nxtcrypto.org; nxtwallet.com; 31.220.50.208; nxt.ddos.me; 203.174.12.25; 88.198.142.92; 66.197.138.90; 64.120.180.106; 109.230.224.65;