Kosmatos (OP)
Member
Offline
Activity: 101
Merit: 10
|
|
October 24, 2013, 12:30:49 AM |
|
I know it can happen occasionally (yes, I did my probabilities class) but it's still scary when blocks are confirming every few minutes and then suddenly it grinds to a halt and nothing for the past 40 minutes.
Always wonder if something has gone terribly wrong.
Carry on.
|
|
|
|
malevolent
can into space
Legendary
Offline
Activity: 3472
Merit: 1724
|
|
October 24, 2013, 12:43:49 AM |
|
|
Signature space available for rent.
|
|
|
Kosmatos (OP)
Member
Offline
Activity: 101
Merit: 10
|
|
October 24, 2013, 12:49:06 AM |
|
Yeah, as aantonop tweeted, "A watched blockchain doesn't hash.". Still 51+ minutes was scary. Anyway, all's well.
|
|
|
|
bitcoinator
|
|
October 24, 2013, 01:12:04 AM |
|
I understand that there is variance and block generation is a stochastic process.
Even assuming the hash rate is always rising, there is still a chance that it will require 100 years to generate the block, isn't it?
I wonder what's the probability of having unacceptable block generation time.
|
|
|
|
theonewhowaskazu
|
|
October 24, 2013, 01:40:10 AM |
|
Yea, thats always a pain, especially if you're waiting for a Gox withdraw or something that sometimes does go terribly wrong. You just show up back at your computer and are like 'OH SHIT', especially if you forget to check blockchain.info.
|
|
|
|
Kluge
Donator
Legendary
Offline
Activity: 1218
Merit: 1015
|
|
October 24, 2013, 01:44:43 AM |
|
I understand that there is variance and block generation is a stochastic process.
Even assuming the hash rate is always rising, there is still a chance that it will require 100 years to generate the block, isn't it?
I wonder what's the probability of having unacceptable block generation time.
If someone did the calculations, we might find it more probable than an address collision, and then the trolls would create a thread every other day about the "10 minute block myth."
|
|
|
|
theonewhowaskazu
|
|
October 24, 2013, 02:15:29 AM |
|
Bitcoin can only adjust difficulty on a block's creation, right? Its not like it can go "oh screw its been 7 days since the last block was created, time to divide difficulty by C"?
|
|
|
|
|
theonewhowaskazu
|
|
October 24, 2013, 02:29:31 AM |
|
In random numbers (block generation time) coincidences happen fairly often. Otherwise, the martingale would be an infallible strategy.
|
|
|
|
chondrite
|
|
October 24, 2013, 02:41:25 AM |
|
"scary" lol
|
|
|
|
oakpacific
|
|
October 24, 2013, 02:57:19 AM |
|
There is also a chance that I go out onto the street then a bag with 100 million dollars, an aerolite, and Elvis Presley all drop out of the blue sky onto my head.
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3486
Merit: 4801
|
|
October 24, 2013, 02:59:56 AM |
|
Bitcoin can only adjust difficulty on a block's creation, right? Its not like it can go "oh screw its been 7 days since the last block was created, time to divide difficulty by C"?
Correct. It's actually even more than that. Bitcoin can only adjust the difficulty every 2016 blocks.
|
|
|
|
theonewhowaskazu
|
|
October 24, 2013, 05:04:49 AM |
|
Bitcoin can only adjust difficulty on a block's creation, right? Its not like it can go "oh screw its been 7 days since the last block was created, time to divide difficulty by C"?
Correct. It's actually even more than that. Bitcoin can only adjust the difficulty every 2016 blocks. Darn. Is there any reason it can't tie difficutly increase to a time period instead? That way we could decrease difficulty every X days and say to naysayers "see, even if something really dumb happens we're guaranteed a block in 2 years "
|
|
|
|
Foxpup
Legendary
Offline
Activity: 4532
Merit: 3183
Vile Vixen and Miss Bitcointalk 2021-2023
|
|
October 24, 2013, 09:37:57 AM |
|
Darn. Is there any reason it can't tie difficutly increase to a time period instead?
Because block timestamps can be inaccurate (either maliciously or by accident) and there's absolutely no way to verify when a block was really mined (and thus how long it has been since the last block). For example, say it's been twenty minutes since the last block, and then you receive a block with a timestamp a few seconds after the previous block. Was it really mined a few seconds after the last block, and you were just late in receiving it due to network lag? Is the miner deliberately using bogus timestamps in an attempt to jack up the difficulty for everybody else? Or is the miner's clock just twenty minutes slow? You don't know. Nobody knows. Fortunately, nobody needs to know, since Bitcoin doesn't care how long ago the last block was mined, and everything works as long as the majority of miners are keeping reasonably accurate time.
|
Will pretend to do unspeakable things (while actually eating a taco) for bitcoins: 1K6d1EviQKX3SVKjPYmJGyWBb1avbmCFM4I am not on the scammers' paradise known as Telegram! Do not believe anyone claiming to be me off-forum without a signed message from the above address! Accept no excuses and make no exceptions!
|
|
|
inform
Newbie
Offline
Activity: 42
Merit: 0
|
|
October 24, 2013, 09:58:09 AM |
|
Yeah, as aantonop tweeted, "A watched blockchain doesn't hash.". Still 51+ minutes was scary. Anyway, all's well.
some this come
|
|
|
|
2GOOD
|
|
October 24, 2013, 10:15:02 PM |
|
It happened on bytecoin (exact copy of bitcoin) network, one diff cycle was about 3-4 months. No problem at all, just wait more for 6+ conf.
Keep in mind that bitcoin diff can change by the margin of 4, in bytecoin example it when 4 times lower after that 2016 blocks were mined
|
|
|
|
kokojie
Legendary
Offline
Activity: 1806
Merit: 1003
|
|
October 25, 2013, 02:15:15 AM |
|
oh please, it only happens every single day, real scary stuff!
|
btc: 15sFnThw58hiGHYXyUAasgfauifTEB1ZF6
|
|
|
|