<<  >> (p.2)
    Author Topic: Permanently keeping the 1MB (anti-spam) restriction is a great idea ...  (Read 105323 times)
    zimmah
    Legendary
    *
    Offline Offline

    Activity: 1106
    Merit: 1005



    View Profile
    February 05, 2015, 06:12:10 AM
     #21

    Great post.

    Perhaps the best way to deal with the transaction limit, so it does not continue to be a problem, is to quadruple the block limit size at each block reward halving every 4 years.  This should put in in line with Moore's Law, such that running a full node won't be out of reach of the average user.


    I like the simplicity of this strategy and it has grounding in practical limitations for physical hardware.

    Although I would suggest to have it at the midway points between halvings so as to smooth out any lumpiness in the response to fees/reward when changing the halving and max_block_size increase together. Analogous to presidential and mid-term election cycles.

    So quadruple max_block_size at 315k, 525k, 735k, 945k, thereafter every 210k blocks. But need to begin with a one-off quadruple increase to 4 MByte ASAP (to account for previous increase that would have ideally happened at 315k).

    Edit: on further thought maybe doubling every 105k blocks is less disruptive again, instead of banging the limit every so often. So a one-off quadruple to 4 MB ASAP then double to 8 MB at next halving (420k blocks) and double every 105k blocks thereafter, i.e. double approx. every 2 years, more or less, depending on hashrate, which is a rough proxy for network demand via price.


    yeah, sounds good.

    the actual numbers and frequency could be tweaked, but the idea seems good.

    This prevents us from having to hardfork it every time.
Page 1
Viewing Page: 2