Luckily there is no automatic NXT<->BTC exchange yet, and shouldn't be for a while, less damage from such bugs.
Btw, someone told this to DGEX owner?
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2190. (Read 2761638 times)
Btw, someone told this to DGEX owner?
How to find out if it is synced, please?
Is your block synced?
if not , just wait
Could you explain what does that mean, please?
I had 301 NXT in my wallet.
Now I see there only 1 NXT.
In block explorer, I see there should be 302 NXT.
What could cause that my wallet is not updated correctly, please?
Could you help me?
Thank you very much in advance.
I had 301 NXT in my wallet.
Now I see there only 1 NXT.
In block explorer, I see there should be 302 NXT.
What could cause that my wallet is not updated correctly, please?
Could you help me?
Thank you very much in advance.
Is your block synced?
if not , just wait
Could you explain what does that mean, please?
I had 301 NXT in my wallet.
Now I see there only 1 NXT.
In block explorer, I see there should be 302 NXT.
What could cause that my wallet is not updated correctly, please?
Could you help me?
Thank you very much in advance.
I had 301 NXT in my wallet.
Now I see there only 1 NXT.
In block explorer, I see there should be 302 NXT.
What could cause that my wallet is not updated correctly, please?
Could you help me?
Thank you very much in advance.
Is your block synced?
if not , just wait
Could you explain what does that mean, please?
I had 301 NXT in my wallet.
Now I see there only 1 NXT.
In block explorer, I see there should be 302 NXT.
What could cause that my wallet is not updated correctly, please?
Could you help me?
Thank you very much in advance.
I had 301 NXT in my wallet.
Now I see there only 1 NXT.
In block explorer, I see there should be 302 NXT.
What could cause that my wallet is not updated correctly, please?
Could you help me?
Thank you very much in advance.
Luckily there is no automatic NXT<->BTC exchange yet, and shouldn't be for a while, less damage from such bugs.
This bug looks very similar to the bug that happened in Bitcoin when someone transferred very big amount that led to overflow. History repeats itself indeed...
hopefully CfB comes back soon...
I'm back. I got some messages about a bug, gonna check it.
thinks.
good luck
hopefully CfB comes back soon...
I'm back. I got some messages about a bug, gonna check it.
24435 482115092852324318 12/25/2013 8:49:03 AM
5 20'000'000 + 20'004 682 B
1 16407975697067619592 6664 %
Also seeing some negative numbers. Maybe we found out the cause of the problem?!
James
5 20'000'000 + 20'004 682 B
1 16407975697067619592 6664 %
Also seeing some negative numbers. Maybe we found out the cause of the problem?!
James
neg and stuc, what to do
?
24435 482115092852324318 12/25/2013 8:49:03 AM
5 20'000'000 + 20'004 682 B
1 16407975697067619592 6664 %
Also seeing some negative numbers. Maybe we found out the cause of the problem?!
James
5 20'000'000 + 20'004 682 B
1 16407975697067619592 6664 %
Also seeing some negative numbers. Maybe we found out the cause of the problem?!
James
So i dont know if anyone has mentioned this but the person who found and used this exploit has really done us a favor. We should be thanking him. Its really great that this was detected and brought to our attention during alpha and not beta.
This! https://nextcoin.org/index.php/topic,1228.0.html
I guess its possible this exploit would have been there without the Ddos. Maybe Ddos was a diversion to give him time to cashout the illicit NXT?
James
James
Ddos attacked made 1 second last anywhere from 1 second to many minutes. This would cause all sorts of unexpected race conditions in the software. Just imagining the issues of different nodes trying to reconcile what is what when the heartbeat was different for every node hurts my brain, I am amazed it was able to pick up the pieces and continue to run.
Not sure if the integer overflow was an accident or a malicious hack, but there were a lot of giant fee generating transactions by that account. Probably saw the millions of NXT he was getting and got greedy and went past 2^31. Good thing signed ints were used! Otherwise he could have gotten away with it.
Who could have predicted such an attack on innocent little NXT, still only one month old?
James
Not sure if the integer overflow was an accident or a malicious hack, but there were a lot of giant fee generating transactions by that account. Probably saw the millions of NXT he was getting and got greedy and went past 2^31. Good thing signed ints were used! Otherwise he could have gotten away with it.
Who could have predicted such an attack on innocent little NXT, still only one month old?
James
Decentralized systems are extremely robust in this respect. All you have to do is query all of your peers once every minute or so, ask them how long their block chain is, if it is longer than yours than ask them to send you a copy. If the chain is legit than you adopt it and ping all of your other peers telling them about your new chain, if it is not legit than you ip block the person who sent it to you for like 24 hours.
So i dont know if anyone has mentioned this but the person who found and used this exploit has really done us a favor. We should be thanking him. Its really great that this was detected and brought to our attention during alpha and not beta.
Ddos attacked made 1 second last anywhere from 1 second to many minutes. This would cause all sorts of unexpected race conditions in the software. Just imagining the issues of different nodes trying to reconcile what is what when the heartbeat was different for every node hurts my brain, I am amazed it was able to pick up the pieces and continue to run.
Not sure if the integer overflow was an accident or a malicious hack, but there were a lot of giant fee generating transactions by that account. Probably saw the millions of NXT he was getting and got greedy and went past 2^31. Good thing signed ints were used! Otherwise he could have gotten away with it.
Who could have predicted such an attack on innocent little NXT, still only one month old?
James
Not sure if the integer overflow was an accident or a malicious hack, but there were a lot of giant fee generating transactions by that account. Probably saw the millions of NXT he was getting and got greedy and went past 2^31. Good thing signed ints were used! Otherwise he could have gotten away with it.
Who could have predicted such an attack on innocent little NXT, still only one month old?
James
We can now be sure that Nxt has not been developed by Satoshi Nakamoto...
There were errors in original BTC software. 
i dont know about all the negative balances or negative fees or 2billion NXT fees, but all 6 of my vpss are solid on 24400
We can now be sure that Nxt has not been developed by Satoshi Nakamoto...
It's not so sure, hahah
Even Satoshi may have mistake, not to say some intentional error. On the other hand, I'm not sure whether the ongoing mistake was caused by the core of Nxt or by the client. So the simple fix will have a check of both the sending value and tx fee in the client.
msin,
Don't worry, that didn't actually happen, if it was after block 24179.
James
Don't worry, that didn't actually happen, if it was after block 24179.
James
Yes, I'm assuming it was after block 24179.
We can now be sure that Nxt has not been developed by Satoshi Nakamoto...
Jump to: