public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Emil Engler <me@emilengler.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address'
Date: Thu, 10 Oct 2019 17:05:36 +0200	[thread overview]
Message-ID: <20824fa5-e3fa-8d4e-1678-4c2048b49b6b@emilengler.com> (raw)
In-Reply-To: <6fe67006-7131-a861-61fa-65392d5be069@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

* Sorry if this mail was sent multiple times, my E-Mail client went crazy *

Thanks for all your feedback.
I came to the decision to write a BIP for this, even if it might not be
implemented by many wallets, a standardization is never wrong and this
would be the first step in the correct direction for better on-chain
privacy.

However currently we still need a good term for the 'address' replacement.

The current suggestions are:
* Invoice ID
* Payment Token
* Bitcoin invoice (address)
* Bitcoin invoice (path)

Because of the LN term invoice I really like the term 'Bitcoin Invoice'
by Chris Belcher.

So how do find a consensus about these terms?

Greetings
Emil Engler

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3199 bytes --]

  reply	other threads:[~2019-10-10 15:05 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 [this message]
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
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=20824fa5-e3fa-8d4e-1678-4c2048b49b6b@emilengler.com \
    --to=me@emilengler.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