Code:
24167 17156841960446798306 2013年12月25日 上午7:06:06
0 0 + 0 0 B
1 18199202185775282486 159 %
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2187. (Read 2761640 times)
just stuck on 24167,right?
one more:
Code:
scum6.bounceme.net scum6.bounceme.net 790'373 397'990 B 4'132 B NRS (0.4.5)
Just got next block
24168 6483973064837388393 12/25/2013 10:46:48 AM
20 1'418'699 + 193 2'560 B
1 4525221562411617061 319 %
Large fee, is that legit?
I got it four times (!) as orphan. Still on 24167. 24168 6483973064837388393 12/25/2013 10:46:48 AM
20 1'418'699 + 193 2'560 B
1 4525221562411617061 319 %
Large fee, is that legit?
@cfb: can you put this version on dropbox 2 please? i can't wget from mega
https://dl.dropboxusercontent.com/u/67242472/nxt.zip
Version 0.4.6 - https://mega.co.nz/#!dIZhiB7K!CLmKETPB3gO6IqH8anfBKgmNTWwh6-FC5EwWqz-r9cQ
Use blockchain files inside the archive. And forge blocks as usually.
Use blockchain files inside the archive. And forge blocks as usually.
shasum?
Why using mega now, instead of dropbox?
I only see one 0.4.5
scum.bounceme.netDonno if you can see my node...
this one:
Code:
37.60.178.103 37.60.178.103 0 355'301 B 481 B NRS (0.4.5)
I understand that. That is why I said to reprocess. Rewind the tape and reprocess all the blocks with a version that doesn't have the bug. Maybe all transactions are preserved!
Just got next block
24168 6483973064837388393 12/25/2013 10:46:48 AM
20 1'418'699 + 193 2'560 B
1 4525221562411617061 319 %
Large fee, is that legit?
James
Just got next block
24168 6483973064837388393 12/25/2013 10:46:48 AM
20 1'418'699 + 193 2'560 B
1 4525221562411617061 319 %
Large fee, is that legit?
James
Is it possible that a fix like changing 32bit signed int to long and then reprocessing all the blocks from before the overflow will properly preserve all the transactions made?
James
No. Every block is depend on previous one. If you change one block you need to recalculate every next blocks. James
Is it possible that a fix like changing 32bit signed int to long and then reprocessing all the blocks from before the overflow will properly preserve all the transactions made?
James
James
so, we have to wait until most peers upgrade to 0.4.6?
I only see one 0.4.5
scum.bounceme.netDonno if you can see my node...
Thank you CfB for your great work.
Nothing can stop Nxt's success.
Nothing can stop Nxt's success.
I only see one 0.4.5
Unfortunate this happened, but glad to see a fix was pushed out quickly.
I think that guy did us a big favor, much bigger than a guy with zombie nodes. Someone should start collecting a reward for him and (after I make sure he is really the owner of that account) pay him.
There is a need for a special donation fund for future bugs too.
Except maybe pay to those only who don't interrupt everything, but warn before that and post some proof of concept.
also stuck on 24167, 7 peers and getting new one every 10 seconds or so.
I lost all my aliases, but I still see the transactions that charged me for them?
James
I lost all my aliases, but I still see the transactions that charged me for them?
James
Just wait, part of the aliases will come back, money for the rest will come back too.
@cfb: can you put this version on dropbox 2 please? i can't wget from mega
I second this. Mega does not want to DL for me.
I see
24167 17156841960446798306 25.12.2013 2:06:06
0 0 + 0 0 B
1 18199202185775282486 159 %
Same here. And all peers are 0.4.4. 24167 17156841960446798306 25.12.2013 2:06:06
0 0 + 0 0 B
1 18199202185775282486 159 %
@cfb: can you put this version on dropbox 2 please? i can't wget from mega
also stuck on 24167, 7 peers and getting new one every 10 seconds or so.
I lost all my aliases, but I still see the transactions that charged me for them?
James
I lost all my aliases, but I still see the transactions that charged me for them?
James
Unfortunate this happened, but glad to see a fix was pushed out quickly.
I think that guy did us a big favor, much bigger than a guy with zombie nodes. Someone should start collecting a reward for him and (after I make sure he is really the owner of that account) pay him.
Jump to: