[Bitcoin-segwit2x] Alpha Milestone

[Oliver Petruzel]

Hugh -
The link on Bitcoin.org will simply have to change if/when SegWit2x
successfully becomes the new reference client.

Alternatively, Core would also merge the hardfork changes into their own
client, and Bitcoin.org would provide links to both (all) compatible
clients -- with "compatibility" defined as any client that implements the
consensus rules found in SegWit2x.

I think the current focus is rightfully on existing nodes/businesses/users,
so let's not put the cart before the horse.

Oliver

On Jun 14, 2017 19:52, "Hugh Madden via Bitcoin-segwit2x" <
bitcoin-segwit2x at lists.linuxfoundation.org> wrote:

> Ultimately most users and businesses will simply apt-get update or
> download the client from bitcoin.org
>
> If we expect incoming and unsophisticated users to choose a fork to be
> compatible with s2x it's dead in the water IMHO
>
>
>
> On 15 Jun. 2017 1:35 am, "Alex Bosworth via Bitcoin-segwit2x" <
> bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
>
>> Are things still on track for the hard fork aspect? Specifically I
>> haven't identified code in the alpha for providing strong 2-way replay
>> protection? (This means transactions valid on one chain should be invalid
>> on the other, and vice-versa) And for wipe-out protection? (Once forked,
>> the fork should remain permanent).
>>
>> Absent firm support for this specific hard fork from BitFinex (the
>> largest volume exchange, Local Bitcoins (the largest volume peer exchange),
>> Slush pool, Trezor, Ledger, Electrum, and many others in the industry and
>> individuals in the development and broader community, the chance for a
>> contentious fork is present, which would suggest those hard fork features
>> would help make a BIP 102 hard fork supportable by neutral service providers
>>
>> On Wed, Jun 14, 2017 at 10:08 AM Mike Belshe via Bitcoin-segwit2x <
>> bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
>>
>>> Hi Segwit2x team:
>>>
>>>
>>>
>>> As we approach the June 15 Alpha milestone, we wanted to compile a
>>> status update.
>>>
>>>
>>>
>>> General
>>>
>>> Segwit2x development has been moving quickly according to plan, and the
>>> project is in good shape.  The  development of the alpha version is near
>>> complete, as is the initial round of testing. Testnet5 has been released,
>>> and we we will be releasing alpha binaries by June 16th, as planned,
>>> which are ready for further testing with the larger group.
>>>
>>>
>>>
>>> June 16 Alpha Deliverable
>>>
>>>    -
>>>
>>>    BIP91 w/ bit4 Segwit Activation at 80%
>>>    -
>>>
>>>    BIP102-style 2MB base block size increase 3mo after Segwit Activation
>>>    -
>>>
>>>    Created testnet5 for testing
>>>    -
>>>
>>>    Manual testing
>>>
>>>
>>>
>>> Alpha Period Dry Runs
>>>
>>> During the Alpha period, we are scheduling multiple “dry run” dates.
>>> These are scheduled times when we’ll execute the 2MB Blocksize increase
>>> across multiple parties on the test network.  We encourage as many
>>> participants as possible to participate in these dry runs and report status
>>> of how various node versions (both newer and older) execute during the
>>> upgrade process.  To participate, parties need to run the testnet5 alpha
>>> binaries available on the btc1 github <https://github.com/btc1>.
>>>
>>>
>>>
>>> To Do List
>>>
>>> Here are some of the open items:
>>>
>>>    -
>>>
>>>    Additional testing from all parties
>>>    -
>>>
>>>    Published Test Plan to date
>>>    -
>>>
>>>    Write a BIP for the process
>>>    -
>>>
>>>    Coordinate multiple “dry run” dates until the process is smooth
>>>    -
>>>
>>>    Production of Gitian builds
>>>
>>>
>>>
>>> Communications
>>>
>>> Follow the github here: https://github.com/btc1
>>>
>>> Subscribe the mailing list: https://lists.linuxfoundation.
>>> org/mailman/listinfo/bitcoin-ng
>>>
>>>
>>>
>>> Thank You
>>>
>>> Finally, a big thank you to all that have contributed so far.  We still
>>> need more developers and testers in the phases ahead, but the project has
>>> been growing every week!
>>>
>>> _______________________________________________
>>> Bitcoin-segwit2x mailing list
>>> Bitcoin-segwit2x at lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x
>>>
>> --
>> Sent from my iPhone
>>
>> _______________________________________________
>> Bitcoin-segwit2x mailing list
>> Bitcoin-segwit2x at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x
>>
>>
> _______________________________________________
> Bitcoin-segwit2x mailing list
> Bitcoin-segwit2x at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/attachments/20170614/f849e1a7/attachment.html>