📅 Original date posted:2018-12-03
📝 Original message:The last difficulty change took about 20% longer than expected. How large
does the time between difficulty changes have to get for us to make
changes? In other words, if, at some point, block confirmation times are
averaging, say, hours or days, will we hardfork to speed things up?
One option is NO. When enough economic interests align to amass the
computing power to get important bitcoin transactions into a block, then
they will work out a way to get that block confirmed. This allows other
cryptocurrencies and technologies like LN to fill in.
There may be a group that will fork the code in order to adjust the
difficulty more rapidly, and bitcoin holders will put a value on
bitcoin-FDA ("Faster-Difficuly-Adjustment"), which is fine with me. We can
learn how to fork peacefully from what we learned when BCH was born, and
what we learned when it split.
I think some insight into how core developers will handle increasing
demands to use faster difficulty adjustments (if they respond at all) will
be helpful, and this is why I'm asking.
Dave Scotese
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20181203/9ca5ce6b/attachment-0001.html>;
Dave Scotese [ARCHIVE] /
npub15w…maru8
2023-06-07 18:15:31
in reply to nevent1q…7uwp
Author Public Key
npub15wz8j5cse6sexlw6f5q7arc5efe5hxn6kcxxyy222et8qms4u3lsemaru8Published at
2023-06-07 18:15:31Event JSON
{
"id": "b85b18feb54c7db3d277ad004e9584f2e9e40de75a7115abc54e0122bc0c0c87",
"pubkey": "a384795310cea1937dda4d01ee8f14ca734b9a7ab60c62114a5656706e15e47f",
"created_at": 1686161731,
"kind": 1,
"tags": [
[
"e",
"cdec6e5dad588176a42dd9b6bd309762b9b19874f824a5553dd820922391b061",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2018-12-03\n📝 Original message:The last difficulty change took about 20% longer than expected. How large\ndoes the time between difficulty changes have to get for us to make\nchanges? In other words, if, at some point, block confirmation times are\naveraging, say, hours or days, will we hardfork to speed things up?\n\nOne option is NO. When enough economic interests align to amass the\ncomputing power to get important bitcoin transactions into a block, then\nthey will work out a way to get that block confirmed. This allows other\ncryptocurrencies and technologies like LN to fill in.\n\nThere may be a group that will fork the code in order to adjust the\ndifficulty more rapidly, and bitcoin holders will put a value on\nbitcoin-FDA (\"Faster-Difficuly-Adjustment\"), which is fine with me. We can\nlearn how to fork peacefully from what we learned when BCH was born, and\nwhat we learned when it split.\n\nI think some insight into how core developers will handle increasing\ndemands to use faster difficulty adjustments (if they respond at all) will\nbe helpful, and this is why I'm asking.\n\nDave Scotese\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20181203/9ca5ce6b/attachment-0001.html\u003e",
"sig": "dccadaa66740cc3dd7a8f51883fb96b6d49d899ad970356e031326c6967e7f57e7f3dfd1fd480eb41483ebf0a767af2e3cb32faf4bc3fa41d0387a792472546e"
}