[Bitcoin-segwit2x] August Status Report for SegWit2x

digitsu jerry.d.chan at bittoku.co.jp
Sun Oct 1 12:53:49 UTC 2017

Exactly this.

Why is the fact that NYA signalling miners switching to mine BCH for a time even a point of discussion here? NYA signalling means that miners are telling you they will support btc1 fork when the fork event occurs.  It says NOTHING about what they can or cannot do BEFORE that event.  For some reason, folks like PeterT think that signalling what you intend to do 3 months later is somehow violated by profit seeking behaviour done today.  Perhaps this whole ‘roundtable’ and ‘knights honor’ theme has really gotten into people’s heads.

> On Aug 24, 2017, at 04:34, Guy Corem via Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
> It seems you believe that the miners are fish, with short-term memory only. Bitcoin Cash gives exactly zero indication of what will happen with s2x. The pools that signed the agreement will not allow legacy chain mining. Sure, some of the core supporting miners will mine Slush pool, but I don't believe the hash rate on the legacy chain will be above 10%.
> Without HF to adjust retargeting algorithm, the legacy chain will be unusable.
> On Aug 23, 2017 10:21 PM, "Peter Todd via Bitcoin-segwit2x" <bitcoin-segwit2x at lists.linuxfoundation.org <mailto:bitcoin-segwit2x at lists.linuxfoundation.org>> wrote:
> On Wed, Aug 23, 2017 at 08:12:13PM +0100, Alex Morcos wrote:
> > Forget about the name.
> >
> > Peter's point is all the miners agreed to run Segwit2x-defined-Bitcoin
> > (call this Bitcoin for short), yet they all defected from Bitcoin to run
> > Bitcoin-Cash when it was in their economic interest.  They will obviously
> > defect from Bitcoin to run
> > Old-Crappy-No2x-BlockstreamCore-Obstructionist-Not-Bitcoin in just the same
> > way if it is also in their economic interest.
> Exactly.
> The questions about "What it Bitcoin?" are unrelated to my main point, which is
> independent of what people decide to call things. I think you just did a better
> job arguing it than me. :)
> --
> https://petertodd.org <https://petertodd.org/> 'peter'[:-1]@petertodd.org <http://petertodd.org/>
> _______________________________________________
> Bitcoin-segwit2x mailing list
> Bitcoin-segwit2x at lists.linuxfoundation.org <mailto:Bitcoin-segwit2x at lists.linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x <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/20171001/304d565f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 874 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/attachments/20171001/304d565f/attachment-0001.sig>

More information about the Bitcoin-segwit2x mailing list