MIME-Version: 1.0
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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
Precedence: list

--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">&lt;<a href=
=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@petertodd.org</a>&gt;=
</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 &lt;<a href=3D"mailto:voisine@gmai=
l.com">voisine@gmail.com</a>&gt; wrote:<br>
&gt;Also remember that the sender is not the one who cares about delays or<=
br>
&gt;even<br>
&gt;getting confirmations at all, it&#39;s the receiver who&#39;s concerned=
 with<br>
&gt;these<br>
&gt;things. They have to tell the sender up-front what they&#39;re willing =
to<br>
&gt;accept in exchange for goods and services.<br>
<br>
</span>You&#39;re assuming a receiver who is accepting a zeroconf transacti=
on; most receivers don&#39;t.<br>
<br>
For instance, when I deposit funds on my exchange they don&#39;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&#39;s the receiver&#39;s requirement. The receiver=
 is the one who cares.=C2=A0</div></div></div></div>

--001a1147ff42aebb3605198507af--