NXT :: descendant of Bitcoin - Updated Information

[fmiboy]

now you should have nodeminer
./nodeminer <NXTacct> <NXTpassphrase>

James

if that phrase has whitespace in it, would that work as it should?

[jl777]

now you should have nodeminer
./nodeminer <NXTacct> <NXTpassphrase>

James

if that phrase has whitespace in it, would that work as it should?

I think you can have a space for the password, but you would need to put it in like:
"passphrase with space"

[nxtcoins]

http://nxtra.org/logo.png

NXTCOINS.COM

Premium NXT Domain

Auction Ending 4/12/2014 4:18 PM EST

Reserve of: $300 / BTC 0.47 Has been Met


http://www.sedo.com/auction/auction_detail.php?auction_id=170319

[jl777]

I running ubuntu and get the following error

./run.sh
In file included from get_dogeaddr.c:13:0:
NXTparse.h:16:23: fatal error: curl/curl.h: No such file or directory
 #include <curl/curl.h>
                       ^
compilation terminated.
In file included from nodeminer.c:19:0:
NXTparse.h:16:23: fatal error: curl/curl.h: No such file or directory
 #include <curl/curl.h>
                       ^
compilation terminated.

You need to install curl
sudo apt-get install curl

[fmiboy]

now you should have nodeminer
./nodeminer <NXTacct> <NXTpassphrase>

James

if that phrase has whitespace in it, would that work as it should?

I think you can have a space for the password, but you would need to put it in like:
"passphrase with space"

alright, it seem to work!

Code:

Get gateway.0 deposit address for 17102884928221738157 and set withdraw address to 
curl_easy_perform() failed: Timeout was reached (http://localhost:[b]6876[/b]/nxt?requestType=sendMessage&secretPhrase=...&recipient=18232225178877143084&message=edfedada6700000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003137313032383834393238323231373338313537&deadline=1440&fee=1)
CMD.(http://localhost:6876/nxt?requestType=sendMessage&secretPhrase=...&recipient=18232225178877143084&message=edfedada6700000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003137313032383834393238323231373338313537&deadline=1440&fee=1) ->  txid.(null)

shouldn't this port be 6876 => 7876?
also we are not using testnet?

[jl777]

now you should have nodeminer
./nodeminer <NXTacct> <NXTpassphrase>

James

if that phrase has whitespace in it, would that work as it should?

I think you can have a space for the password, but you would need to put it in like:
"passphrase with space"

alright, it seem to work!

Get gateway.0 deposit address for 17102884928221738157 and set withdraw address to
curl_easy_perform() failed: Timeout was reached (http://localhost:6876/nxt?requestType=sendMessage&secretPhrase=...&recipient=18232225178877143084&message=edfedada6700000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003137313032383834393238323231373338313537&deadline=1440&fee=1)
CMD.(http://localhost:6876/nxt?requestType=sendMessage&secretPhrase=...&recipient=18232225178877143084&message=edfedada6700000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003137313032383834393238323231373338313537&deadline=1440&fee=1) ->  txid.(null)

shouldn't this port be 6876 => 7876?
also we are not using testnet?

It is for testnet

[fmiboy]

shouldn't this port be 6876 => 7876?
also we are not using testnet?

It is for testnet

I see, I should run testnet locally to get access...

[jl777]

I running ubuntu and get the following error

./run.sh
In file included from get_dogeaddr.c:13:0:
NXTparse.h:16:23: fatal error: curl/curl.h: No such file or directory
 #include <curl/curl.h>
                       ^
compilation terminated.
In file included from nodeminer.c:19:0:
NXTparse.h:16:23: fatal error: curl/curl.h: No such file or directory
 #include <curl/curl.h>
                       ^
compilation terminated.

You need to install curl
sudo apt-get install curl

I have curl

which curl
/usr/bin/curl

do i need the development files, if so which?

Ooops, you are right
sudo aptitude install libcurl-dev

[jl777]

shouldn't this port be 6876 => 7876?
also we are not using testnet?

It is for testnet

I see, I should run testnet locally to get access...

If you are running 8.8, you just need to change the preferences file in nxt/conf
nxt.testnetPeers=bug.airdns.org
nxt.isTestnet=true

[jl777]

Im not sure what it is doing, but it seems to be doing what it is supposed to do

Its reporting all the active peers, which are then used to calculate the most useful nodes and allocating nodecoins based on that.

current 33.33333333 0.27705624 nodecoins | sent 56.00000000

Do you see the nodecoins in your NXT AE "my assets"?

James

[jl777]

Im not sure what it is doing, but it seems to be doing what it is supposed to do

Its reporting all the active peers, which are then used to calculate the most useful nodes and allocating nodecoins based on that.

current 33.33333333 0.27705624 nodecoins | sent 56.00000000

Do you see the nodecoins in your NXT AE "my assets"?

James

Yes

Code:

nodecoin	110	999'999'999	0.00001%	/	/	/	Transfer

Cool!
Now, just need more people running it to find any problems.Not sure the nodecoin allocation is quite right yet

James

[Fern]

James, do you want us to just start trading it ?

[Eadeqa]

35 char is more than enough. Don't need to add special character

Exactly.

50 characters is even stronger than 256-bit, even though curve25519 is only 128-bit  (at best) strong.

[Eadeqa]

Here's my new logic for my client http://nxtra.org/nxt-client (to be available later today, not yet uploaded)

Thoughts?

very cool adding the random word for passwd.
There are space between random words of password  or just consecutive random words without space?

Spaces

[CIYAM]

I've completed the 1st draft of my article about forging from a probabilistic point of view: http://www.docdroid.net/9yub/forging.pdf.html

Comments, suggestions, (and donations ) are welcome!

Please, discuss it here: https://forums.nxtcrypto.org/viewtopic.php?f=17&t=836 (or send me a PM). Unfortunately, I won't be able to follow this thread in the next few days.

+1. Ciyam should like it a lot.

Great stuff - I hope some donations are sent for his efforts.

@mathcl - I think I found a spelling error:

...then the system should be able to fence off the attack by other means, which we shall not discuss in tis note.

(probably should be "this paper" instead).

[MadCow]

Jimmy Wales is discussing wikipedia potentially accepting bitcoins on reddit

http://www.reddit.com/r/Bitcoin/comments/201fa6/hello_from_jimmy_wales_of_wikipedia/


Interesting quote

What I've said for a long time continues to be true. I'm "cautiously pessimistic" about Bitcoin.
What I mean by that is that I'm loving the idea but I see a lot of real problems. One of my concerns is that the complexity of it all will hinder adoption.
I also have concerns that are perhaps born out of a lack of full understanding. What happens when BTC mining returns drop significantly lower than costs? Will transactions fees be sufficient to induce miners to continue participating?
But I'm not forecasting doom for BTC. I'm cautious. I don't know enough to say for sure.

[xyzzyx]

Here's an interesting service for Bitcoin using multisignatures:

https://bitcointalk.org/index.php?topic=502830.0

Should multisig be implemented in Nxt, a similar but decentralized service would be a good idea to explore.

[Eadeqa]

Is this 1626 words dictionary enough now or should we go with a bigger one, also to allow less words?

Why?

If crypto.getRandomValues is working properly then 1626 is just perfect. If crypto.getRandomValues  isn't working then even 20,000 words won't be enough, as real entropy will be limited by the random number generator.

Some people are having difficulty comprehending that 128-bit is a very big number.

Lets assume the worst case.

Lets say in two years, 1 billion people are using wesleh'sy client and  everyone created their pass phrase using these randomly generated words.  

Now lets assume that every bitcoin miner in the world  (millions of dollars of electricity per day)  all work together to find just one of these 1 billion randomly generated pass phrase. The current hash rate on bitcoin network is 3 million GH/s.

How long would it take for the entire bitcoin network combined to find just one of 1 billion pass phrase?

Total number (aprox 128-bit)  1626^12 = 3.4×10^38

1 billion users, 3.4×10^38 / 1000000000 = 3.4 x 10^29

Now the entire bitcoin network combined works to find just one pass phrase   3.4 x 10^29 / 300000000000000000  =  1133333333333 seconds

that's 36,000 years (36 thousand years).

lets assume they get very lucky and find one pass phrase only after 1% of search, that's still  3 thousand years

And after all that work (and electricity) and 3 thousand years later,  they might discover that the account they did find only had 2 Nxt  in it.

The point is that  the problem (if there is) will be with random number generator -- not with number of words, which are just fine.

That's why I keep saying you don't need 50 or 100 character password  (not even 35, actually  -- 25 is fine). . It doesn't add any more security. If there is a security hole (like for example keyloggers) even 1 million character password isn't going to help.

[allwelder]

Any suggestions about Parallel Chains? If not then I'll stick to BCNext's draft.

maximum parallel chains is ?
all parallel chains use the same Nxt Wallet?

[CIYAM]

That's why I keep saying you don't need 50 or 100 character password  (not even 35, actually  -- 25 is fine). . It doesn't add any more security. If there is a security hole (like for example keyloggers) even 1 million character password isn't going to help.

Agreed - unfortunately people don't *think* or bother with things like *math* here - instead they just pluck numbers like 35 or 50 "out of thin air" and make it a *rule* that must be followed.