From: Mike Hearn <mike@plan99•net>
To: Mark van Cuijk <mark@coinqy•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] "On behalf of" BIP 70 extension proposal
Date: Wed, 30 Jul 2014 13:34:59 +0200 [thread overview]
Message-ID: <CANEZrP3FR4woBMV-Zp84CUJjT-bZweanWTJZgy5BCJY-tO-Tzg@mail.gmail.com> (raw)
In-Reply-To: <BCE1032B-A181-4A07-B04A-CAFFE975DE5A@coinqy.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
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 <mark@coinqy•com> wrote:
> On 28 Jul 2014, at 15:32 , Mike Hearn <mike@plan99•net> 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’m 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’re working on going to describe the process?
[-- Attachment #2: Type: text/html, Size: 1528 bytes --]
prev parent reply other threads:[~2014-07-30 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 6:55 Mark van Cuijk
2014-07-27 19:31 ` Mike Hearn
2014-07-28 9:01 ` Mark van Cuijk
2014-07-28 12:46 ` Mike Hearn
2014-07-28 13:06 ` Mark van Cuijk
2014-07-28 13:32 ` Mike Hearn
2014-07-30 7:54 ` Mark van Cuijk
2014-07-30 11:34 ` Mike Hearn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP3FR4woBMV-Zp84CUJjT-bZweanWTJZgy5BCJY-tO-Tzg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mark@coinqy$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox