[Bitcoin-segwit2x] September/October SegWit2x Status Update

[Will M]

We need to move onto a model where hammered cryptographic hash functions and “peer reviewed” cryptographic primitives are insufficient; all of these things should be approached with suspicion.

All that said, if you are selling, I’ll find a buyer. Cheers.

On Oct 25, 2017, 4:58 PM -0700, bitPico <bitpico at icloud.com>, wrote:
> ZeroDay flaws are to be reserved for special occasions. They are not meant to be shared or discussed. They have a very high value dollar-wise and also make for good bartering or deal making. Does 0.15 have ZeroDay flaws? Perhaps...
>
> On Oct 25, 2017, at 7:50 PM, Will M <will.madden at gmail.com> wrote:
>
> > Are you aware of a ZeroDay flaw that you are at liberty to share? Even if you cannot, I agree with your statement and position.
> >
> > On Oct 25, 2017, 4:49 PM -0700, bitPico <bitpico at icloud.com>, wrote:
> > > No; our statement was clear: Bitcoin Core 0.15 most likely contains developer only known bugs or ZeroDay flaws. 0.14 is the safest base code in that regard.
> > >
> > > EOC
> > >
> > > Thanks!
> > >
> > > On Oct 25, 2017, at 7:43 PM, Will M <will.madden at gmail.com> wrote:
> > >
> > > > bitPico, so you can say with confidence that the 518 open issues are all thoroughly analyzed and non-critical issues? I do not believe you.
> > > >
> > > > On Oct 25, 2017, 4:40 PM -0700, bitPico via Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org>, wrote:
> > > > > Bitcoin Core does not open GitHub tickets for ZeroDay exploits. That said; 0.15 is very experimental and most likely contains exploits that only the Core Developers are aware of. 0.14 is the most stable Bitcoin Core codebase and cannot be attacked by “secret bugs” because they don’t exist any longer.
> > > > >
> > > > > Sent from my Space Ship.
> > > > >
> > > > > On Oct 25, 2017, at 6:52 PM, Daniel Newton via Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
> > > > >
> > > > > > >7. I've been paying close attention to the Bitcoin Core 0.15.x rollout.    Based on instability and bugs that upstream
> > > > > > >Bitcoin Core project is seeing - ie. Core's bugs not ours - segwit2x will stay on Bitcoin Core 0.14.x through the
> > > > > > >November fork.  This is the most stable path for users, based on upstream Bitcoin Core instability.
> > > > > >
> > > > > > Is there a list of these issues?
> > > > > >
> > > > > > I havent heard of any problems except for the GUI issue that prompted the 0.15.0.1 release
> > > > > >
> > > > > > The issue tracker (https://github.com/bitcoin/bitcoin/issues?q=is%3Aissue+label%3ABug+is%3Aopen) does not show anything out of the ordinary
> > > > > >
> > > > > > > On Thu, Oct 26, 2017 at 6:54 AM, Jeff Garzik via Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
> > > > > > > > Hi all!
> > > > > > > >
> > > > > > > > This is a follow-on from the previous status update in August: https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-August/000265.html
> > > > > > > >
> > > > > > > > 1. To state the obvious, everything is still full steam ahead for segwit2x upgrade in mid-November.
> > > > > > > >
> > > > > > > > 2. As noted in August, the project continues to be in a code freeze for the fork:  https://en.wikipedia.org/wiki/Freeze_(software_engineering)   Only changes or fixes thought to be important pre-fork will be included.
> > > > > > > >
> > > > > > > > 3. Reviewing the btc1 project and branch policies, btc1 is a source code fork of Bitcoin Core, very much like Fedora Linux is a fork/distribution intended for end users.  As such, we track Bitcoin Core updates as necessary and pull those into the project.
> > > > > > > >
> > > > > > > > 4. "segwit2x" is the production release branch for the SegWit2x Working Group, and the latest release can be downloaded here: https://github.com/btc1/bitcoin/releases/tag/v1.14.5
> > > > > > > >
> > > > > > > > 5. "segwit2x-dev" is the development and testing release branch.  New changes go to segwit2x-dev first, for external testing and feedback, before being merged into the production branch, and labelled a production release.
> > > > > > > >
> > > > > > > > 6. The current segwit2x production release, on the segwit2x branch, is based on Bitcoin Core 0.14.x.   The current dev release is based on Bitcoin Core 0.15.x.
> > > > > > > >
> > > > > > > > 7. I've been paying close attention to the Bitcoin Core 0.15.x rollout.    Based on instability and bugs that upstream Bitcoin Core project is seeing - ie. Core's bugs not ours - segwit2x will stay on Bitcoin Core 0.14.x through the November fork.  This is the most stable path for users, based on upstream Bitcoin Core instability.
> > > > > > > >
> > > > > > > > In short we -do not- feel that Bitcoin Core bugs and instability will impact our project in the short term, because this is not yet in a segwit2x production release on a production branch.
> > > > > > > >
> > > > > > > > 8. The only change worth noting is a likely be an adjustment of miner policy defaults that will be accepted through the code freeze: https://github.com/btc1/bitcoin/pull/136
> > > > > > > >
> > > > > > > > Thanks everyone!
> > > > > > > >
> > > > > > > > --
> > > > > > > > Jeff Garzik
> > > > > > > > CEO and Co Founder
> > > > > > > > Bloq, Inc.
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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/20171025/cc3daa66/attachment.html>