NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

A "#" in the secret in the url before the host?

Hehe, seems so. It must be url-encoded.

[1714156269]

1714156269

[LightningFury]

works

"#" to "%23"

[Jean-Luc]

Yes, you have to url-encode at least # and &, that I can think of. You can't even fix it on the server side because in the case of # I don't think the string after the hash gets submitted to the server at all. So, people with special characters in the password will have to encode them manually, see e.g. table here:
http://www.w3schools.com/tags/ref_urlencode.asp
Or do a simple javascript page that does the encoding in javascript on the client. Obviously, don't submit your passwords to any online services that offer url-encoding.

[starik69]

Two times today client suddenly lost all balance and began counting forged fees from zero. Restart helped. Wrong was only balance, other things seemed ok.

[GCInc.]

What does that mean (blockchain explorer):

Code:

Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?

[Drexme]

What does that mean (blockchain explorer):

Code:

Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?

They become confirmed once they reach 1440 confirms.

[Come-from-Beyond]

What does that mean (blockchain explorer):

Code:

Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?

They become confirmed once they reach 1440 confirms.

Why?

[nexern]

What does that mean (blockchain explorer):

Code:

Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?

coins, once confirmed on your account can't be reversed. the 1440 confirmations defines also when coins are able to mining fees.
iirc counted from the first transaction on a new account. problem is we haven't any official white paper or specifications about the
inner algos now, so i decided to add this indicator because the api also delivers this. in case the mining algo will change i can remove
this distinction. in your case this makes no difference, genesis accounts are able to mining right away from start.

[Drexme]

Wouldn't it be convenient to have a button that alerts you when a new update is released and when you click it it takes you to download page/forum/website.

More suggestions: http://nextcoin.org/index.php/topic,140.msg995.html#msg995

[GCInc.]

They become confirmed once they reach 1440 confirms.

Currently all tx that go through to the network eventually get that I guess (except if a blockchain reorg is needed) But in the future, what if you set a deadline far away with 1 NXT fee and they never get that many confirms? What's the max deadline?

[salsacz]

Ok time to claim my Nxt (sorry I waited this long).

Hash of secret phrase is:
e999d608692123f54d35e6a4e95b9601801ee8c950719efef2aaac811243df32
My account number is:
16382877351667953798

Cheers!

You shouldn't write here your password I guess..

[klee]

Ok time to claim my Nxt (sorry I waited this long).

Hash of secret phrase is:
e999d608692123f54d35e6a4e95b9601801ee8c950719efef2aaac811243df32
My account number is:
16382877351667953798

Cheers!

You shouldn't write here your password I guess..

It is not the pwd but the hash of the secret phrase to claim the coins..

[wakasaki808]

Ok time to claim my Nxt (sorry I waited this long).

Hash of secret phrase is:
e999d608692123f54d35e6a4e95b9601801ee8c950719efef2aaac811243df32
My account number is:
16382877351667953798

Cheers!

You shouldn't write here your password I guess..

It is not the pwd but the hash of the secret phrase to claim the coins..

yeah I think he posted the hash of the hash that was the step in the original thread to claim the genesis block coins.

[ImmortAlex]

Try
1. Stop soft.
2. Delete peers.nxt.
3. Start soft.
several times.

Edit: Also remove all well known peers from web.xml except 88.198.210.245.

Doesn't help.
88.198.210.245 alone is not working at all.
When I set known list to "fluke.airdns.org; nxt.airdns.org" it generates a lot of traffic, but doesn't download blockchain.

[bybitcoin]

