{"type":"rich","version":"1.0","author_name":"npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7f","author_url":"https://nostr.ae/npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7f","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 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"}