From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 7492B516 for ; Sat, 8 Apr 2017 16:05:53 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 1527013C for ; Sat, 8 Apr 2017 16:05:52 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:a45d:823b:2d27:961c]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 3EA2638A230B; Sat, 8 Apr 2017 16:05:11 +0000 (UTC) X-Hashcash: 1:25:170408:jaejoon@gmail.com::9Qo9ozcFhLXw6Eed:d8hS6 X-Hashcash: 1:25:170408:bitcoin-dev@lists.linuxfoundation.org::vwKENqdlcZOFKjCh:aT+Xj From: Luke Dashjr To: Jimmy Song Date: Sat, 8 Apr 2017 16:05:09 +0000 User-Agent: KMail/1.13.7 (Linux/4.9.16-gentoo; KDE/4.14.29; x86_64; ; ) References: <201704081459.13185.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201704081605.10175.luke@dashjr.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] A Small Modification to Segwit X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2017 16:05:53 -0000 On Saturday, April 08, 2017 3:17:47 PM Jimmy Song wrote: > Overt ASICBoost is allowed on the network already. Until a proposal > explicitly blocking overt ASICBoost as a soft fork is activated, this seems > to be better than the current state which is that overt ASICBoost is > allowed, but at a cost to BIP9 signals. No, it isn't allowed right now. Doing it wouldn't invalidate blocks, but it would clearly be an attack on the network and cause harm. The same as if miners were to maliciously mine only empty blocks. Luke