Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XCS9y-00073H-Og for bitcoin-development@lists.sourceforge.net; Wed, 30 Jul 2014 11:35:06 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.218.48 as permitted sender) client-ip=209.85.218.48; envelope-from=mh.in.england@gmail.com; helo=mail-oi0-f48.google.com; Received: from mail-oi0-f48.google.com ([209.85.218.48]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XCS9x-0008GD-Rq for bitcoin-development@lists.sourceforge.net; Wed, 30 Jul 2014 11:35:06 +0000 Received: by mail-oi0-f48.google.com with SMTP id h136so744931oig.21 for ; Wed, 30 Jul 2014 04:35:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.144.161 with SMTP id sn1mr4838022obb.82.1406720099952; Wed, 30 Jul 2014 04:34:59 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Wed, 30 Jul 2014 04:34:59 -0700 (PDT) In-Reply-To: References: <5E988ED7-845D-4982-9240-155AACD20F66@coinqy.com> Date: Wed, 30 Jul 2014 13:34:59 +0200 X-Google-Sender-Auth: VukSwGonIAwhEt8NiINBg20MoUg Message-ID: From: Mike Hearn To: Mark van Cuijk Content-Type: multipart/alternative; boundary=089e0158ac78db4dc304ff678bff 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: 1XCS9x-0008GD-Rq Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] "On behalf of" BIP 70 extension proposal 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, 30 Jul 2014 11:35:06 -0000 --089e0158ac78db4dc304ff678bff Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That would definitely be a new BIP. But firstly it'd make sense to implement it and make sure that the payment processors intend to use it. Like I said, I wasn't very successful so far in getting them to make useful memo fields. I'm hoping that once wallets start actually recording and displaying the memo in their transactions list that will change. On Wed, Jul 30, 2014 at 9:54 AM, Mark van Cuijk wrote: > On 28 Jul 2014, at 15:32 , Mike Hearn wrote: > > > So what now? To be honest my next priority with BIP70 was to formalise > the extensions process, I've been dragging my feet over that because I'm > working on other things. And then after that to knock some heads together > over at BitPay/Coinbase and get them to put useful text in the memo field > instead of random numbers. Baby steps .... > > I can probably pick up writing the proposal. > > However, I=E2=80=99m not sure what process to follow. Should I format the= proposal > as a new BIP or should it become part of BIP.70? How does the extensions > process you=E2=80=99re working on going to describe the process? --089e0158ac78db4dc304ff678bff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That would definitely be a new BIP.

But= firstly it'd make sense to implement it and make sure that the payment= processors intend to use it. Like I said, I wasn't very successful so = far in getting them to make useful memo fields. I'm hoping that once wa= llets start actually recording and displaying the memo in their transaction= s list that will change.


On Wed,= Jul 30, 2014 at 9:54 AM, Mark van Cuijk <mark@coinqy.com> wro= te:
On 28 Jul 2014, at 15:32 , M= ike Hearn <mike@plan99.net> wr= ote:

> So what now? To be honest my next priority with BIP70 was to formalise= the extensions process, I've been dragging my feet over that because I= 'm working on other things. And then after that to knock some heads tog= ether over at BitPay/Coinbase and get them to put useful text in the memo f= ield instead of random numbers. Baby steps ....

I can probably pick up writing the proposal.

However, I=E2=80=99m not sure what process to follow. Should I format the p= roposal as a new BIP or should it become part of BIP.70? How does the exten= sions process you=E2=80=99re working on going to describe the process?

--089e0158ac78db4dc304ff678bff--