Gregory Maxwell [ARCHIVE] on Nostr: 📅 Original date posted:2015-09-03 📝 Original message:On Thu, Sep 3, 2015 at ...
📅 Original date posted:2015-09-03
📝 Original message:On Thu, Sep 3, 2015 at 2:40 PM, Jeff Garzik <jgarzik at gmail.com> wrote:
> Expanding on pay-with-diff and volatility (closing comment),
>
> Users and miners will have significant difficulty creating and/or predicting
> a stable block size (and fee environment) with pay-with-diff across the
> months. The ability of businesses to plan is low. Chaos and
> unpredictability are bad in general for markets and systems. Thus the
> binary conclusion of "not get used" or "volatility"
Sorry, I'm still not following. I agree that predictability is important.
I don't follow where unpredictability is coming from here. Most (all?)
of the difficulty based adjustments had small limits on the difficulty
change that wouldn't have substantially changed the interblock times
relative to orphaning.
> It's written as 'a' and/or 'b'. If you don't have idle hashpower, then paying with difficulty requires some amount of collusion ('a')
> Any miner paying with a higher difficulty either needs idle hashpower, or self-increase their own difficulty at the possible opportunity cost of losing an entire block's income to another miner who doesn't care about changing the block size. The potential loss does not economically compensate for size increase gains in most cases, when you consider the variability of blocks (they come in bursts and pauses) and the fee income that would be associated
What the schemes propose is blocksize that increases fast with
difficulty over a narrow window. The result is that your odds of
producing a block are slightly reduced but the block you produce if
you do is more profitable: but only if there is a good supply of
transactions which pay real fees compariable to the ones you're
already taking. The same trade-off exists at the moment with respect
to orphaning risk and miners still produce large blocks, producing a
larger block means a greater chance you're not successful (due to
orphaning) but you have a greater utility. The orphing mediated risk
is fragile and can be traded off for centeralization advantage or by
miners bypassing validation, issues which at least so far we have no
reason to believe exist for size mediated schemes.
As you know, mining is not a race (ignoring edge effects with
orphaning/propagation time). Increasing difficulty does not put you at
an expected return disavantage compared to other miners so long as the
income increases at least proportionally (otherwise pooling with low
diff shares would be an astronomically losing proposition :)!).
Pay-for-size schemes have been successfully used in some altcoins
without the effects you're suggesting.
Published at
2023-06-07 17:39:26Event JSON
{
"id": "2f956ec163c26e4988da23a66b15fe381ecbc5923cd8621f579fe89adef8a595",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686159566,
"kind": 1,
"tags": [
[
"e",
"dbb4e6d7748308ee67a1d1ad1fb204aeb89db8ab4acccbd7812a3205f4f42fd9",
"",
"root"
],
[
"e",
"bbce652e089c1e86f8dd03b8de283fb5dc3b9eefb3c07e05d272201794a77d8a",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2015-09-03\n📝 Original message:On Thu, Sep 3, 2015 at 2:40 PM, Jeff Garzik \u003cjgarzik at gmail.com\u003e wrote:\n\u003e Expanding on pay-with-diff and volatility (closing comment),\n\u003e\n\u003e Users and miners will have significant difficulty creating and/or predicting\n\u003e a stable block size (and fee environment) with pay-with-diff across the\n\u003e months. The ability of businesses to plan is low. Chaos and\n\u003e unpredictability are bad in general for markets and systems. Thus the\n\u003e binary conclusion of \"not get used\" or \"volatility\"\n\nSorry, I'm still not following. I agree that predictability is important.\n\nI don't follow where unpredictability is coming from here. Most (all?)\nof the difficulty based adjustments had small limits on the difficulty\nchange that wouldn't have substantially changed the interblock times\nrelative to orphaning.\n\n\u003e It's written as 'a' and/or 'b'. If you don't have idle hashpower, then paying with difficulty requires some amount of collusion ('a')\n\u003e Any miner paying with a higher difficulty either needs idle hashpower, or self-increase their own difficulty at the possible opportunity cost of losing an entire block's income to another miner who doesn't care about changing the block size. The potential loss does not economically compensate for size increase gains in most cases, when you consider the variability of blocks (they come in bursts and pauses) and the fee income that would be associated\n\nWhat the schemes propose is blocksize that increases fast with\ndifficulty over a narrow window. The result is that your odds of\nproducing a block are slightly reduced but the block you produce if\nyou do is more profitable: but only if there is a good supply of\ntransactions which pay real fees compariable to the ones you're\nalready taking. The same trade-off exists at the moment with respect\nto orphaning risk and miners still produce large blocks, producing a\nlarger block means a greater chance you're not successful (due to\norphaning) but you have a greater utility. The orphing mediated risk\nis fragile and can be traded off for centeralization advantage or by\nminers bypassing validation, issues which at least so far we have no\nreason to believe exist for size mediated schemes.\n\nAs you know, mining is not a race (ignoring edge effects with\norphaning/propagation time). Increasing difficulty does not put you at\nan expected return disavantage compared to other miners so long as the\nincome increases at least proportionally (otherwise pooling with low\ndiff shares would be an astronomically losing proposition :)!).\n\nPay-for-size schemes have been successfully used in some altcoins\nwithout the effects you're suggesting.",
"sig": "0bdb3846d4ad56dd06a51e0da20539c0c8861f437e269c196edd150dec7dc8be47a7b2e1fe3f818a3eabde6a0afb09dddad9acf19d253803e12aafac285c1b77"
}