This is a great proposal. This gets over the problem that even if consensus (say 75%) is reached how do we ensure transactions are not lost before everyone (100%) has upgraded or risk being on a losing chain forever.
Under this proposal we no longer need as much as 75%, 55% would probably do and the rest can safely upgrade with all transactions ending up on the winning chain because, by the time we reach 55%, we will know which chain will win.
|
|
|
I've always been certain Szabo is Satoshi but even more convinced after hearing the pod-cast. He seems to go out of his way to refer to Satoshi in the third person. Also the fact that no-one really knows much about Szabo shows that here is an individual who is very careful about protecting his identity. I think also that Andreas knows that he is Satoshi - he's almost referential in his questions to Szabo.
|
|
|
I like BIP1xx but don't think we should double or half the blocksize in one go. Maybe consider plus or minus 20% in one go so there is not so much of a sudden change.
|
|
|
Why is this a problem, exactly?
It's not a huge problem now but imagine (maybe somewhat in the future) you paid for something in a shop of a significant value (say $100) in bitcoin and the vendor required one confirmation for payment to be accepted. Waiting 10 minutes wouldn't be a problem but 1 hour or more would start to be really inconvenient. You could also find that so many transactions had built up during that hour that your transaction would be delayed by a block or two (even with a miners fee). If bitcoin wants to replace existing payment structures then we want to think of ways we can avoid these delays even if they are occasional. 3 days ago there were 2 long waits within a 2 hour period 364834 11/07/2015 09:14 364835 11/07/2015 10:03 364836 11/07/2015 10:06 364837 11/07/2015 10:09 364838 11/07/2015 10:16 364839 11/07/2015 11:08
|
|
|
Every 3 days (on average) a block will take more than an hour to solve. Although 10 minutes is the average, occasionally it could be much more than this.
An hour is a long time to wait for a single confirmation, especially if Bitcoin becomes widely adopted.
It might not happen very often but this doesn't mean it's acceptable - ( once every 3 years a block will takes more than 2 hours to solve! )
I guess it's hard to propose a solution to this but could the difficulty be reduced (temporarily) if a block has not been solved in say, 20 minutes?
I realize that time is a fuzzy concept in the Bitcoin network so this might fall down if the nodes can't agree on what actually is 20 minutes.
|
|
|
"This is actually good news"
|
|
|
I've emailed Amazon, will be emailed again at 6,000, 7,000 etc
|
|
|
250 left, the final push. The biggest shop on the Internet should really be using the Internet Currency by now. .....or be left behind!
|
|
|
The price started to rise culminating one month later with the price at 1147
(Doesn't mean it will happen this year though....) 03 November 2013 207.6335 04 November 2013 225.196 05 November 2013 239.29 06 November 2013 253.6933 07 November 2013 283.3023 08 November 2013 323.767 09 November 2013 336.1358 10 November 2013 311.9005 11 November 2013 332.6263 12 November 2013 349.3425 13 November 2013 393.2795 14 November 2013 410.723 15 November 2013 409.1675 16 November 2013 428.8238 17 November 2013 476.295 18 November 2013 674.3768 19 November 2013 541.8257 20 November 2013 572.6675 21 November 2013 695.8668 22 November 2013 747.4818 23 November 2013 776.6998 24 November 2013 751.377 25 November 2013 778.6753 26 November 2013 899.2 27 November 2013 948.4088 28 November 2013 1037.755 29 November 2013 1120.3971 30 November 2013 1124.7631 01 December 2013 946.9237 02 December 2013 1038.3485 03 December 2013 1068.6675 04 December 2013 1147.2457
|
|
|
Nearly there less than 300 now
|
|
|
|