From: Mike Hearn <mike@plan99•net>
To: Gmail <will.yager@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Date: Wed, 25 Jun 2014 10:25:43 +0200 [thread overview]
Message-ID: <CANEZrP0ce4MMX2hOhcGVWt23L_CMn6Cmj9_Okqd0BR9seQXJew@mail.gmail.com> (raw)
In-Reply-To: <C95DB811-9E6A-4EA2-AE8F-83595C3AC817@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
>
> I agree. It would be even sillier to start specifying container formats
> for random one-off "that would be kind of nice, I guess" features.
>
No, it'd be sensible.
Here's a list I drew up a long time ago of features I imagined adding to
the payment protocol:
https://bitcointalk.org/index.php?topic=270055.msg2890147#msg2890147
The protocol is there to contain features! There is zero benefit to
slavishly following some religious notion of purity or minimalism here. The
shared resource in question is just varint encoded integers. So, we should
be guided by what will help our users and what will help adoption.
Anyway, Gavin asked me to start handling more BIP 70 stuff a few weeks ago.
I want to use something simple to set up the extensions process more
formally. IMO we need a "living document" version of the payment protocol
with all the different extensions out there folded into it, to simplify
programming tasks and ensure field numbers don't collide.
[-- Attachment #2: Type: text/html, Size: 1490 bytes --]
next prev parent reply other threads:[~2014-06-25 8:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:27 Mike Hearn
2014-06-24 14:21 ` Jeff Garzik
2014-06-24 14:24 ` Mike Hearn
2014-06-24 14:32 ` slush
2014-06-24 15:06 ` Mike Hearn
2014-06-24 15:15 ` Gmail
2014-06-24 15:48 ` Jeff Garzik
2014-06-24 19:00 ` Gmail
2014-06-24 19:34 ` Andy Alness
2014-06-24 20:12 ` Gavin Andresen
2014-06-24 20:28 ` Gmail
2014-06-25 8:25 ` Mike Hearn [this message]
2014-06-25 13:33 ` Jorge Timón
2014-06-25 18:10 ` Jeff Garzik
2014-06-25 14:15 ` slush
2014-06-25 16:03 ` Gmail
2014-06-24 18:34 ` Roy Badami
2014-06-24 15:43 ` Andreas Schildbach
2014-06-24 15:59 ` Mike Hearn
2014-06-24 17:37 ` Drak
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=CANEZrP0ce4MMX2hOhcGVWt23L_CMn6Cmj9_Okqd0BR9seQXJew@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=will.yager@gmail$(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