summaryrefslogtreecommitdiff
path: root/50/6e34009255a066af3afa440b982ccc735bbb5f
blob: 0e13a460a16caf2495577098c69eb45f5220cdcf (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
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 <mh.in.england@gmail.com>) id 1WdLqK-0006o9-Dm
	for bitcoin-development@lists.sourceforge.net;
	Thu, 24 Apr 2014 15:45:44 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.172 as permitted sender)
	client-ip=209.85.214.172; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f172.google.com; 
Received: from mail-ob0-f172.google.com ([209.85.214.172])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WdLqI-0005G8-G3
	for bitcoin-development@lists.sourceforge.net;
	Thu, 24 Apr 2014 15:45:44 +0000
Received: by mail-ob0-f172.google.com with SMTP id wo20so2855823obc.17
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 24 Apr 2014 08:45:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.76.194 with SMTP id m2mr2071727oew.47.1398354337033; Thu,
	24 Apr 2014 08:45:37 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Thu, 24 Apr 2014 08:45:36 -0700 (PDT)
In-Reply-To: <CAC1+kJNTpHpG5EpRKj21PEy3z2iAouuH6Yiix8m20uji3b6Lgg@mail.gmail.com>
References: <CAC1+kJM3pSq8YfwbX167rQ0=0Y_hozRQ3pggDN524=LUfOdTqg@mail.gmail.com>
	<CANEZrP1f9WV-Mp9SGm4q88h82xxBnwqg8M7JJhnqGOHCWf65xg@mail.gmail.com>
	<CAB+qUq7=o05GgCNdTtH=cuW56qbjg5v0ZpxvCYmCPj1AvFui+g@mail.gmail.com>
	<CANEZrP0fjzuUKh0Jmk9c99ne81hdxZdTnhw6sq47Na7AC4n04A@mail.gmail.com>
	<CAC1+kJNTpHpG5EpRKj21PEy3z2iAouuH6Yiix8m20uji3b6Lgg@mail.gmail.com>
Date: Thu, 24 Apr 2014 17:45:36 +0200
X-Google-Sender-Auth: 5ISzL-dt6O4rNbeJslTwVM_lKnY
Message-ID: <CANEZrP2Bhq5+ECNoEgupsq3_0RfmDG+6KOxvffsOgqaRn9=_LA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@monetize.io>
Content-Type: multipart/alternative; boundary=047d7b33cea687779204f7cbbdb2
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WdLqI-0005G8-G3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0 confirmation txs using replace-by-fee
 and game theory
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: Thu, 24 Apr 2014 15:45:44 -0000

--047d7b33cea687779204f7cbbdb2
Content-Type: text/plain; charset=UTF-8

>
> Of course if we're not comparing this with Bitcoin today and we're
> comparing it to some theoretical mechanism for instant p2p
> serialization without requiring proof of work then, yes, this concept
> is not very interesting.
>

Bitcoin's competition is not some theoretical perfect p2p system but
rather, bank notes and credit cards.

--047d7b33cea687779204f7cbbdb2
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Of course if we&#39;re not comparing this with Bitcoin today and we&#39;re<br>

comparing it to some theoretical mechanism for instant p2p<br>
serialization without requiring proof of work then, yes, this concept<br>
is not very interesting.<br>
</blockquote></div><br></div><div class="gmail_extra">Bitcoin&#39;s competition is not some theoretical perfect p2p system but rather, bank notes and credit cards.</div></div>

--047d7b33cea687779204f7cbbdb2--