From: vv01f <vv01f@c3d2.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP for segwit compatibility URIs
Date: Thu, 18 Oct 2018 18:52:49 +0200 [thread overview]
Message-ID: <871627c9-8679-5f82-a76f-cec9ffa28379@c3d2.de> (raw)
In-Reply-To: <CAHGSxGuqf2vKOWtW-_hfdqfsH8a_QTaWBsrUViV8A39dk1KA6A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 624 bytes --]
I already pointed out a while ago that the separator could be the & and
the returning value is either an address or an array of addresses.
So no comma or other delimiter needed.
also I would suggest to call the parameter `address` and not a shortcut
for it as we are used to `message` and `amount` spelled out as well.
On 18.10.2018 16:20, Clark Moody via bitcoin-dev wrote:
> Since we don't know what sort of address changes will happen later on, you
> could make this future-proof by passing a list of addresses to `addr`.
>
> The syntax is
>
> bitcoin:<address>[?addr=<address>[,<address>[,<address>]]]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2018-10-18 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 19:52 [bitcoin-dev] BIP for segwit compatibility URIs Srintuar
2018-10-18 14:20 ` Clark Moody
2018-10-18 16:52 ` vv01f [this message]
2018-10-18 22:27 ` Clark Moody
2018-10-18 23:58 ` Srintuar
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=871627c9-8679-5f82-a76f-cec9ffa28379@c3d2.de \
--to=vv01f@c3d2.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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