Topic: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks - page 20. (Read 155565 times)
March 11, 2013, 10:41:48 PM
my pool is 0.7 version
March 11, 2013, 10:41:21 PM
Any info on when its expected to be sorted out?
How long will it take for 0.8 clients to be in the correct chain so people can resume trading?
How long will it take for 0.8 clients to be in the correct chain so people can resume trading?
March 11, 2013, 10:40:52 PM
Watching the devs IRC you fockers are top notch!!! MAD RESPECT!!!
http://i28.photobucket.com/albums/c239/judkinsrich/ali-g-respect-1.jpg
http://i28.photobucket.com/albums/c239/judkinsrich/ali-g-respect-1.jpg
March 11, 2013, 10:40:30 PM
It is my understanding that it's still possible for the problem to occur, if someone keep mining on 0.8, right? As long at 0.8 is in the field...
The defaults for 0.8 mining are just fine.
However, if you increase the default block size limit, you can reintroduce the problem, yes.
Don't worry though. Now that people are aware of the issue, it is easy to handle.
The fork will "heal", and all coins are safe.
thx for the update.
March 11, 2013, 10:39:01 PM
March 11, 2013, 10:32:33 PM
March 11, 2013, 10:37:41 PM
Is this where the "EXCEPTION:11DbException Db::put: Not enough space" message comes from?
Do I need to do anything on my non-mining client to fix things, or will it auto-fix itself soon?
it will fix itself. Do I need to do anything on my non-mining client to fix things, or will it auto-fix itself soon?
March 11, 2013, 10:36:24 PM
So if I may say something... I learned about this glitch fairly early on and immediately hopped into the bitcoin-dev IRC room. The impression I got was one of many brilliant, professional, dedicated bitcoin developers working together to resolve the issue. I was immensely impressed with them.
Even people like Luke-Jr and myself, who seem to be mortal enemies, worked politely together and did what was needed to contain the situation and fix things. Most of the people in the room stayed respectfully quiet and let the important work occur.
To all the amazingly intelligent devs who make this crazy shit actually work, my hat is off to you (even you, Luke-Jr!). Eternally impressed with your work, coordination, and skill. And this all being done for the simple passion of Bitcoin. Quite inspiring, really.
paid shill? Even people like Luke-Jr and myself, who seem to be mortal enemies, worked politely together and did what was needed to contain the situation and fix things. Most of the people in the room stayed respectfully quiet and let the important work occur.
To all the amazingly intelligent devs who make this crazy shit actually work, my hat is off to you (even you, Luke-Jr!). Eternally impressed with your work, coordination, and skill. And this all being done for the simple passion of Bitcoin. Quite inspiring, really.
March 11, 2013, 10:35:20 PM
is the price going to plummet
It went down. Lucky people with cash on the sidelines bought cheap coins, price went back up.
March 11, 2013, 10:35:07 PM
Is this where the "EXCEPTION:11DbException Db::put: Not enough space" message comes from?
Do I need to do anything on my non-mining client to fix things, or will it auto-fix itself soon?
Do I need to do anything on my non-mining client to fix things, or will it auto-fix itself soon?
March 11, 2013, 10:35:00 PM
He nailed it by my quick read.
Not really. No amount of testing of 0.8 would have found a bug in 0.7 that nobody knew about and wasn't looking for. March 11, 2013, 10:28:47 PM
So if I may say something... I learned about this glitch fairly early on and immediately hopped into the bitcoin-dev IRC room. The impression I got was one of many brilliant, professional, dedicated bitcoin developers working together to resolve the issue. I was immensely impressed with them.
Even people like Luke-Jr and myself, who seem to be mortal enemies, worked politely together and did what was needed to contain the situation and fix things. Most of the people in the room stayed respectfully quiet and let the important work occur.
To all the amazingly intelligent devs who make this crazy shit actually work, my hat is off to you (even you, Luke-Jr!). Eternally impressed with your work, coordination, and skill. And this all being done for the simple passion of Bitcoin. Quite inspiring, really.
Even people like Luke-Jr and myself, who seem to be mortal enemies, worked politely together and did what was needed to contain the situation and fix things. Most of the people in the room stayed respectfully quiet and let the important work occur.
To all the amazingly intelligent devs who make this crazy shit actually work, my hat is off to you (even you, Luke-Jr!). Eternally impressed with your work, coordination, and skill. And this all being done for the simple passion of Bitcoin. Quite inspiring, really.
quite gay I must say... LMFAO!!!
nahh I'm kidding, above all, I'm impressed with how quickly the price recovered. That shows the community is actually mature enough to analyze the situation and not create panic, except a few morons.
That was impressive and the level of communication in the forum was also impressive!
Still gay tho...
March 11, 2013, 10:34:45 PM
The large block is unknown as well as the miner right?
March 11, 2013, 10:32:52 PM
So if I may say something... I learned about this glitch fairly early on and immediately hopped into the bitcoin-dev IRC room. The impression I got was one of many brilliant, professional, dedicated bitcoin developers working together to resolve the issue. I was immensely impressed with them.
Even people like Luke-Jr and myself, who seem to be mortal enemies, worked politely together and did what was needed to contain the situation and fix things. Most of the people in the room stayed respectfully quiet and let the important work occur.
To all the amazingly intelligent devs who make this crazy shit actually work, my hat is off to you (even you, Luke-Jr!). Eternally impressed with your work, coordination, and skill. And this all being done for the simple passion of Bitcoin. Quite inspiring, really.
Even people like Luke-Jr and myself, who seem to be mortal enemies, worked politely together and did what was needed to contain the situation and fix things. Most of the people in the room stayed respectfully quiet and let the important work occur.
To all the amazingly intelligent devs who make this crazy shit actually work, my hat is off to you (even you, Luke-Jr!). Eternally impressed with your work, coordination, and skill. And this all being done for the simple passion of Bitcoin. Quite inspiring, really.
There is the old bitcoin community I been hearing about. Lets hope it stays like this.
Good job guys... Thumbs up!!!
March 11, 2013, 10:32:44 PM
It is my understanding that it's still possible for the problem to occur, if someone keep mining on 0.8, right? As long at 0.8 is in the field...
The defaults for 0.8 mining are just fine.
However, if you increase the default block size limit, you can reintroduce the problem, yes.
Don't worry though. Now that people are aware of the issue, it is easy to handle.
The fork will "heal", and all coins are safe.
March 11, 2013, 10:31:56 PM
Atlas warned about database change some time ago. Original discussion here https://bitcointalk.org/index.php?topic=119566.0;all
Pffft! Credit where credit is due...He nailed it by my quick read.
March 11, 2013, 10:31:47 PM
is the price going to plummet
March 11, 2013, 10:31:29 PM
Just writing here to make part of history. "I WAS THERE" when Bitcoin shows the 2nd high level bug! 
March 11, 2013, 10:29:57 PM
Back up to $45+ ALREADY?? Could this widespread bug, and it's fairly fast community-assisted response, maybe actually bolster confidence in bitcoins?
Yep. Price will go up. Time to buy
.Joe
March 11, 2013, 10:27:35 PM
It is my understanding that it's still possible for the problem to occur, if someone keep mining on 0.8, right? As long at 0.8 is in the field...
Jump to: