On February 21st, 2016, in Hong Kong’s Cyberport, representatives from the bitcoin industry and members of the development community have agreed on the following points:We understand that SegWit continues to be developed actively as a soft-fork and is likely to proceed towards release over the next two months, as originally scheduled.We will continue to work with the entire Bitcoin protocol development community to develop, in public, a safe hard-fork based on the improvements in SegWit.The Bitcoin Core contributors present at the Bitcoin Roundtable commit to make a good faith effort to have an implementation of such a hard-fork ready for merge within three months after the release of SegWit.This hard-fork is expected to include features which are currently being discussed within technical communities, including an increase in the maximum effective block size, to more than 2 MB and less than 4 MB, and will only be adopted with a broad support across the entire Bitcoin community. -We will run a SegWit release in production by the time such a hard-fork is released in a version of Bitcoin Core.We will not run Bitcoin Classic. We will only run Bitcoin Core-compatible consensus systems in production for the foreseeable future.We are committed to scaling technologies which use block space more efficiently, such as Schnorr multisig.Based on the above points, the timeline will likely follow the below dates.SegWit is expected to be released in April 2016.The code for the hard-fork will therefore be available by July 2016.If there is strong community support, the hard-fork activation will likely happen around July 2017.The undersigned support this roadmap. via /r/Bitcoin http://bit.ly/1XE3fKb
No comments :
Post a Comment