Pages:
Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 50. (Read 2761629 times)

hero member
Activity: 966
Merit: 513
As for "our new friend here", like somebody said, guys have some self respect and ignore his posts. He doesn't want any help, it's quite obvious.

I asked for help understanding what happened. I now understand what happened due to the help I received.

Someone even offered to make me whole and I declined.

I don't understand the anger I'm receiving at pointing out a glaringly obvious problem with the software.

Many even acknowledge the problem and offer a solution(a different client), but that won't protect the people that use the OP as a guide and download the same client I did. This thing is months old and yet these basic issues remain un-addressed.

Don't even get me started on the min transaction fees that will be generated if this thing goes mainstream. What % of that would go to the few people that staked this thing from the git?
sr. member
Activity: 308
Merit: 250

I think it's going to have a delay with NQT introduction.  Javascript doesn't have "long", and "int" can't handle that large numbers.



Javascript has a pretty decent BigNum library.


I use jsbn.js / jsbn2.js

http://www-cs-students.stanford.edu/~tjw/jsbn/
full member
Activity: 238
Merit: 100
As for "our new friend here", like somebody said, guys have some self respect and ignore his posts. He doesn't want any help, it's quite obvious.
full member
Activity: 238
Merit: 100
I think it's going to have a delay with NQT introduction.  Javascript doesn't have "long", and "int" can't handle that large numbers.

If ECDSA algos can be coded in Javascript then I assume some sort of "big integer" stuff must have already been created.

(this shouldn't be a big problem - just will require the use of a .js *library*)


Of course. The issue was that the numbers were returned from the API as integers, not strings, which meant large numbers would result in incorrect output. Now the new 0.9.1 returns as strings, which can be passed to a js library if needed.

I see, well whenever you guys finish it, it will be great. Like I said it is a thing of beauty and we don't need no more from a client.
legendary
Activity: 1260
Merit: 1168

I think it's going to have a delay with NQT introduction.  Javascript doesn't have "long", and "int" can't handle that large numbers.



Javascript has a pretty decent BigNum library.
sr. member
Activity: 308
Merit: 250
I think it's going to have a delay with NQT introduction.  Javascript doesn't have "long", and "int" can't handle that large numbers.

If ECDSA algos can be coded in Javascript then I assume some sort of "big integer" stuff must have already been created.

(this shouldn't be a big problem - just will require the use of a .js *library*)


Of course. The issue was that the numbers were returned from the API as integers, not strings, which meant large numbers would result in incorrect output. Now the new 0.9.1 returns as strings, which can be passed to a js library if needed.
hero member
Activity: 574
Merit: 500
@solarion - When you made an account first with your 6 words phrase, you should have written or copied the account number.

When you then sent from Cryptsy you should have checked that you're sending to THIS account, but you didn't.

Instead you were a bit reckless.

Someone should mention to him 6 words probably isn't long enough (and his reaction to one of my first questions implies he used a sentence/phrase against all advice he read)
hero member
Activity: 966
Merit: 513
@solarion - When you made an account first with your 6 words phrase, you should have written or copied the account number.

When you then sent from Cryptsy you should have checked that you're sending to THIS account, but you didn't.

Instead you were a bit reckless.

Agreed. I was reckless. As I said I was tired and probably not thinking clearly. It's not much "money" and I wasn't that concerned. If I was concerned I'd have sent 1 next well...1 next and a 100% transaction fee to be absorbed by the founders of this thing.

Doesn't change the fact that the client is crap.

...also doesn't change the fact that I've set up dozens of "old skool" wallets and never had a problem, but this "next" wallet is causing all kinds of problems.

Minimum transaction fee = 6340 satoshis atm. How is THAT supposed to fly?!?
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
I think it's going to have a delay with NQT introduction.  Javascript doesn't have "long", and "int" can't handle that large numbers.

If ECDSA algos can be coded in Javascript then I assume some sort of "big integer" stuff must have already been created.

(this shouldn't be a big problem - just will require the use of a .js *library*)
legendary
Activity: 1120
Merit: 1000
@solarion - When you made an account first with your 6 words phrase, you should have written or copied the account number.

When you then sent from Cryptsy you should have checked that you're sending to THIS account, but you didn't.

Instead you were a bit reckless.
hero member
Activity: 644
Merit: 500
I will give @solarion the *benefit of the doubt* rather than just "shooting him down in flames".

Yes - it is unfortunate that the "default" client doesn't stop you from entering an "empty" password (or a non-secure one for that matter).

As has been mentioned this will be addressed when the "new" client becomes part of the Nxt standard software.

Understand that early Bitcoin versions had even worse problems (gmaxwell has mentioned some of those) so always when using "alpha" software *be very careful*.


Well this has already been solved, I just tried not to enter password in Wesley web client and it didn't let me.

I agree that NRS is to long around. A month ago we were talking that we will have Wesleys web client with incorporated NRS by Jean Luc in a matter of days. Month has passed and still nothing.

I just downloaded today a windows client from Weslehy and it is a thing of beauty. I see it is beta, but this needs to be pushed ASAP as our only official client. I don't know how far are we from the moment that is completely safe, but to me it seems safe. This is a question for Wesley.


I think it's going to have a delay with NQT introduction.  Javascript doesn't have "long", and "int" can't handle that large numbers.

https://bitbucket.org/JeanLucPicard/nxt/issue/83/nqt-and-javascript-precision
hero member
Activity: 966
Merit: 513
Fuck off.

I wanted to try this coin out. Don't give a happy gd if you believe me or not.
full member
Activity: 238
Merit: 100
1593 or 1592 less the nonsensical minimum transaction fee.

PM me your Nxt account # associated with YOUR password and I'll send you 1593 later, I think you should at least stick around so you can try Asset Exchange and some other really neat features being released soon.

Msin you are a great guy but you shouldn't do this. It is clear that he showed up over here just to run his mouth and bash all that we do. He is a troll and period. Even after you offered to reimburse his coins he acts like a dick. He is a FUDster and troll. Point blank. From his third post he started running his mouth and it is obvious this was his only intention.
hero member
Activity: 966
Merit: 513
So why don't you guys get the windows client stricken from the op? It's plainly garbage, yet it's still there.
hero member
Activity: 644
Merit: 500
I get that. Think I'd rather stick to coins with wallet.dat files and move coins to online wallets as necessary.

then you didnt choose the right client!
https://nextcoin.org/index.php/topic,4525.0.html
offspring client supports wallet.dat for your passphrase.

I USED THE DIRECTIONS FROM PAGE ONE OF THIS THREAD.

"Make sure you use a very random, complex password of at least 80 characters.  You can use 0-1, a-z, A-Z, special and national characters."

dafuq am I going to remember that? I already have 10k passwords floating around in my head.

Make wallet.dat and save it there, as that is what bitcoin do anyway Smiley

Or use password managers http://www.pcmag.com/article2/0,2817,2407168,00.asp


hero member
Activity: 574
Merit: 500
I get that. Think I'd rather stick to coins with wallet.dat files and move coins to online wallets as necessary.

then you didnt choose the right client!
https://nextcoin.org/index.php/topic,4525.0.html
offspring client supports wallet.dat for your passphrase.

I USED THE DIRECTIONS FROM PAGE ONE OF THIS THREAD.

"Make sure you use a very random, complex password of at least 80 characters.  You can use 0-1, a-z, A-Z, special and national characters."

dafuq am I going to remember that? I already have 10k passwords floating around in my head.

So you are saying you didn't follow the directions on page one of this thread?

You are all over the place.

Ignored. Got no patience for mindless clones that get married to a cryptocurrency.

This thing has to be usable by nearly anyone to be taken seriously. It's not even close to that.

The logic bombs always stump the least prepared fudsters.
full member
Activity: 238
Merit: 100
I will give @solarion the *benefit of the doubt* rather than just "shooting him down in flames".

Yes - it is unfortunate that the "default" client doesn't stop you from entering an "empty" password (or a non-secure one for that matter).

As has been mentioned this will be addressed when the "new" client becomes part of the Nxt standard software.

Understand that early Bitcoin versions had even worse problems (gmaxwell has mentioned some of those) so always when using "alpha" software *be very careful*.


Well this has already been solved, I just tried not to enter password in Wesley web client and it didn't let me.

I agree that NRS is to long around. A month ago we were talking that we will have Wesleys web client with incorporated NRS by Jean Luc in a matter of days. Month has passed and still nothing.

I just downloaded today a windows client from Weslehy and it is a thing of beauty. I see it is beta, but this needs to be pushed ASAP as our only official client. I don't know how far are we from the moment that is completely safe, but to me it seems safe. This is a question for Wesley.
hero member
Activity: 966
Merit: 513
I get that. Think I'd rather stick to coins with wallet.dat files and move coins to online wallets as necessary.

then you didnt choose the right client!
https://nextcoin.org/index.php/topic,4525.0.html
offspring client supports wallet.dat for your passphrase.

I USED THE DIRECTIONS FROM PAGE ONE OF THIS THREAD.

"Make sure you use a very random, complex password of at least 80 characters.  You can use 0-1, a-z, A-Z, special and national characters."

dafuq am I going to remember that? I already have 10k passwords floating around in my head.

So you are saying you didn't follow the directions on page one of this thread?

You are all over the place.

Ignored. Got no patience for mindless clones that get married to a cryptocurrency.

This thing has to be usable by nearly anyone to be taken seriously. It's not even close to that.
legendary
Activity: 1120
Merit: 1000
The fact that there is no warning about the null account is a mistake.

But the biggest mistake here that you didn't check where you're sending the nxt! Your own fault.

Did check. The account # cryptsy sent the coins to is the same account # on my screen.

This months old software is still garbage.

Just go to bed, wake-up and rethink.
hero member
Activity: 966
Merit: 513
Do you really think everyone sees nxt on coinmarket site reads all the posts and wikis and everything? He downloaded the NRS first time, hit entered, and got into "null" account. This is how bitcoin clones work. I am sure he won't be the last one to make to make the same mistake. Look how many transactions the "null" account has

http://blocks.nxtcrypto.org/nxt/nxt.cgi?action=3000&acc=3791936988034107349


Well...  thankfully this is NOT a Bitcoin clone!    Wink

if it were this would not have happened and we wouldn't be having this conversation.
Pages:
Jump to: