📅 Original date posted:2015-08-14
📝 Original message:On 14 August 2015 at 11:59, Jakob Rönnbäck <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> What if one were to adjust the difficulty (for individual blocks)
> depending on the relative size to the average block size of the previous
> difficulty period? (I apologize if i’m not using the correct terms, I’m not
> a real programmer, and I’ve only recently started to subscribe to the
> mailing list)
>
That would mean that as usage grew, blocksize could increase, but
confirmation times would also increase (though presumably less than
linearly). That seems like a loss?
If you also let the increase in confirmation time (due to miners finding
harder blocks rather than a reduction in hashpower) then get reflected back
as decreased difficulty, it'd probably be simpler to just dynamically
adjust the max blocksize wouldn't it?
Cheers,
aj
--
Anthony Towns <aj at erisian.com.au>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150814/292ce830/attachment.html>;
Anthony Towns [ARCHIVE] /
npub17r…x9l2h
2023-06-07 17:35:04
in reply to nevent1q…nf9z
Author Public Key
npub17rld56k4365lfphyd8u8kwuejey5xcazdxptserx03wc4jc9g24stx9l2hPublished at
2023-06-07 17:35:04Event JSON
{
"id": "b840eb17d5061c5bbdd1a707977c3cd5fd9b38ebdfe4be658dee7c2750bbc038",
"pubkey": "f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab",
"created_at": 1686159304,
"kind": 1,
"tags": [
[
"e",
"a8017727a59f71aff278a9d44fbd695d630cc6578468e5de58b21febfee4579c",
"",
"root"
],
[
"e",
"0afcb1572f69fb8a35aefd45a18bc840941cea4a94092f015e23efa35cb450f0",
"",
"reply"
],
[
"p",
"86adfa6ab3effe134323642507f0277694258be263f5ed52c2dc8f4dae18db5e"
]
],
"content": "📅 Original date posted:2015-08-14\n📝 Original message:On 14 August 2015 at 11:59, Jakob Rönnbäck \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e What if one were to adjust the difficulty (for individual blocks)\n\u003e depending on the relative size to the average block size of the previous\n\u003e difficulty period? (I apologize if i’m not using the correct terms, I’m not\n\u003e a real programmer, and I’ve only recently started to subscribe to the\n\u003e mailing list)\n\u003e\n\nThat would mean that as usage grew, blocksize could increase, but\nconfirmation times would also increase (though presumably less than\nlinearly). That seems like a loss?\n\nIf you also let the increase in confirmation time (due to miners finding\nharder blocks rather than a reduction in hashpower) then get reflected back\nas decreased difficulty, it'd probably be simpler to just dynamically\nadjust the max blocksize wouldn't it?\n\nCheers,\naj\n\n-- \nAnthony Towns \u003caj at erisian.com.au\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150814/292ce830/attachment.html\u003e",
"sig": "aa454891e067136b2fa63981f64513089995b2c94ebeb6784fb37d4a44366fc630037993939acff366c1d85a56fb49e8709c99147a5ff1173b06af0b1411893b"
}