blob: a3f3d26087dcc525bbbb58ce8f989f9594293750 (
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <cryptocurrencies@quidecco.de>) id 1Y0X3K-0000D7-Bk
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Dec 2014 14:55:14 +0000
X-ACL-Warn:
Received: from quidecco.de ([81.169.136.15])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Y0X3J-00077U-5F
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Dec 2014 14:55:14 +0000
Received: from localhost (localhost [127.0.0.1])
by quidecco.de (Postfix) with SMTP id 54A06E23568;
Mon, 15 Dec 2014 15:55:06 +0100 (CET)
From: Isidor Zeuner <cryptocurrencies@quidecco.de>
To: patrick <patrick@intersango.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
References: <54880492.9060300@intersango.com> <54876653.4020403@certimix.com>
<548769FA.5040406@bluematt.me>
<CA+s+GJAe9MeO+Sr0+2BRwu3q-Be5JQt_s_xdnBBEcquXqOyxcA@mail.gmail.com>
<417518B4-1E4D-4467-BC87-95C9EAF0C599@bitsofproof.com>
In-Reply-To: <54880492.9060300@intersango.com>
Message-Id: <20141215145506.54A06E23568@quidecco.de>
Date: Mon, 15 Dec 2014 15:55:06 +0100 (CET)
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1Y0X3J-00077U-5F
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Merged mining a side chain with proof of
burn on parent chain
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 14:55:14 -0000
> The goal is to have an opportunity cost to breaking the rules.
>
> Proof of Burn is a real cost for following the rules.
>
For every participant who could try to decide about the adequateness
of the cost, no direct effect comes from the difference between Proof
of Burn, and approaches which keep the Bitcoins inside the set of
outputs that can still participate. So, any notion which
differentiates with respect to this must make some assumption about
what defines the interest of the Bitcoin nodes as a community.
Best regards,
Isidor
|
