I was under the impression they are already adding a 1.75-2MB "buffer" in April. Are you now advocating for the need of 4MB instead? Should we fork Classic and increase maxBlockSize to 4MB now?
no.. thats a misdirect.. they are switchin data around into 2 blocks. the main block and the witness block.. but.. here is the kicker.. all the other features of blockstream will add more data to the main block that the moving of signatures meant to have saved.
for instance a signature is less data saved than the 250bytes of data that a payment code would have in the main blockchain.
so the average transactions size of a 2009-2015 tx would be less data. than a 2016 segwit confidential transaction.
take for instance a very laymans tx (dont knit pick. its for simple demo purposes and not real data lengths or real data)
{TXID:0123456790ABCDEF
IN[TXID:ABCDEF0123456790,sig:a0b1c2d345e67f89]
OUT[address:1Ar4nd0m4ddr3ss,value:100000000]
}
lets say this very layman tx is 116 characters
with segwit it would be
mainblock
{TXID:0123456790ABCDEF
IN[TXID:ABCDEF0123456790]
OUT[address:1Ar4nd0m4ddr3ss,value:100000000]
}
now 95 characters(blockstreamers utopian promise of less data.. but).. PLUS
witness
{TXID:0123456790ABCDEF
0:a0b1c2d345e67f89
}
44 characters. (totalling 139)as the witness merkle needs the TXID and an index to be able to refer back to the mainblock tx and the mainblock tx needs to refer to the witness merkle
then ontop.. lets start thinking about the new features, eg confidential transactions would turn a segwit FULL ARCHIVAL DATA transaction into
{TXID:0123456790ABCDEF
IN[TXID:ABCDEF0123456790]
OUT[address:1Ar4nd0m4ddr3ss,value:PC1234567890987654321abcdeffedcba]
}
{TXID:0123456790ABCDEF
0:a0b1c2d345e67f89
}
which in total would be a laymans 119 in the mainblock vs the old 116 in the main block (segwit+confidential fulldata combined=163)
so thats why core needs to set the mainblock limit to 2000000 ASWELL as all their little features.. so that its true capacity increase aswell as features increase.