📅 Original date posted:2015-09-27
📝 Original message:I was mansplaining weak blocks to my wife. She asked a simple question:
Why would I, as a miner, publish a weak block if I find one?
I don't know.
Sure, I will get faster propagation for my solved block, should I find one.
On the other hand everybody else mining a similar block will enjoy the same
benefit. Assuming that I'm not a huge miner, it's unlikely that I will
actually solve the block, so I'm probably just giving away fast propagation
times to someone else.
So how does publishing a weak block benefit the producer of it more than
the other miners? Please help me understand this.
/Kalle Rosenbaum
2015-09-27 11:42 GMT+02:00 Tier Nolan via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org>:
>
>
> On Sun, Sep 27, 2015 at 2:39 AM, Gregory Maxwell via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> Unless the weak block transaction list can be a superset of the block
>> transaction list size proportional propagation costs are not totally
>> eliminated.
>>
>
> The POW threshold could be dynamic. The first weak-block that builds on a
> new block could be forwarded with a smaller target.
>
> This reduces the window size until at least one weak block is
> propagated.
>
> The change in threshold could be time based (for the first 30 seconds or
> so). This would cause a surge of traffic when a new block once a new block
> has propagated, so perhaps not so good an idea.
>
>
>> As even if the weak block criteria is MUCH lower than the block
>> criteria (which would become problematic in its own right at some
>> point) the network will sometimes find blocks when there hasn't been
>> any weak block priming at all (e.g. all prior priming has made it into
>> blocks already).
>>
>
> If there is a transaction backlog, then miners could forward merkle
> branches with transactions in the memory pool with a commitment in the
> coinbase.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150927/04c13069/attachment.html>;
Kalle Rosenbaum [ARCHIVE] /
npub1uw…55zf7
2023-06-07 17:41:07
in reply to nevent1q…uthm
Author Public Key
npub1uwweecasakwtk96j3vjmkjenhnhyv4rku382txq0kmexjwuh4w2st55zf7Published at
2023-06-07 17:41:07Event JSON
{
"id": "47c207d60ac8365730a1d22b4897feda0805f7134e392fc71f86ebdc30def37d",
"pubkey": "e39d9ce3b0ed9cbb17528b25bb4b33bcee465476e44ea5980fb6f2693b97ab95",
"created_at": 1686159667,
"kind": 1,
"tags": [
[
"e",
"47e992d8066a798c3fec58fb87e76f9362fea651b87542b83f6a85adc1e96982",
"",
"root"
],
[
"e",
"6b0c1daaf601e25ca754289f1160a16e3d96439b05600eebdbd5a20011fb205b",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2015-09-27\n📝 Original message:I was mansplaining weak blocks to my wife. She asked a simple question:\n\nWhy would I, as a miner, publish a weak block if I find one?\n\nI don't know.\n\nSure, I will get faster propagation for my solved block, should I find one.\nOn the other hand everybody else mining a similar block will enjoy the same\nbenefit. Assuming that I'm not a huge miner, it's unlikely that I will\nactually solve the block, so I'm probably just giving away fast propagation\ntimes to someone else.\n\nSo how does publishing a weak block benefit the producer of it more than\nthe other miners? Please help me understand this.\n\n/Kalle Rosenbaum\n\n\n2015-09-27 11:42 GMT+02:00 Tier Nolan via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e:\n\n\u003e\n\u003e\n\u003e On Sun, Sep 27, 2015 at 2:39 AM, Gregory Maxwell via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e Unless the weak block transaction list can be a superset of the block\n\u003e\u003e transaction list size proportional propagation costs are not totally\n\u003e\u003e eliminated.\n\u003e\u003e\n\u003e\n\u003e The POW threshold could be dynamic. The first weak-block that builds on a\n\u003e new block could be forwarded with a smaller target.\n\u003e\n\u003e This reduces the window size until at least one weak block is\n\u003e propagated.\n\u003e\n\u003e The change in threshold could be time based (for the first 30 seconds or\n\u003e so). This would cause a surge of traffic when a new block once a new block\n\u003e has propagated, so perhaps not so good an idea.\n\u003e\n\u003e\n\u003e\u003e As even if the weak block criteria is MUCH lower than the block\n\u003e\u003e criteria (which would become problematic in its own right at some\n\u003e\u003e point) the network will sometimes find blocks when there hasn't been\n\u003e\u003e any weak block priming at all (e.g. all prior priming has made it into\n\u003e\u003e blocks already).\n\u003e\u003e\n\u003e\n\u003e If there is a transaction backlog, then miners could forward merkle\n\u003e branches with transactions in the memory pool with a commitment in the\n\u003e coinbase.\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150927/04c13069/attachment.html\u003e",
"sig": "04789e9efbd83f9c9d458372cff808d88cf8f16bdd0567447af898b3b1e52a4659a404da6514df7d12e73ed61a0ba6cda93176343ef402fe8dd2cdfaaa6d8f68"
}