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
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
Return-Path: <voisine@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 205D2ABF
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 19:40:35 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com
[209.85.192.52])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 87683126
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 19:40:34 +0000 (UTC)
Received: by qgal13 with SMTP id l13so43684996qga.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 12:40:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=s7zmcKkKeHdJZvlDFEAaqxpeZtT5vZKSSieBzrYItRY=;
b=Pye7+vA0IqresgIgNgiauUfqOcrNUuPdJL1c+BEua6cMdtPBTaCDaZ3uEzv7WUXspD
BrkmnPq4NOkYJ4s5m4iM3V6PT8TxY9Ia8v/Cq4yeWjiN5+1oUkRK8kRDRgA9GRK9xLXq
nZ30D2LgZFpmeNNMeyuiOpGFf1bv8P7USPinIofc7hJUtVTymxwhKAD1WZZy0z3LlsUG
ixsxz7NlJrXHFHlzkWbiC83uPtyZzGyhmm2UlWXZDX7cijBv6SnwWjvU5vrhsitb65CB
1k2p/S0EFgJwEDSflmO4A2rrbb6IZWSxOsVQyq8f8vsfA9/Iq0MCZbH8zfelHtRRjKqY
gu6Q==
MIME-Version: 1.0
X-Received: by 10.55.49.134 with SMTP id x128mr17018780qkx.49.1435434033787;
Sat, 27 Jun 2015 12:40:33 -0700 (PDT)
Received: by 10.140.91.37 with HTTP; Sat, 27 Jun 2015 12:40:33 -0700 (PDT)
In-Reply-To: <9BD77EB3-8EC7-4207-8E90-98E48C8365DE@petertodd.org>
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>
<CADm_Wca+ow4pMzN7SyKjsMdFo0wuUerYYjf5xKs5G_2Q2PzMmA@mail.gmail.com>
<CAPg+sBg=sn7djO_8H16NDg7S7m7_0eTcrgLVofMWQ2ANz+jw9w@mail.gmail.com>
<CADm_WcbQog_UCV=JPHyqTRxKbaGY7jedtHE_D8jJSe_thMg05w@mail.gmail.com>
<CAPg+sBhrBUSfPdMjbLthLEFD17zBC3LoWf9LvZsOD1Vp0D78BQ@mail.gmail.com>
<558DA56F.3010703@jrn.me.uk> <20150626193630.GB17829@muck>
<558E3EFD.9040602@ktorn.com>
<CACq0ZD5S6dDcBh9fsHCgbPJXom4vF8VymtHXogODjfD38RDNfA@mail.gmail.com>
<9BD77EB3-8EC7-4207-8E90-98E48C8365DE@petertodd.org>
Date: Sat, 27 Jun 2015 12:40:33 -0700
Message-ID: <CACq0ZD4_xfVidPtjqaXbC7XiamAG71z85GPhhu4qv39H3VwKXg@mail.gmail.com>
From: Aaron Voisine <voisine@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=001a1147ff42aebb3605198507af
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Sat, 27 Jun 2015 19:40:35 -0000
--001a1147ff42aebb3605198507af
Content-Type: text/plain; charset=UTF-8
On Sat, Jun 27, 2015 at 8:13 AM, Peter Todd <pete@petertodd.org> wrote:
> On 27 June 2015 03:14:41 GMT-04:00, Aaron Voisine <voisine@gmail.com>
> wrote:
> >Also remember that the sender is not the one who cares about delays or
> >even
> >getting confirmations at all, it's the receiver who's concerned with
> >these
> >things. They have to tell the sender up-front what they're willing to
> >accept in exchange for goods and services.
>
> You're assuming a receiver who is accepting a zeroconf transaction; most
> receivers don't.
>
> For instance, when I deposit funds on my exchange they don't credit those
> funds until 4 confirmations, so I very much cafe about how long it takes to
> get the first confirmation.
>
Yes, the receiver can tell the sender up-front that they are only willing
accept 4-confirmations, and put that on the sender to figure out, but the
sender then only cares because it's the receiver's requirement. The
receiver is the one who cares.
--001a1147ff42aebb3605198507af
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Sat, Jun 27, 2015 at 8:13 AM, Peter Todd <span dir=3D"ltr"><<a href=
=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@petertodd.org</a>>=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 27 Jun=
e 2015 03:14:41 GMT-04:00, Aaron Voisine <<a href=3D"mailto:voisine@gmai=
l.com">voisine@gmail.com</a>> wrote:<br>
>Also remember that the sender is not the one who cares about delays or<=
br>
>even<br>
>getting confirmations at all, it's the receiver who's concerned=
with<br>
>these<br>
>things. They have to tell the sender up-front what they're willing =
to<br>
>accept in exchange for goods and services.<br>
<br>
</span>You're assuming a receiver who is accepting a zeroconf transacti=
on; most receivers don't.<br>
<br>
For instance, when I deposit funds on my exchange they don't credit tho=
se funds until 4 confirmations, so I very much cafe about how long it takes=
to get the first confirmation.<br></blockquote><div><br></div><div>Yes, th=
e receiver can tell the sender up-front that they are only willing accept 4=
-confirmations, and put that on the sender to figure out, but the sender th=
en only cares because it's the receiver's requirement. The receiver=
is the one who cares.=C2=A0</div></div></div></div>
--001a1147ff42aebb3605198507af--
|
