ð
Original date posted:2017-05-08
ð Original message: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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170508/aaeb7ba1/attachment.html>;
Sergio Demian Lerner [ARCHIVE] /
npub1fvâŠ3vq7f
2023-06-07 18:00:55
in reply to nevent1qâŠt9zz
Author Public Key
npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7fPublished at
2023-06-07 18:00:55Event JSON
{
"id": "4b9630f049d113dc23410a5c2f7905c44d1c2267028b5b71913d60e5d28a9209",
"pubkey": "4b38603408f5be002091210e869a4ca86fc2aa1ffd0871036a0668068ee626ee",
"created_at": 1686160855,
"kind": 1,
"tags": [
[
"e",
"4aacc31e765e9e31a3d8eb41d296ff5dc213462528e2e5335cec5ccb80e70465",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "ð
Original date posted:2017-05-08\nð Original message:I have processed 1000 blocks starting from Block #461653.\n\nI computed several metrics, including the supposed size of witness data and\nnon-witness data (onchain), assuming all P2SH inputs/outputs are converted\nto P2PWSH and all P2PKH inputs/outputs are converted to P2WPKH.\n\nThis takes into account that other types of transactions will not be\nmodified by Segwit (e.g. OP_RETURN outputs, or P2PK). This analysis doesn't\ntake into account that LN transactions may affect the current state,\n increasing the segwit/nosegwit ratio.\n\nAmong a lot of information, I've got the following real world results...\n\nacMainChainSpace =352608924\nacSegwitSpace =599400403\nRatio segwit/nosegwit=1.6999\n\nThis implies that the 75% that discount is not the best option to prevent\nwitness spam in a block of 4 MB, as stated in\nhttps://segwit.org/why-a-discount-factor-of-4-why-not-2-or-8-bbcebe91721e.\n\nThe non-witness data weight factor should not be 4 but 2.35. The closest\ninteger value is 2, which leads to a 50% witness discount.\n\nThe Bitcoinj source code is available for anyone to review. I encourage\nanyone to re-compute this with another utility to cross-check. Maybe\nAntoine Le Calvez (p2sh.info) would like to double-check.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170508/aaeb7ba1/attachment.html\u003e",
"sig": "6dc8d9615b43738bf705e1d18d7a45aa6afebcfc414d4c787e41fa49e0e445706360b192c1647629d000b34e438442ac41bf76d2e8fa419194e817832d45a2e3"
}