I see
24167 17156841960446798306 25.12.2013 2:06:06
0 0 + 0 0 B
1 18199202185775282486 159 %
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2188. (Read 2761640 times)
Unfortunate this happened, but glad to see a fix was pushed out quickly.
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.
heh, ok
U'll see 0.4.5 there, coz the only difference is blockchain files.
Seems like you forget to change version number.
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.
heh, ok
This is the gift for us on christmas day ---just a joke. 
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.
stuck on 24449
Code:
24449 6719982959416303457 2013年12月25日 下午3:13:45
1 1 + 1 128 B
1 9036556180184158034 1428 %
I got message from BCNext. He said to roll chain back and reforge blocks again. Be ready for 0.4.6.
Well, guys. I deployed a fast work-around. BCNext is out of reach now (Xmas, hehe). Dunno what he would do, I just left everything in blockchain as it is (for the history).
But the nxt generated using the bug cannot be spent anymore? What happened to the ones that were already sent across the system?
Cfb should get in touch with him!
But the nxt generated using the bug cannot be spent anymore? What happened to de ones that were already sent across the system?
This is fast work-around. I'm searching for the block where all this happened. I think we'll start from that block again.
I think it started here:
2022567515111486500
In big masses at least.
Well, guys. I deployed a fast work-around. BCNext is out of reach now (Xmas, hehe). Dunno what he would do, I just left everything in blockchain as it is (for the history).
But the nxt generated using the bug cannot be spent anymore? What happened to the ones that were already sent across the system?
But the nxt generated using the bug cannot be spent anymore? What happened to de ones that were already sent across the system?
This is fast work-around. I'm searching for the block where all this happened. I think we'll start from that block again.
Does this mean we don't have to reconstruct everything manually after the corrupted block?
James
James
No, what for?
Xmas bug
Does this mean we don't have to reconstruct everything manually after the corrupted block?
James
James
No, what for?
To kill off the extra coin supply, or how does that work?
Does this mean we don't have to reconstruct everything manually after the corrupted block?
James
James
No, what for?
Well, guys. I deployed a fast work-around. BCNext is out of reach now (Xmas, hehe). Dunno what he would do, I just left everything in blockchain as it is (for the history).
But the nxt generated using the bug cannot be spent anymore? What happened to the ones that were already sent across the system?
0.45 almost caught up, but already past the tainted block
It seems transactions are preserved, but a bunch of aliases I did seem to be missing
Is there a point in resubmitting all the aliases, or will all this get rewound back to the tainted block?
James
It seems transactions are preserved, but a bunch of aliases I did seem to be missing
Is there a point in resubmitting all the aliases, or will all this get rewound back to the tainted block?
James
Jump to: