Today's meeting was IMO largely unproductive, but we did manage to come to consensus on everything but LockinOnTimeout.

Activation height range: 693504-745920
MASF threshold: 1815/2016 blocks (90%)

Keep in mind only ~100 people showed for the meetings, hardly representative of the entire community.
So, these details remain JUST a proposal for now.

It seems inevitable that there won't be consensus on LOT.
Everyone will have to choose for himself. :/


@lukedashjr if Core has a responsibility to act in the best interest of the chain/bitcoin/ecosystem then the obvious choice is to set it to True. Setting it as False is not impartial. leaving it unset and forcing users to decide on install is.
their argument smells like bullshit

Sign in to participate in the conversation
Bitcoin Mastodon

Bitcoin Maston Instance