Anthony Towns [ARCHIVE] on Nostr: ๐
Original date posted:2015-12-17 ๐ Original message:On Thu, Dec 17, 2015 at ...
๐
Original date posted:2015-12-17
๐ Original message:On Thu, Dec 17, 2015 at 04:51:19PM +0100, sickpig--- via bitcoin-dev wrote:
> On Thu, Dec 17, 2015 at 2:09 PM, Jorge Timรณn wrote:
> > Unless I'm missing something, 2 mb x4 = 8mb, so bip102 + SW is already
> > equivalent to the 2-4-8 "compromise" proposal [...]
> isn't SegWit gain ~75%? hence 2mb x 1.75 = 3.5.
Segwit as proposed gives a 75% *discount* to witness data with the
same limit, so at a 1MB limit, that might give you (eg) 2.05MB made up
of 650kB of base block data plus 1.4MB of witness data; where 650kB +
1.4MB/4 = 1MB at the 1MB limit; or 4.1MB made up of 1.3MB of base plus
2.8MB of witness, for 1.3MB+2.8MB/4 = 2MB at a 2MB limit.
> 4x is theoric gain you get in case of 2-2 multisig txs.
With segregated witness, 2-2 multisig transactions are made up of 94B
of base data, plus about 214B of witness data; discounting the witness
data by 75% gives 94+214/4=148 bytes. That compares to about 301B for
a 2-2 multisig transaction with P2SH rather than segwit, and 301/148
gives about a 2.03x gain, not a 4x gain. A 2.05x gain is what I assumed
to get the numbers above.
You get further improvements with, eg, 3-of-3 multisig, but to get
the full, theoretical 4x gain you'd need a fairly degenerate looking
transaction.
Pay to public key hash with segwit lets you move about half the
transaction data into the witness, giving about a 1.6x improvement by
my count (eg 1.6MB = 800kB of base data plus 800kB of witness data,
where 800kB+800kB/4=1MB), so I think a gain of between 1.6 and 2.0 is
a reasonable expectation to have for the proposed segwit scheme overall.
Cheers,
aj
Published at
2023-06-07 17:46:35Event JSON
{
"id": "f375f865badbc0503fecce8cd4f7145023eec915d5ba9dc61a14b6c347eb3351",
"pubkey": "f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab",
"created_at": 1686159995,
"kind": 1,
"tags": [
[
"e",
"46b1d48aa4e00b636e8dc4e9c37e717542bb528954bcd46114dd6b14e1119e69",
"",
"root"
],
[
"e",
"c9e08da838ffd9beca80636f68e0cccc8d431fc4b7f973467a659122095012da",
"",
"reply"
],
[
"p",
"6d57865557024df52765583218ef3ffec184f7423a66f5284d92b8851cbca430"
]
],
"content": "๐
Original date posted:2015-12-17\n๐ Original message:On Thu, Dec 17, 2015 at 04:51:19PM +0100, sickpig--- via bitcoin-dev wrote:\n\u003e On Thu, Dec 17, 2015 at 2:09 PM, Jorge Timรณn wrote:\n\u003e \u003e Unless I'm missing something, 2 mb x4 = 8mb, so bip102 + SW is already\n\u003e \u003e equivalent to the 2-4-8 \"compromise\" proposal [...]\n\u003e isn't SegWit gain ~75%? hence 2mb x 1.75 = 3.5.\n\nSegwit as proposed gives a 75% *discount* to witness data with the\nsame limit, so at a 1MB limit, that might give you (eg) 2.05MB made up\nof 650kB of base block data plus 1.4MB of witness data; where 650kB +\n1.4MB/4 = 1MB at the 1MB limit; or 4.1MB made up of 1.3MB of base plus\n2.8MB of witness, for 1.3MB+2.8MB/4 = 2MB at a 2MB limit.\n\n\u003e 4x is theoric gain you get in case of 2-2 multisig txs.\n\nWith segregated witness, 2-2 multisig transactions are made up of 94B\nof base data, plus about 214B of witness data; discounting the witness\ndata by 75% gives 94+214/4=148 bytes. That compares to about 301B for\na 2-2 multisig transaction with P2SH rather than segwit, and 301/148\ngives about a 2.03x gain, not a 4x gain. A 2.05x gain is what I assumed\nto get the numbers above.\n\nYou get further improvements with, eg, 3-of-3 multisig, but to get\nthe full, theoretical 4x gain you'd need a fairly degenerate looking\ntransaction.\n\nPay to public key hash with segwit lets you move about half the\ntransaction data into the witness, giving about a 1.6x improvement by\nmy count (eg 1.6MB = 800kB of base data plus 800kB of witness data,\nwhere 800kB+800kB/4=1MB), so I think a gain of between 1.6 and 2.0 is\na reasonable expectation to have for the proposed segwit scheme overall.\n\nCheers,\naj",
"sig": "3a39eea90e36641f533c003c4967b7f7b9f297d1a283494839119f946f80949c7e4533ea7dc91b472802ddbd08ac7ca4018d63b8423a939b2479a2eb8f82edba"
}