Quote from: awemany on August 17, 2015, 06:30:53 PM

Hi folks,

as announced and also proposed by Peter__R around here, I created the draft what should become a BIP on Bitcoin/Core for a completely user-defined limit.

Note that I didn't ask Peter__R yet but put him into the document as an author - so do not take it as his endorsement!

The link to the PDF is here:

https://github.com/awemany/bslconfig/releases/download/first-draft/bslconfig.pdf

And here is the link to the github repo, feel free to fork it and make it better (for example, fix the language of this non-native English speaker):

https://github.com/awemany/bslconfig/

I am looking forward to any feedback on this!

EDIT: I am sorry, new to github 'releases'. Links should work now!

This is a great idea and further adds to decentralization. However, I think you may run into a problem if you don't have a preset default. Many non-technical users or users that have not followed the debate may not understand this setting or be fully aware of all of its implications. If the user enters 1 mb as the limit while the network is producing >1mb blocks, then they run the risk of getting routed to a bad fork. I would suggest having a default despite perception of bias, to protect users only. Perhaps you could even have no limit as the default.

For example, you could have two radio buttons. One with a default value and the caption "choose this setting if you don't fully understand the block size limit." The other that enables a text box or drop-down menu that let's the user input the block size limit of their choosing with the caption "advanced - leave blank for no limit" - or something similar.