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 A2D00898 for ; Wed, 28 Jun 2017 05:21:13 +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 8DDB218A for ; Wed, 28 Jun 2017 05:21:12 +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 057D038A224F; Wed, 28 Jun 2017 05:20:30 +0000 (UTC) X-Hashcash: 1:25:170628:bitcoin-dev@lists.linuxfoundation.org::c6Ttw9dCgUn9fVXy:v84L X-Hashcash: 1:25:170628:chris@suredbits.com::4MZOnIMPDzG/JZwr:fuxOK From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Chris Stewart Date: Wed, 28 Jun 2017 05:20:27 +0000 User-Agent: KMail/1.13.7 (Linux/4.9.16-gentoo; KDE/4.14.32; x86_64; ; ) References: 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: <201706280520.29105.luke@dashjr.org> X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, 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 Subject: Re: [bitcoin-dev] BIP: OP_BRIBVERIFY - the op code needed for Blind Merge Mined drivechains 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: Wed, 28 Jun 2017 05:21:13 -0000 On Wednesday 28 June 2017 12:37:13 AM Chris Stewart via bitcoin-dev wrote: > BRIBEVERIFY redefines the existing NOP4 opcode. When executed, if the given > critical hash is included at the given vout index in the coinbase > transaction > the script evaluates to true. Otherwise, the script will fail. > > This allows sidechains to be merged mined against > bitcoin without burdening bitcoin miners with extra resource requirements. I don't see how. It seems like the logical outcome from this is "whoever pays the most gets the next sidechain block"... That's not particularly useful for merge mining. > This enables sidechains in Bitcoin. There are different kinds of sidechains... Federated peg: this already works on Bitcoin. SPV/SNARK peg: this isn't enabled by your BIP. Drivechains: this isn't enabled by your BIP. How do you say this enables any kind of sidechain? > A new block rule is added which requires that the miner's coinbase reward > be at index 0 in the coinbase transaction's output vector. > > It also fixes the witness commitment output to be at index 1 of the > coinbase transaction's output vector. This is unacceptable, for reasons Greg already pointed out. > This document is placed in the public domain. Note that this is not acceptable for BIPs anymore. https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#BIP_licensing