<div dir="auto"><div>Answers inline...<div dir="auto"><br></div><br><div class="gmail_extra"><br><div class="gmail_quote">On Oct 12, 2017 6:41 AM, "Melvin Carvalho via Bitcoin-segwit2x" <<a href="mailto:bitcoin-segwit2x@lists.linuxfoundation.org">bitcoin-segwit2x@lists.linuxfoundation.org</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div class="quoted-text">On 12 October 2017 at 14:49, Peter BitcoinReminder.com via Bitcoin-segwit2x <span dir="ltr"><<a href="mailto:bitcoin-segwit2x@lists.linuxfoundation.org" target="_blank">bitcoin-segwit2x@lists.<wbr>linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Since F2Pool stopped signaling for the NYA[1] and slush also mines mostly non-NYA blocks, are you still going to fork off in November - splitting the chain intentionally? </div></blockquote><div><br></div></div><div>This is good new information, thanks!<br></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">It is information over a month old. See counter.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>A sensible approach might be:<br><br></div><div>1. Allow the implementation of Schnorr signatures<br></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Very risky- this impacts tx message integrity and authenticity. Changing transaction signing code impacts private keys and other security sensitive surfaces.</div><div dir="auto"><br></div><div dir="auto">In comparison, changing the size of the message container - a block - does not impact message integrity and authenticity.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>2. In parallel, address the issues raised on the segwit2x codebase<br></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Link to the issues filed?</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>3. Unfreeze the segwit2x code, and seek a dialogue with core on a timeline for a 2x block size increase<br></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">All field evidence points to continual delays, never a base block size increase as has been planned since 2010.</div><div dir="auto"><br></div><div dir="auto">Repeated attempts at dialogue just result in attacks, delays, The Familiar Stuff.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>The reason being that we've just had a capacity upgrade and segwit is starting to kick in. Blocks are less congested now. Schnorr will likely give another 30% capacity quite soon. This will allow general hardware increases to make moving to 2x blocks, without a contentious hard fork, more practical.<br></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">It is extremely contentious to continue blocking a block size increase.</div><div dir="auto"><br></div><div dir="auto">Continued delay is part of what produced the gridlock that we saw over the past two years.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Just my 2 cents.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><br></div></div><div>—</div><div>[1] <a href="https://imgur.com/LgYdFKw" target="_blank">https://imgur.com/LgYdFKw</a></div><div><br></div></div><br>______________________________<wbr>_________________<br>
Bitcoin-segwit2x mailing list<br>
<a href="mailto:Bitcoin-segwit2x@lists.linuxfoundation.org" target="_blank">Bitcoin-segwit2x@lists.linuxfo<wbr>undation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-s<wbr>egwit2x</a><br>
<br></blockquote></div><br></div></div>
<br>______________________________<wbr>_________________<br>
Bitcoin-segwit2x mailing list<br>
<a href="mailto:Bitcoin-segwit2x@lists.linuxfoundation.org">Bitcoin-segwit2x@lists.<wbr>linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>segwit2x</a><br>
<br></blockquote></div><br></div></div></div>