From: CryptAxe <cryptaxe@gmail.com>
To: Sjors Provoost <sjors@sprovoost.nl>
Cc: Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
Matt Corallo <matt@chaincode.com>
Subject: Re: [bitcoin-dev] BIP-21 amendment proposal: -no125
Date: Tue, 5 Dec 2017 12:06:31 -0800 [thread overview]
Message-ID: <CAF5CFkiVD6gUzmJbNGaJShMD3h5mq-RmUkBJEx61Eg6ie7=0MQ@mail.gmail.com> (raw)
In-Reply-To: <FD79573C-4771-464B-A570-E2868BBA0CA5@sprovoost.nl>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
On Dec 5, 2017 12:00 PM, "Sjors Provoost" <sjors@sprovoost.nl> wrote:
...
I don't think all BIPs lend themselves to this pattern. Can you think of
another example?
Not right now, just seemed like a good idea to consider making it useful
for more than one thing (maybe CT or something else could use it in the
future?).
I also suspect each ignored flag requires carefully defined behavior, so
it's probably better to spell that out in the BIP.
Sjors
Agreed, no reason they couldn't reuse the same section of the payment
request URI though. (And define that behavior in the BIP)
[-- Attachment #2: Type: text/html, Size: 1733 bytes --]
next prev parent reply other threads:[~2017-12-05 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 19:24 [bitcoin-dev] BIP-21 amendment proposal: -no125 Sjors Provoost
2017-12-05 19:39 ` Luke Dashjr
2017-12-05 20:00 ` Sjors Provoost
2017-12-05 20:06 ` CryptAxe [this message]
2017-12-11 18:19 ` Peter Todd
2017-12-23 16:25 ` Matt Corallo
2017-12-23 18:33 ` Paul Iverson
2017-12-05 19:40 ` CryptAxe
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='CAF5CFkiVD6gUzmJbNGaJShMD3h5mq-RmUkBJEx61Eg6ie7=0MQ@mail.gmail.com' \
--to=cryptaxe@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=matt@chaincode.com \
--cc=sjors@sprovoost.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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