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 ) id 1V7BX1-0006Gl-CN for bitcoin-development@lists.sourceforge.net; Wed, 07 Aug 2013 21:44:35 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f181.google.com; Received: from mail-ob0-f181.google.com ([209.85.214.181]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V7BX0-0005gx-MB for bitcoin-development@lists.sourceforge.net; Wed, 07 Aug 2013 21:44:35 +0000 Received: by mail-ob0-f181.google.com with SMTP id dn14so4465806obc.40 for ; Wed, 07 Aug 2013 14:44:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.71.38 with SMTP id r6mr4089248obu.64.1375911869247; Wed, 07 Aug 2013 14:44:29 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.84.231 with HTTP; Wed, 7 Aug 2013 14:44:29 -0700 (PDT) In-Reply-To: References: Date: Wed, 7 Aug 2013 23:44:29 +0200 X-Google-Sender-Auth: KFELl0zwTyQ4WamLMtG3NCDKBGQ Message-ID: From: Mike Hearn To: Pieter Wuille Content-Type: multipart/alternative; boundary=e89a8fb1f56c357a3704e36272d2 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: 1V7BX0-0005gx-MB Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 21:44:35 -0000 --e89a8fb1f56c357a3704e36272d2 Content-Type: text/plain; charset=UTF-8 > My concerns here are: > * Making sure wallet applications can function without supporting the > P2P protocol (which drops a huge implementation overhead for simple - > perhaps hardware-based - wallets) How would such wallets get transactions into their wallet in the first place? The P2P protocol is really the simplest part of implementing a wallet, IMO. I don't really have a strong opinion either way, but doing more work to prevent transactions being announced to the network feels weird. --e89a8fb1f56c357a3704e36272d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
My concerns here are:
* Making sure wallet applications can function without supporting the
P2P protocol (which drops a huge implementation overhead for simple -
perhaps hardware-based - wallets)
=C2=A0
How wou= ld such wallets get transactions into their wallet in the first place?

The P2P protocol is really the simplest part of implem= enting a wallet, IMO.=C2=A0

I don't really have a strong opinion either way, bu= t doing more work to prevent transactions being announced to the network fe= els weird.=C2=A0

--e89a8fb1f56c357a3704e36272d2--