Bitcoin-BLAKE2b will launch with the block size reduced to 300 KB. The change will automatically expire after one year, just like the other RDTS (BIP-110) changes.
This will provide a good opportunit...
how is that limit expressed? like, vBytes as with bitcoin core that is "1 megabyte" but due to witness discount on weight it means actually 4mb at most (not quite, but yes one tx could theoretically have close to 4mb of data plus the normal weight single transaction. practically this means most bitcoin core blocks are between 1 and 3mb.
if the new limit is on that same basis of "300kVbytes" then in practice it means a theoretical max size around 750kb of block which actually isn't as extreme a divergence from the original pre-segwit-witness-discount as it sounds.
why not just remove the witness discount though? that would have approximately the same effect. and why does RDTS ever expire. is there any statement about what happens after that? also is the mempool going to be shared, i mean, there's literally no way to stop it being shared without adding a fork identifier to transactions, they will be the same on either side as they don't identify the chain, they are simply valid on the uxto set.
if the new limit is on that same basis of "300kVbytes" then in practice it means a theoretical max size around 750kb of block which actually isn't as extreme a divergence from the original pre-segwit-witness-discount as it sounds.
why not just remove the witness discount though? that would have approximately the same effect. and why does RDTS ever expire. is there any statement about what happens after that? also is the mempool going to be shared, i mean, there's literally no way to stop it being shared without adding a fork identifier to transactions, they will be the same on either side as they don't identify the chain, they are simply valid on the uxto set.
2
