MIME-Version: 1.0
In-Reply-To: <CAPg+sBgOt=qhQVZv5P-4mcD75=L4PKgOfRqhyB6FZdSYQajrwQ@mail.gmail.com>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
	<CAPg+sBgOt=qhQVZv5P-4mcD75=L4PKgOfRqhyB6FZdSYQajrwQ@mail.gmail.com>
From: Jim Phillips <jim@ergophobia.org>
Date: Fri, 7 Aug 2015 16:30:40 -0500
Message-ID: <CANe1mWyZ4fbvFyHZZzK63fWFeWH2yXkaUxOopaYKKCft-QVujQ@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f235739b90096051cbf5a08
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fees and the block-finding process
Precedence: list

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

On Fri, Aug 7, 2015 at 10:16 AM, Pieter Wuille via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
> But perhaps there is some "use" for ultra-low-priority unreliable
> transactions (... despite DoS attacks).
>

I can think of a variety of protocols that broadcast information and don't
really care about whether it gets delivered.. Think of everything that uses
UDP on TCP/IP. The most basic thing I can think of would be low-priority
notifications that are sent to the entire Bitcoin universe, but don't need
to persist. The protocol provides for a signed and thus verified message,
and a method for broadcasting it to every node that might be interested in
seeing it. If it never makes it into a block, so be it. If it does, so be
it.

--
*James G. Phillips IV*
<https://plus.google.com/u/0/113107039501292625391/posts>
<http://www.linkedin.com/in/ergophobe>

*"Don't bunt. Aim out of the ball park. Aim for the company of immortals."
-- David Ogilvy*

 *This message was created with 100% recycled electrons. Please think twice
before printing.*

--e89a8f235739b90096051cbf5a08
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Aug 7, 2015 at 10:16 AM, Pieter Wuille via bitcoin-dev <span dir=3D"ltr=
">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_b=
lank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><d=
iv class=3D"gmail_quote"><div>But perhaps there is some &quot;use&quot; for=
 ultra-low-priority unreliable transactions (... despite DoS attacks).</div=
></div></div></div></blockquote><div><br></div><div>I can think of a variet=
y of protocols that broadcast information and don&#39;t really care about w=
hether it gets delivered.. Think of everything that uses UDP on TCP/IP. The=
 most basic thing I can think of would be low-priority notifications that a=
re sent to the entire Bitcoin universe, but don&#39;t need to persist. The =
protocol provides for a signed and thus verified message, and a method for =
broadcasting it to every node that might be interested in seeing it. If it =
never makes it into a block, so be it. If it does, so be it.=C2=A0</div></d=
iv></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gm=
ail_signature"><div>--<div><b>James G. Phillips IV</b>=C2=A0<a href=3D"http=
s://plus.google.com/u/0/113107039501292625391/posts" target=3D"_blank" styl=
e=3D"font-size:x-small"><img src=3D"https://ssl.gstatic.com/images/icons/gp=
lus-16.png"></a>=C2=A0<a href=3D"http://www.linkedin.com/in/ergophobe" targ=
et=3D"_blank"><img src=3D"http://developer.linkedin.com/sites/default/files=
/LinkedIn_Logo16px.png"></a></div></div><div><font size=3D"1"><i>&quot;Don&=
#39;t bunt. Aim out of the ball park. Aim for the company of immortals.&quo=
t; -- David Ogilvy<br></i></font><div><font size=3D"1"><br></font></div></d=
iv><div><font size=3D"1"><img src=3D"http://findicons.com/files/icons/1156/=
fugue/16/leaf.png">=C2=A0<em style=3D"font-family:verdana,geneva,sans-serif=
;line-height:16px;color:green">This message was created with 100% recycled =
electrons. Please think twice before printing.</em></font></div></div></div=
><br></div></div>

--e89a8f235739b90096051cbf5a08--