@Come-from-Beyond: the network is officially down by the hacker(s), nxt.airdns.org and fluke.airdns.org are almost capturing all the nodes, Everytime I start, I get stuck at 9861 block and stay there ad infinitum. I have the same collection of txs on both my accounts, but see all kind of weird balances from 0 to 1 and sometimes -5 , no matter which account and which IP (I use a wireless dynamic IP based connection).
Please if you are not able to introduce a resolution during today 12/08/2013 , at least provide temporarily that client server you had for us to send some txs at initial days. I really need to send some txs and I really do not care the fuckkk about how insecure it might be to use your server (I've sold Nxt to some guys, their btc resides in my wallet, and I am fighting with the clients 3.13, 3.14 and now 3.15 for 3 days )
Waiting for your reply, to see if I can send these guys their Nxt or should their BTC back!

[abctc]

.. I get stuck at 9861 block and stay there ad infinitum. ..

- Nxt net is working for me. Curent block is 10418, ID=17503691764654152287

[Sharky444]

@Come-from-Beyond: the network is officially down by the hacker(s), nxt.airdns.org and fluke.airdns.org are almost capturing all the nodes, Everytime I start, I get stuck at 9861 block and stay there ad infinitum. I have the same collection of txs on both my accounts, but see all kind of weird balances from 0 to 1 and sometimes -5 , no matter which account and which IP (I use a wireless dynamic IP based connection).
Please if you are not able to introduce a resolution during today 12/08/2013 , at least provide temporarily that client server you had for us to send some txs at initial days. I really need to send some txs and I really do not care the fuckkk about how insecure it might be to use your server (I've sold Nxt to some guys, their btc resides in my wallet, and I am fighting with the clients 3.13, 3.14 and now 3.15 for 3 days )
Waiting for your reply, to see if I can send these guys their Nxt or should their BTC back!

The network is not down!

You can always see the current block number here:

http://87.230.14.1/nxt/nxt.cgi?action=40

[Financisto]

I decided to clean up and improve the vanity account number generator mentioned before:
https://bitcointalk.org/index.php?topic=303898.msg3691750#msg3691750

This is the updated version:

Source code: https://dl.dropboxusercontent.com/s/gtq6vm1f346oqyy/Vanity.java

Compiled jar file: https://dl.dropboxusercontent.com/s/f9xdycfu3w73q09/Vanity.jar

sha256sums:
4d2e1e182637c564f95fea1e8864fa2364769f42e28ed4135b99b5514a7f4f1f  Vanity.jar
3d98075c9e51c99b78f0794fc402dfbfd984f609308b53a234d1efb0f024737f  Vanity.java

To run it:

Code:

java -jar Vanity.jar

In addition to searching for accounts starting with a given prefix, now it can also search for accounts containing sequences of repeating digits. So there are three modes of operation.

Without any parameters, it will start from a random 16-character secret phrase and keep appending characters to it trying to find vanity-looking accounts:

Code:

$ java -jar Vanity.jar
Using a randomly generated secret prefix: )trT-&Ubyp+d]p`k
Generating vanity accounts...
)trT-&Ubyp+d]p`kE$[ gives account number 3333335333097075555
)trT-&Ubyp+d]p`k!)o4 gives account number 8888377001144420555
)trT-&Ubyp+d]p`k!%Bw gives account number 10713333338888888154

With a single parameter, it will use this as the secret prefix instead of a randomly generated one.

Code:

$ java -jar Vanity.jar my_secret_password
WARNING: For a given secret prefix, the passwords this program generates
are always the same. Therefore, using a strong secret prefix is crucial.
Anyone who can guess your secret prefix can use this program to also
discover your password. You have been warned.
Using a user-supplied secret prefix: my_secret_password
Generating vanity accounts...
my_secret_password861 gives account number 9999679005505533333
my_secret_password!(k^ gives account number 2111114455001119991
my_secret_password"!uE gives account number 13220066661444888887

With two parameters, it defaults to the original behavior, i.e. looking for shortest account number using the first parameter as secret prefix and the second as the account prefix.

Code:

$ java -jar Vanity.jar my_secret_password 888
WARNING: For a given secret prefix, the passwords this program generates
are always the same. Therefore, using a strong secret prefix is crucial.
Anyone who can guess your secret prefix can use this program to also
discover your password. You have been warned.
Using a user-supplied secret prefix: my_secret_password
Looking for the shortest account numbers beginning with 888
Generating vanity accounts...
my_secret_password#$ gives account number 8880281789351433347
my_secret_password^7 gives account number 888082872862915443
my_secret_passwordB`O gives account number 88888386812508853

To repeat the above warning once again:
For a given user-supplied secret prefix, the sequence of generated account numbers is always the same. This is in order to keep the number of characters appended to the secret prefix small. So it is extremely important that you pick up a strong secret prefix. Anybody who can guess your secret prefix can just run this program with it to arrive at your full secret phrase. This obviously doesn't apply when you let the program generate the secret phrase randomly (i.e., running it without any parameters).

Nice app. Maybe it should be listed on the original post (right at "page 1").

A brainwallet for XNT would also be interesting...

(Nxt, in my point of view, is a kind of brainwallet by itself)

Maybe some modifications and additions may be done here: https://github.com/brainwallet/brainwallet.github.com ( source code for http://www.brainwallet.org )

WARNING: BTW, Nxt users will fatally face a problem widely discussed here: https://bitcointalk.org/index.php?topic=251037

i.e. weak passwords/passphrases and funds stolen subsequently.

[abctc]

(Nxt, in my point of view, is a kind of brainwallet by itself)

- correct.

[Come-from-Beyond]

@Come-from-Beyond: the network is officially down by the hacker(s), nxt.airdns.org and fluke.airdns.org are almost capturing all the nodes, Everytime I start, I get stuck at 9861 block and stay there ad infinitum. I have the same collection of txs on both my accounts, but see all kind of weird balances from 0 to 1 and sometimes -5 , no matter which account and which IP (I use a wireless dynamic IP based connection).
Please if you are not able to introduce a resolution during today 12/08/2013 , at least provide temporarily that client server you had for us to send some txs at initial days. I really need to send some txs and I really do not care the fuckkk about how insecure it might be to use your server (I've sold Nxt to some guys, their btc resides in my wallet, and I am fighting with the clients 3.13, 3.14 and now 3.15 for 3 days )
Waiting for your reply, to see if I can send these guys their Nxt or should their BTC back!

Down? Hm, my local node is working without any issues. If u r a stakeholder u should buy VPS and follow the instruction for 0.3.15.