Topic: NXT :: descendant of Bitcoin - Updated Information - page 2406. (Read 2761626 times)
I don't have but positive predictions, This is the ONLY crypto aside Bitcoin that REALLY caught my attention.
if I don't hallmark my computer, my stake will be safe while forging?
- if your computer is secure, then it is safe to forge. But during the zombie attacks your (not hallmarked) computer would be at the risk to be cutted from the Nxt network. 
How can you prevent your computer for being a huge hacking target when usually only big stakes connect to the mining network?
- those big Thanks for answering me. So are you saying that, if I don't hallmark my computer, my stake will be safe while forging?
How can you prevent your computer for being a huge hacking target when usually only big stakes connect to the mining network?
- those big Hey People, what are your prediciotns of the NXT coin for the upcoming month? And the future? Thanks a lot!
You want to hear things like "NXT TO DA MOON!!" or "Get ready for the NXT train leaving for the Saturn!!"?
lol no, just a serieus prediction…
The first year will see some bugs, major ups and downs in market cap (due to genesis founders selling) but also wide adoption if the source code is released in Jan. and features implemented. I'm going to wait things out for the long term as I see Nxt taking over BTC (yes I'm serious)
Hey People, what are your prediciotns of the NXT coin for the upcoming month? And the future? Thanks a lot!
You want to hear things like "NXT TO DA MOON!!" or "Get ready for the NXT train leaving for the Saturn!!"?
lol no, just a serieus prediction…
I think it is a really good investment, especially for these prices on dgex.com
If the majority of the features really will be implemented (which will be, I am pretty sure) and the big stakeholder (3 million and more) will distribute their coins (here I am not so sure anymore) this will be a success story.
I don´t know BCNext, only heard about him, but he is having some quite good ideas for most of the problems (even for the issue where stakeholders are sitting and holing on their coins), so I am sure they will make this a fucking good tool. I am all in.
Hey People, what are your prediciotns of the NXT coin for the upcoming month? And the future? Thanks a lot!
You want to hear things like "NXT TO DA MOON!!" or "Get ready for the NXT train leaving for the Saturn!!"?
lol no, just a serieus prediction…
Hey People, what are your prediciotns of the NXT coin for the upcoming month? And the future? Thanks a lot!
You want to hear things like "NXT TO DA MOON!!" or "Get ready for the NXT train leaving for the Saturn!!"?
Hey People, what are your prediciotns of the NXT coin for the upcoming month? And the future? Thanks a lot!
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?
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?
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?
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.
I've seen an original way to mark Nxt account number:
I like it.
I like it.
nevermind
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?
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.
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?
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?
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.
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?
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.
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?
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?
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.
Am I the only who runs CentOS these days?
Jump to: