From mboxrd@z Thu Jan  1 00:00:00 1970
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 1We6We-0006KC-IZ
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Apr 2014 17:36:32 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.173 as permitted sender)
	client-ip=209.85.214.173; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f173.google.com; 
Received: from mail-ob0-f173.google.com ([209.85.214.173])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1We6Wd-0007HT-OA
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Apr 2014 17:36:32 +0000
Received: by mail-ob0-f173.google.com with SMTP id wn1so5682122obc.32
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 26 Apr 2014 10:36:26 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.40.201 with SMTP id z9mr12982919obk.45.1398533786416;
	Sat, 26 Apr 2014 10:36:26 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Sat, 26 Apr 2014 10:36:26 -0700 (PDT)
In-Reply-To: <CABsx9T3boaWYuY8S-Xz=bAxe+ne5iP7m8AnuciaAOmDx_3D4Fg@mail.gmail.com>
References: <535ABD5D.7070509@jrn.me.uk>
	<CABsx9T3boaWYuY8S-Xz=bAxe+ne5iP7m8AnuciaAOmDx_3D4Fg@mail.gmail.com>
Date: Sat, 26 Apr 2014 19:36:26 +0200
X-Google-Sender-Auth: ZSC5W48vqZb6KSqjIcEspksITaI
Message-ID: <CANEZrP3TuN2LFi3_7z29JncojbOZX=C-1BsJMp1AJ56k8wjgBg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c33b028bbc4b04f7f58582
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: 1We6Wd-0007HT-OA
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Error handling in payment protocol
 (BIP-0070 and BIP-0072)
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: Sat, 26 Apr 2014 17:36:32 -0000

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

>
> PaymentRequests are limited to 50,000 bytes. I can't think of a reason why
> Payment messages would need to be any bigger than that. Submit a pull
> request to the existing BIP.
>

In future it might be nice to have images and things in the payment
requests, to make UIs look prettier. But with the current version 50kb
should be plenty indeed.

--001a11c33b028bbc4b04f7f58582
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"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">
<div class=3D""><div>PaymentRequests are limited to 50,000 bytes. I can&#39=
;t think of a reason why Payment messages would need to be any bigger than =
that. Submit a pull request to the existing BIP.</div></div></div></div></d=
iv>
</blockquote><div><br></div><div>In future it might be nice to have images =
and things in the payment requests, to make UIs look prettier. But with the=
 current version 50kb should be plenty indeed.=C2=A0</div></div></div></div=
>

--001a11c33b028bbc4b04f7f58582--