summaryrefslogtreecommitdiff
path: root/a3/627c52f196c590eb22f6520c507585b670994a
blob: da00c779d04e9d1f564aa9e70c44429c3457d099 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
Return-Path: <adam.back@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 142578DC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 28 Jun 2017 05:28:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com
	[209.85.220.176])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AF499223
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 28 Jun 2017 05:28:32 +0000 (UTC)
Received: by mail-qk0-f176.google.com with SMTP id r62so42537945qkf.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 27 Jun 2017 22:28:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:reply-to:in-reply-to:references:from:date:message-id
	:subject:to:cc;
	bh=qWn4iTC3MwQYf/R77andUU3T4xCtK2RivrwQOo2UkPU=;
	b=NjWKrHq66xYmQGU0ardoXVMb/tZVq0Ck/rmv22x9istQ8HWr4NDN8VRPkmfIXmwXYC
	437hfvWGQYh4hTp1jLhoxHH/iLmhSjv0ZdfZEyKve3q4UwJdb6gx3W0sOyFD+okeLs5Z
	9mCxYMKUgmmZeB/OcSmY7/4bAZB7Z0jaIZ1OAIl/dcIJe9ukBL2iwYazW/XJXLYhehgl
	2wf8Y2fleXCxcmgu4IcqLCwS3H7eKzRZepLLw7uY2RaoHx2XJm43mfLOFAaT+C31X1w5
	uUgmoMEj60t3CYEqyxjB6JlVhPtO3tmTwbENAWAELPyqreNR0lj62lOQ2zX1A6g57D4K
	H3xQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:reply-to:in-reply-to:references
	:from:date:message-id:subject:to:cc;
	bh=qWn4iTC3MwQYf/R77andUU3T4xCtK2RivrwQOo2UkPU=;
	b=In9QxZSSZcWwZ8Oh/K4wO5h5wNShTaWPVJBkJ2lIFqkgG4b9afEnFPkwJ1pEBgzQ8H
	lXgRDRgM7ih8Sg1Z9ajZZYcvpnbSTUBwuPIc4tcbsxWpYMyCEGg4rmSC7vYdQcgTNj1a
	LKml7miw1ZT0GgzI7oKjAJNW0FyarP+tgAfkhQADUSN4oSvgn06xLTYTFCRExCRhnJxS
	OrXpdhq0mifyGXdxVeJ+LLBZgExhXj4FmGDCCCxyZGPCi5WXLKAEjzy+RDX1S8uZJy3y
	ErDfeMOvSyUP/n7si8cK6UJt0eJJT45QC6BX996ryNFxlhdp7gV7iCg0yv1KHfF9/cux
	5udw==
X-Gm-Message-State: AKS2vOxAzsNHZsbcs7aOhj0amIwCWX3+qAJgi5oV318XcaYFQN0NXpUT
	lhJfT1KJrcvZvVo7kchFvjGq3pFYQQ==
X-Received: by 10.55.75.204 with SMTP id y195mr11082419qka.183.1498627711889; 
	Tue, 27 Jun 2017 22:28:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.66 with HTTP; Tue, 27 Jun 2017 22:28:31 -0700 (PDT)
Reply-To: adam@cypherspace.org
In-Reply-To: <201706280520.29105.luke@dashjr.org>
References: <CAGL6+mHQ_vMc2JYVqwfP89WOZdUF2WDtWfh7ccL1PQve=nC+zQ@mail.gmail.com>
	<201706280520.29105.luke@dashjr.org>
From: Adam Back <adam.back@gmail.com>
Date: Tue, 27 Jun 2017 22:28:31 -0700
Message-ID: <CALqxMTE7jXdnXvsXoyTqTv6m1xQDQXCXsu7mh3oHmw8aXhrB0w@mail.gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jun 2017 05:28:33 -0000

On 27 June 2017 at 22:20, Luke Dashjr via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.

Maybe that's phrased badly but the point of the "blind merge mining"
is just that the sidechain fees are paid in main chain bitcoin (rather
than in sidechain bitcoin).

That means that a miner who solo mines the main chain could still mine
the sidechain by requesting a block-proposal from a trusted sidechain
fullnode.  The sidechain fullnode would actually pay the mainchain
fee, and pay itself the sidechain fees as part of the side-chain
block-proposal.

This was viewed as less centralising than forcing miners to directly
process sidechain blocks, which could in principle be bandwidth and
CPU expensive to process, construct and validate.

Adam