mimblewimble team mailing list archive

[Andrew Bellenie <andybellenie@xxxxxxxxx>]

I agree, except I don't see a reason to limit it to the first 2 years. Six
monthly upgrades seem to be well accepted by the Monero community. I'd
leave the option open, besides, it could always be removed or adjusted in
one of the upgrades (e.g. move to annual, then bi-annual, or stop
altogether).

I like the solstice idea too for entirely non-technical reasons.

On 3 October 2017 at 21:29, Ignotus Peverell <igno.peverell@xxxxxxxxxxxxxx>
wrote:

> Hi all,
>
> As we're preparing both a fully new blockchain format and implementation
> we, developers, are bound to make mistakes. Some of them will be trivial to
> correct, and some of them will not, requiring changes in consensus
> parameters. We will also want to "clean up" some technical debt that can
> accumulate in younger implementations. So I think it's fair to ask for some
> leeway to hard fork when required, at least at the beginning.
>
> To make that process easier and more predictable, I would like to include
> scheduled hard forks with the following limitations:
>
>    - Only 2 scheduled hard forks per year.
>    - Only for the first 2 years.
>
> The mechanism would be a mandated block version increase every 6 months,
> limited to 4 increases.
>
> Thoughts?
>
> - Igno
>
> P.S. Thanks to yeastplume for suggesting we establish a pre-defined
> schedule.
>
> --
> Mailing list: https://launchpad.net/~mimblewimble
> Post to     : mimblewimble@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mimblewimble
> More help   : https://help.launchpad.net/ListHelp
>
>