NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

Does anyone have problems with 0.3.18 or it's only me?

[ferment]

If u announce address of ur host via "myAddress" u must set it to the "host" value returned by http://otherserver.com:7874/nxt?requestType=getMyInfo . In one of the next versions nodes will begin checking that it matches the address returned by http://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#getRemoteHost()

I switched mine back to the IP address. From what I understand, to get FQDN the ip of the host listed in the NXT client, it needs to have reverse DNS setup. I just requested it for my node (64.22.108.120) and will test after it resolves.

-Ferm

[plasticAiredale]

Does anyone have problems with 0.3.18 or it's only me?

Working for me. (Windows 7)

[Come-from-Beyond]

If u announce address of ur host via "myAddress" u must set it to the "host" value returned by http://otherserver.com:7874/nxt?requestType=getMyInfo . In one of the next versions nodes will begin checking that it matches the address returned by http://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#getRemoteHost()

I switched mine back to the IP address. From what I understand, to get FQDN the ip of the host listed in the NXT client, it needs to have reverse DNS setup. I just requested it for my node (64.22.108.120) and will test after it resolves.

-Ferm

After Decentralized DNS launched such problems will disappear.

[Come-from-Beyond]

Does anyone have problems with 0.3.18 or it's only me?

Working for me. (Windows 7)

It may hung in 10 mins. Keep watching.

[klee]

MacOS goes smooth by far....

[plasticAiredale]

Does anyone have problems with 0.3.18 or it's only me?

Working for me. (Windows 7)

It may hung in 10 mins. Keep watching.

16 minutes in...still going strong (just got block 13370). I'll still keep an eye on it though.

[MyZhre]

So far so good for me, Ubuntu 13.04

[Come-from-Beyond]

Am I the only who runs CentOS these days?

[laowai80]

Am I the only who runs CentOS these days?

Certainly not. I'd choose CentOS over Debian for a server, but vice versa for a desktop.

[opticalcarrier]

regarding this hallmark thing, and advertising our actual IP address...

I have DSL that uses PPP.  As such my IP will frequently change.  My router does have dynamic DNS configured to update my particular DNS name with my IP address after every reboot.

Can I use my DDNS name when I go through the hallmark thing?  Will it cause any problems if I never code my IPv4 address?

[Come-from-Beyond]

regarding this hallmark thing, and advertising our actual IP address...

I have DSL that uses PPP.  As such my IP will frequently change.  My router does have dynamic DNS configured to update my particular DNS name with my IP address after every reboot.

Can I use my DDNS name when I go through the hallmark thing?  Will it cause any problems if I never code my IPv4 address?

Check http://88.198.210.245:7874/nxt?requestType=getMyInfo
If u don't see host name then u have to wait for the decentralized DNS.

[JohnyCrypt]

Am I the only who runs CentOS these days?

I got tired of RPM/Yum hell. Now I use Ubuntu LTS whenever possible.

v0.3.18 up and running on 12.04LTS with no issues. The blockchain relocation works no problem.

[opticalcarrier]

and also, you may want to reconsider allowing the client to be unlocked before having a complete blockchain...

Per the other thread on address length, it appears that if a never-ever-before-been-entered-into-a-client passphrase is entered that results in an already existing visibleAccountId that shares the first 64bits of the full 256bit address with another passphrase, then the client doesnt allow that passphrase.

If you allow clients to unlock before having a complete blockchain, how will you deal with address collision then?

[Come-from-Beyond]

and also, you may want to reconsider allowing the client to be unlocked before having a complete blockchain...

Per the other thread on address length, it appears that if a never-ever-before-been-entered-into-a-client passphrase is entered that results in an already existing visibleAccountId that shares the first 64bits of the full 256bit address with another passphrase, then the client doesnt allow that passphrase.

If you allow clients to unlock before having a complete blockchain, how will you deal with address collision then?

Good point. But BCNext decides.

[opticalcarrier]

nevermind

[Come-from-Beyond]

I've seen an original way to mark Nxt account number:



I like it.

[lophie]

and also, you may want to reconsider allowing the client to be unlocked before having a complete blockchain...

Per the other thread on address length, it appears that if a never-ever-before-been-entered-into-a-client passphrase is entered that results in an already existing visibleAccountId that shares the first 64bits of the full 256bit address with another passphrase, then the client doesnt allow that passphrase.

If you allow clients to unlock before having a complete blockchain, how will you deal with address collision then?

Good point. But BCNext decides.

I would be glad to take some decisions off to my favourite IDE and Hatsune Miku, impatiently waiting for the source code.

[Polvos]

I find myself really curious about this currency. ¿How do you prevent hackers from stealing your stake while your account is opened and yor computer is mining?

Editing: more questions.

¿How can you prevent your computer for being a huge hacking target when usually only big stakes connect to the mining network?

[twistelaar]

Hey People, what are your prediciotns of the NXT coin for the upcoming month? And the future? Thanks a lot!