Block size possible solution - to set minimum size #6581

issue bdimych opened this issue on August 22, 2015
  1. bdimych commented at 11:06 PM on August 22, 2015: none

    Hi, As I understand the main problem of the fork Core<->XT is possibility of double spending: -I run XT and spend my coins -it is written in 8mb block -Core does not accept this block -I run Core and spend my coins again -it is written in 1mb block -but XT accepts this block too so -in the XT blockchain both blocks [8] and [1] contain my coins

    I thought that possible solution can be to set minimum block size i.e. 2016: 1mb <= blockSize < 2mb 2017: 2mb <= blockSize < 3mb 2018: 3mb <= blockSize < 4mb etc

    Free space could be filled with zeroes and compressed.

    That's all, just an idea.

  2. laanwj commented at 10:03 AM on August 24, 2015: member

    Please, no block size proposals here. The right place is the mailing list.

    (Also: most of the blocksize BIPs already feature automatic scaling of the block size over time. The problem is that you cannot predict the future so any automatic growth may be problematic at some point)

  3. laanwj closed this on Aug 24, 2015

  4. MarcoFalke locked this on Sep 8, 2021
Contributors

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 21:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me