<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>The hardfork part is already locked in and is not subject to
change. Many btc1 nodes are already deployed and they should not
and don't need to update. The only thing left is a potential extra
softfork for opt-in replay protection. Only the miners need this
softfork.</p>
<p>What makes you think the hardfork will have less than 40%
hashpower?<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">Emil Oldenburg, CTO
<a class="moz-txt-link-abbreviated" href="mailto:Emil@bitcoin.com">Emil@bitcoin.com</a>
Visit the all new <a class="moz-txt-link-freetext" href="https://bitcoin.com">https://bitcoin.com</a>
Wechat: emilold
Telegram: emilold</pre>
<div class="moz-cite-prefix">On 2017年10月13日 17:31, Peter
BitcoinReminder.com wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8E765460-59BF-468B-A568-49927E4777DF@bitcoinreminder.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Thats not a reason, the BTC1 sourcecode is still in development
(f.e. replay protection was reverted just 1-2 days ago?) - so the
argument „it can’t be called off“ is just wrong.
<div class=""><br class="">
</div>
<div class="">So wouldn’t it make sense to add a minimum required
hashrate for the HF to lock in? You are really going to fork off
with f.e. 40 % hashpower?</div>
<div class=""><br class="">
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">Am 13.10.2017 um 03:42 schrieb Emil
Oldenburg via Bitcoin-segwit2x <<a
href="mailto:bitcoin-segwit2x@lists.linuxfoundation.org"
class="" moz-do-not-send="true">bitcoin-segwit2x@lists.linuxfoundation.org</a>>:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">If we try to be technical here. The HF is
already activated, is estimated to trigger in 36
days, and can't be "called off". Nor is there any
logic to delay it if hashrate deflects. That's the
rules of the btc1 client.<br class="">
</p>
<p class=""><br class="">
</p>
<pre class="moz-signature" cols="72">Emil Oldenburg, CTO
<a class="moz-txt-link-abbreviated" href="mailto:Emil@bitcoin.com" moz-do-not-send="true">Emil@bitcoin.com</a>
Visit the all new <a class="moz-txt-link-freetext" href="https://bitcoin.com/" moz-do-not-send="true">https://bitcoin.com</a>
Wechat: emilold
Telegram: emilold</pre>
<div class="moz-cite-prefix">On 2017年10月13日 05:31,
John Heathco via Bitcoin-segwit2x wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:CAPwBOFU4wVgCVL6gpZ7HUo2d4i8gmESMRbUEpobT2RqygLy=ZA@mail.gmail.com"
class="">
<div class="">
<div dir="auto" class="">I don't believe there is
an explicitly stated hashpower in which the fork
would be "called off", but I would assume it is
much lower than what is currently signaling,
even if we make the (unwise) assumption that
F2Pool would not contribute to mining 2x
whatsoever.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class=""><br class="">
</div>
<br class="">
<div class="gmail_quote">
<div class="">On Thu, Oct 12, 2017 at 12:57 PM
Peter <a href="http://BitcoinReminder.com"
class="" moz-do-not-send="true">BitcoinReminder.com</a>
via Bitcoin-segwit2x <<a
href="mailto:bitcoin-segwit2x@lists.linuxfoundation.org"
moz-do-not-send="true" class="">bitcoin-segwit2x@lists.linuxfoundation.org</a>>
wrote:<br class="">
</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" class="">
<div class="">I’m not Peter Todd, we just
share the same (nice) firstname.</div>
<div class=""><br class="">
</div>
<div class="">I still didn’t get an answer
what the minimum amount of hashpower is
required, before the fork is getting
delayed?</div>
<div class="">We have to plan time for the
whole security measures etc, so I think
it’s reasonable to get more information
about this?</div>
</div>
<div style="word-wrap:break-word" class="">
<div class=""><br class="">
<div class=""><br class="">
</div>
<div class="">
<div class="">
<blockquote type="cite" class="">
<div class="">Am 12.10.2017 um 21:53
schrieb bitPico <<a
href="mailto:bitpico@icloud.com"
target="_blank"
moz-do-not-send="true" class="">bitpico@icloud.com</a>>:</div>
<br
class="m_6746094084308521097Apple-interchange-newline">
<div class="">
<div style="word-wrap:break-word"
class="">Without you knowing why
they stopped signaling this is
FUD and off-topic for this list.
Please instead let F2Pool state
their own opinion here since
yours doesn’t count. If you
think your opinion does count
then show us your blocks that
your pool has produced; until
then you are simply an end-user
and still you are off-topic for
this list. If you need ELI5 for
how this list works please let
us know and we can help you
Peter Todd.
<div class=""><br class="">
</div>
<div class="">Have a groovy day!<br
class="">
<div class=""><br class="">
<div class="">
<blockquote type="cite"
class="">
<div class="">On Oct 12,
2017, at 8:49 AM,
Peter <a
href="http://bitcoinreminder.com/"
target="_blank"
moz-do-not-send="true"
class="">BitcoinReminder.com</a>
via Bitcoin-segwit2x
<<a
href="mailto:bitcoin-segwit2x@lists.linuxfoundation.org"
target="_blank"
moz-do-not-send="true"
class="">bitcoin-segwit2x@lists.linuxfoundation.org</a>>
wrote:</div>
<br
class="m_6746094084308521097Apple-interchange-newline">
<div class="">
<div
style="word-wrap:break-word"
class="">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 class="">
<div class=""><br
class="">
</div>
</div>
<div class="">—</div>
<div class="">[1] <a
href="https://imgur.com/LgYdFKw" target="_blank" moz-do-not-send="true"
class="">https://imgur.com/LgYdFKw</a></div>
<div class=""><br
class="">
</div>
</div>
_______________________________________________<br class="">
Bitcoin-segwit2x
mailing list<br
class="">
<a
href="mailto:Bitcoin-segwit2x@lists.linuxfoundation.org"
target="_blank"
moz-do-not-send="true"
class="">Bitcoin-segwit2x@lists.linuxfoundation.org</a><br
class="">
<a
href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x"
target="_blank"
moz-do-not-send="true"
class="">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
_______________________________________________<br class="">
Bitcoin-segwit2x mailing list<br class="">
<a
href="mailto:Bitcoin-segwit2x@lists.linuxfoundation.org"
target="_blank" moz-do-not-send="true"
class="">Bitcoin-segwit2x@lists.linuxfoundation.org</a><br
class="">
<a
href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x</a><br
class="">
</blockquote>
</div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre class="" wrap="">_______________________________________________
Bitcoin-segwit2x mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-segwit2x@lists.linuxfoundation.org" moz-do-not-send="true">Bitcoin-segwit2x@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x" moz-do-not-send="true">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br
class="">
Bitcoin-segwit2x mailing list<br class="">
<a
href="mailto:Bitcoin-segwit2x@lists.linuxfoundation.org"
class="" moz-do-not-send="true">Bitcoin-segwit2x@lists.linuxfoundation.org</a><br
class="">
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<br>
</body>
</html>