📅 Original date posted:2017-05-08
📝 Original message:Sergio,
I'm not sure what the data you present has to do with the discount. A 75%
discount prevents witness spam precisely because it is 75%, nothing more.
The current usage simply gives a guideline on how much capacity is gained
through a particular discount. With the data you show, it would imply that
those blocks, with SegWit used where possible, would result in blocks of
~1.8MB.
On Mon, May 8, 2017 at 5:42 PM, Sergio Demian Lerner via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> I have processed 1000 blocks starting from Block #461653.
>
> I computed several metrics, including the supposed size of witness data
> and non-witness data (onchain), assuming all P2SH inputs/outputs are
> converted to P2PWSH and all P2PKH inputs/outputs are converted to P2WPKH.
>
> This takes into account that other types of transactions will not be
> modified by Segwit (e.g. OP_RETURN outputs, or P2PK). This analysis doesn't
> take into account that LN transactions may affect the current state,
> increasing the segwit/nosegwit ratio.
>
> Among a lot of information, I've got the following real world results...
>
> acMainChainSpace =352608924
> acSegwitSpace =599400403
> Ratio segwit/nosegwit=1.6999
>
> This implies that the 75% that discount is not the best option to prevent
> witness spam in a block of 4 MB, as stated in https://segwit.org/why-a-
> discount-factor-of-4-why-not-2-or-8-bbcebe91721e.
>
> The non-witness data weight factor should not be 4 but 2.35. The closest
> integer value is 2, which leads to a 50% witness discount.
>
> The Bitcoinj source code is available for anyone to review. I encourage
> anyone to re-compute this with another utility to cross-check. Maybe
> Antoine Le Calvez (p2sh.info) would like to double-check.
>
>
>
>
>
>
> _______________________________________________
> 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/20170508/eda3ff72/attachment.html>;
Alphonse Pace [ARCHIVE] /
npub1xd…lkyw0
2023-06-07 18:00:56
in reply to nevent1q…hf8g
Author Public Key
npub1xddusuj8cyeqaqalq0zklafvdgr26pt32t0tvquw5mmwwwm3dehsqlkyw0Published at
2023-06-07 18:00:56Event JSON
{
"id": "4ae66f415ac3468eea36da928fe062da797a2bb85aa177db7112f8ff256fc62e",
"pubkey": "335bc87247c1320e83bf03c56ff52c6a06ad057152deb6038ea6f6e73b716e6f",
"created_at": 1686160856,
"kind": 1,
"tags": [
[
"e",
"4aacc31e765e9e31a3d8eb41d296ff5dc213462528e2e5335cec5ccb80e70465",
"",
"root"
],
[
"e",
"4b9630f049d113dc23410a5c2f7905c44d1c2267028b5b71913d60e5d28a9209",
"",
"reply"
],
[
"p",
"4b38603408f5be002091210e869a4ca86fc2aa1ffd0871036a0668068ee626ee"
]
],
"content": "📅 Original date posted:2017-05-08\n📝 Original message:Sergio,\n\nI'm not sure what the data you present has to do with the discount. A 75%\ndiscount prevents witness spam precisely because it is 75%, nothing more.\nThe current usage simply gives a guideline on how much capacity is gained\nthrough a particular discount. With the data you show, it would imply that\nthose blocks, with SegWit used where possible, would result in blocks of\n~1.8MB.\n\n\n\nOn Mon, May 8, 2017 at 5:42 PM, Sergio Demian Lerner via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e I have processed 1000 blocks starting from Block #461653.\n\u003e\n\u003e I computed several metrics, including the supposed size of witness data\n\u003e and non-witness data (onchain), assuming all P2SH inputs/outputs are\n\u003e converted to P2PWSH and all P2PKH inputs/outputs are converted to P2WPKH.\n\u003e\n\u003e This takes into account that other types of transactions will not be\n\u003e modified by Segwit (e.g. OP_RETURN outputs, or P2PK). This analysis doesn't\n\u003e take into account that LN transactions may affect the current state,\n\u003e increasing the segwit/nosegwit ratio.\n\u003e\n\u003e Among a lot of information, I've got the following real world results...\n\u003e\n\u003e acMainChainSpace =352608924\n\u003e acSegwitSpace =599400403\n\u003e Ratio segwit/nosegwit=1.6999\n\u003e\n\u003e This implies that the 75% that discount is not the best option to prevent\n\u003e witness spam in a block of 4 MB, as stated in https://segwit.org/why-a-\n\u003e discount-factor-of-4-why-not-2-or-8-bbcebe91721e.\n\u003e\n\u003e The non-witness data weight factor should not be 4 but 2.35. The closest\n\u003e integer value is 2, which leads to a 50% witness discount.\n\u003e\n\u003e The Bitcoinj source code is available for anyone to review. I encourage\n\u003e anyone to re-compute this with another utility to cross-check. Maybe\n\u003e Antoine Le Calvez (p2sh.info) would like to double-check.\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\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/20170508/eda3ff72/attachment.html\u003e",
"sig": "14b533e7162231ba3335d78685fc3e8dfaf7a900a05fc91e06e3f888e6f2728b955c9ee5d27f04bfbf7452963ea9b2181da123a49df3ff920d91109d5a26993f"
}