š
Original date posted:2016-03-02
š Original message:On Wed, Mar 02, 2016 at 02:56:14PM +0000, Luke Dashjr via bitcoin-dev wrote:
> To alleviate this risk, it seems reasonable to propose a hardfork to the
> difficulty adjustment algorithm so it can adapt quicker to such a significant
> drop in mining rate. BtcDrak tells me he has well-tested code for this in his
> altcoin, which has seen some roller-coaster hashrates, so it may even be
> possible to have such a proposal ready in time to be deployed alongside SegWit
> to take effect in time for the upcoming subsidy halving. If this slips, I
> think it may be reasonable to push for at least code-readiness before July,
> and possibly roll it into any other hardfork proposed before or around that
> time.
>
> I am unaware of any reason this would be controversial, so if anyone has a
> problem with such a change, please speak up sooner rather than later. Other
> ideas or concerns are of course welcome as well.
Changing the difficulty adjustment algorithm significantly changes the
security of the whole system, as it lets attackers create fake chains
with a lot less hashing power.
Given as tx fees rise this problem will hopefully be a one-time issue, a
simple fixed difficulty adjustment probably makes sense. No need to
bring in new algorithms here with controversial new security tradeoffs.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
0000000000000000045a03e0e551c4e674f301e0a8eeb217a31ad13580446626
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 650 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160302/fc9c261c/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 17:49:36
in reply to nevent1qā¦w57f
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 17:49:36Event JSON
{
"id": "1fffb808a261094c67f1a7018aef43bb85d0772cdba22a1fe6ce811220ac280f",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686160176,
"kind": 1,
"tags": [
[
"e",
"c19c64d0621f34bc049688bdbd88cd48f1e91c193354087b0b32d42fce855169",
"",
"root"
],
[
"e",
"432aec63de1a5e7e21cfb7440d652f5798702e731c3e28ecc79ba794451df8bb",
"",
"reply"
],
[
"p",
"7ac0bd39b854f24cbf067103758f3a9d398c23832d6d75824d190ae35c6c23be"
]
],
"content": "š
Original date posted:2016-03-02\nš Original message:On Wed, Mar 02, 2016 at 02:56:14PM +0000, Luke Dashjr via bitcoin-dev wrote:\n\u003e To alleviate this risk, it seems reasonable to propose a hardfork to the \n\u003e difficulty adjustment algorithm so it can adapt quicker to such a significant \n\u003e drop in mining rate. BtcDrak tells me he has well-tested code for this in his \n\u003e altcoin, which has seen some roller-coaster hashrates, so it may even be \n\u003e possible to have such a proposal ready in time to be deployed alongside SegWit \n\u003e to take effect in time for the upcoming subsidy halving. If this slips, I \n\u003e think it may be reasonable to push for at least code-readiness before July, \n\u003e and possibly roll it into any other hardfork proposed before or around that \n\u003e time.\n\u003e \n\u003e I am unaware of any reason this would be controversial, so if anyone has a \n\u003e problem with such a change, please speak up sooner rather than later. Other \n\u003e ideas or concerns are of course welcome as well.\n\nChanging the difficulty adjustment algorithm significantly changes the\nsecurity of the whole system, as it lets attackers create fake chains\nwith a lot less hashing power.\n\nGiven as tx fees rise this problem will hopefully be a one-time issue, a\nsimple fixed difficulty adjustment probably makes sense. No need to\nbring in new algorithms here with controversial new security tradeoffs.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n0000000000000000045a03e0e551c4e674f301e0a8eeb217a31ad13580446626\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160302/fc9c261c/attachment.sig\u003e",
"sig": "723c22128d9891b2815542546a8a24a331bb2408f72a243be2fe3cff464d23aaf79e1a1bae05335be7a4f673e7cf2461c6bdf9dd13676417b18fb6b9611ebe98"
}