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
|
Return-Path: <yanmaani@cock.li>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 623A2C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Apr 2021 01:23:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 4385460758
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Apr 2021 01:23:17 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 1.391
X-Spam-Level: *
X-Spam-Status: No, score=1.391 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RDNS_NONE=0.793,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=cock.li
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 514-TsMqt8T8
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Apr 2021 01:23:15 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail.cock.li (unknown [37.120.193.123])
by smtp3.osuosl.org (Postfix) with ESMTPS id A25E060731
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Apr 2021 01:23:15 +0000 (UTC)
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cock.li; s=mail;
t=1618881793; bh=2ysf8sO/yCim8RArEzTc/GtQ/hhAhbyhXNOCnWKytho=;
h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
b=N+fSVmICq43Mhjg1FVt1bGTCHqy7KQjQ/xE3YSAObpEkjERm+G6fZXo+I2YWieA5m
6uIkhJqBdtcezlki5wUlTYOcxjYd0IVRz8Q6s1SFTWoKZaftpg50PZm5kGNvQri0jT
imnY7twt8B2TdUBJkdyU50EjN47LOBE7EzbEySjMAVPCqiJuVK3TGlVKdUwlK20aVj
7LquXEihYzsTChqG/I0VjCCBZNw2+kS5hAVm2K/0Txqb375SbtXSGPuoHRRNIJx5cV
VDV1Y2whENnafvkbLxg/6fry9m/wNRI1xEkJB64wVnMXU3MfhLvxYJXn8pxafwsSfu
/m6pyBvLM8LOQ==
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 20 Apr 2021 01:23:12 +0000
From: yanmaani@cock.li
To: Ruben Somsen <rsomsen@gmail.com>, Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <CAPv7Tja=4ZFm5+gHw+wMcZyPEqeQiVx-AjyXsRn0T8a+tXHb1A@mail.gmail.com>
References: <CAK=nyAxOa8fsVfxucH7WTTMn25BCzgQ28h_sNsunedpCoRXjjQ@mail.gmail.com>
<CABE6yHscUPAcyK58DvqhOnxSOoPMBAy9aMUmReJYSkBit-Mekg@mail.gmail.com>
<CAPv7Tja=4ZFm5+gHw+wMcZyPEqeQiVx-AjyXsRn0T8a+tXHb1A@mail.gmail.com>
Message-ID: <050674b8bc51cff11e0a6e105880b647@cock.li>
X-Sender: yanmaani@cock.li
User-Agent: Roundcube Webmail/1.3.15
X-Mailman-Approved-At: Tue, 20 Apr 2021 02:28:44 +0000
Cc: christopher.gilliard@gmail.com
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Tue, 20 Apr 2021 01:23:17 -0000
> If only one hash is allowed per block, then those who wish to utilize
> the hash will have to out-bid each other ("fee-bidding"). This hash can
> then be used to create another chain ("merged-mining")
Merged mining at present only needs one hash for a merkle root, and
that's stored in the coinbase. It would be even simpler to add the
following rules:
1) No OP_RETURN transactions allowed at all
2) If you want to commit data, do so in that one transaction in the
coinbase
Also curious about how you'd handle the payment - do I need to put in a
transaction that burns bitcoins for the tx fee? That isn't free in terms
of storage either.
|
