From: Marco Falke <falke.marco@gmail.com>
To: Emil Engler via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address'
Date: Thu, 17 Oct 2019 09:23:39 -0400 [thread overview]
Message-ID: <CAK51vgCpvLTMXwdrgSNaOMFAu25QuHkuXpwsaqK+92cq8NZiow@mail.gmail.com> (raw)
In-Reply-To: <a5c28fd3-4ffd-94f8-f80c-c55c202a3f2c@emilengler.com>
I also like the "bitcoin invoice address" term by Chris. Invoice is a
common term and easily translatable into other languages.
Marco
next prev parent reply other threads:[~2019-10-17 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 21:57 [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address' Emil Engler
2019-10-06 11:32 ` Luke Dashjr
2019-10-06 16:06 ` Emil Engler
2019-10-09 19:32 ` Chris Belcher
2019-10-10 15:05 ` Emil Engler
2019-10-11 1:13 ` Lloyd Fournier
2019-10-11 2:00 ` Karl-Johan Alm
2019-10-11 4:22 ` Ariel Lorenzo-Luaces
2019-10-11 21:03 ` Emil Engler
2019-10-17 13:23 ` Marco Falke [this message]
2019-10-17 19:28 ` Emil Engler
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=CAK51vgCpvLTMXwdrgSNaOMFAu25QuHkuXpwsaqK+92cq8NZiow@mail.gmail.com \
--to=falke.marco@gmail.com \
--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