[CSL-48] [Research] Block size

[jagajaga]

@georgeee

From Charles:

Charles:
we also have to decide on block size
my advice is start with something like 2 mb and then include a metric to gradually increase block size over time
something connected to estimated rate of growth in disk space and also network capacity
it depends upon block generation rate
and also average transaction size
but we have to have an opinion on it

George:
Do we need to explicitly restrict block size? Can't we just include all transactions ready-to-go and don't care much about block size? (edited)

Charles:
yes because you can spam the network
I can create a block of massive size and no one can download it

George:
Sure, obviously.

Charles:
there is a lot of content on this. It's an interesting topic to consider

George:
But can't we just hardcode this value and increase it eventually in new releases. Having well-written update system nodes won't operate with blocks of new size if they didn't update yet

Ivan:
Increasing block size limit manually means changing protocol rules, it's not easy (AFAIK)

Charles:
I suggest you guys add this to your list of topics to review
google bitcoin blocksize debate
ivan is correct
the size is a bit premature to set
usually you have three factors driving the conversaion
the expected TPS
the rate of blockchain growth
and network propagation of blocks
refer to this paper

http://www.gsd.inesc-id.pt/~ler/docencia/rcs1314/papers/P2P2013_041.pdf

we need to understand more about the PoS algorithm
and it's impact on the system
as well as expect Transaction size
so it will likely be the last thing we fix prior to the launch

https://bitcoincore.org/en/2016/10/28/segwit-costs/

[jagajaga]

@georgeee

Contact Chepurnoy & other researchers right after reading papers Charles suggested.

[jagajaga]

@georgeee

https://blockchain.info/charts/avg-block-size?timespan=all

[jagajaga]

@georgeee

Look at BIPS 101-109. They reflect BTC block size debate
Also don't forget to update document https://docs.google.com/spreadsheets/d/1wqe90w2Pn4WaFcxM-hOcc5zmPD2xeJS_9mKCdOZ_VZ4/edit#gid=0 with results of review

[jagajaga]

@georgeee

Also, think of slotDuration.
Increasing block size would eventually break system if we not adjust slotDuration over time as well.
Cause slotDuration is determined as time range large enough for any message to spread over network.

[jagajaga]

@georgeee

Also, consider limiting size of address, transaction. It may be usable as well

[jagajaga]

@georgeee

For address: to be clarified, depending on which direction CSL-347 goes

[jagajaga]

@manpages

Cause

[jagajaga]

@manpages

Initial version of the article is done.

[jagajaga]

@georgeee

https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki