From: "David A. Harding" <dave@dtrt.org>
To: Karel Kyovsky <karel.kyovsky@generalbytes.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Travel rule, VASP UID and bitcoin URI - A new BIP
Date: Fri, 16 Jul 2021 11:42:16 -1000 [thread overview]
Message-ID: <20210716214216.mtc6h55ahopxt32q@ganymede> (raw)
In-Reply-To: <CALSqm3bG0pYhPvGQd-uxN5fTQXS_rbzQFq3L5+d2xbaLUuCE3Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Fri, Jul 16, 2021 at 04:35:21PM +0200, Karel Kyovsky via bitcoin-dev wrote:
> I would like to propose a standardization of [a new] bitcoin URI parameter name
> [...]
> My question is: Should I prepare a completely new BIP or should I prepare a
> modification of BIP21?
Please use a new BIP. See BIP72 for a previous instance where another
URI parameter for BIP21 was standardized.
https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki
(I think your compliance situation is mostly off topic for this list, so
I'm not commenting on that.)
-Dave
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-07-16 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 14:35 [bitcoin-dev] Travel rule, VASP UID and bitcoin URI - A new BIP Karel Kyovsky
2021-07-16 21:42 ` David A. Harding [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=20210716214216.mtc6h55ahopxt32q@ganymede \
--to=dave@dtrt.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=karel.kyovsky@generalbytes.com \
/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