Alex Waters [ARCHIVE] on Nostr: 📅 Original date posted:2011-09-14 🗒️ Summary of this message: Gavin Andresen ...
📅 Original date posted:2011-09-14
🗒️ Summary of this message: Gavin Andresen suggests that forking changes should not be introduced until there is a compelling reason, and should be saved for when they are necessary.
📝 Original message:On Wed, Sep 14, 2011 at 4:28 PM, Gavin Andresen <gavinandresen at gmail.com> wrote:
> What do other people think? I think it is too high risk for too
> little benefit and shouldn't be done until we have a really compelling
> reason to introduce a forking change.
Could we bundle this and potential future blockchain-splitting changes
- to implement them in a major release (down the road)? Or save them
for when they are very necessary?
TL;DR shelf it until needed, have it written just in case.
-Alex
🗒️ Summary of this message: Gavin Andresen suggests that forking changes should not be introduced until there is a compelling reason, and should be saved for when they are necessary.
📝 Original message:On Wed, Sep 14, 2011 at 4:28 PM, Gavin Andresen <gavinandresen at gmail.com> wrote:
> What do other people think? I think it is too high risk for too
> little benefit and shouldn't be done until we have a really compelling
> reason to introduce a forking change.
Could we bundle this and potential future blockchain-splitting changes
- to implement them in a major release (down the road)? Or save them
for when they are very necessary?
TL;DR shelf it until needed, have it written just in case.
-Alex