From: Emil Engler <me@emilengler•com>
To: Luke Dashjr <luke@dashjr•org>, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address'
Date: Sun, 6 Oct 2019 18:06:27 +0200 [thread overview]
Message-ID: <ea664ec6-4485-d925-ada1-d302d6f81eb1@emilengler.com> (raw)
In-Reply-To: <201910061132.39215.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
> But a pubkey is not a Base58 string, and fundamentally different from an
> address. An address identifies the recipient and the purpose of the payment;
> a pubkey does not. The pubkey remains with the UTXO; an address does not.
I don't know much about this topic in Bitcoin so far, but I meant the
address :)
> That problem would require using a different term than "address" to address.
I meant this the whole time, sorry for misunderstandings.
> A BIP is unlikely to do the job (though it may help).
Why? They are specifications and implementations need them (even if some
do not implement everything).
Also BIP 21 would need an alternative/separate parameter with the new term.
> Neither the address nor pubkey are a password...
In Germany at least (where I live), you need to provide a 'Password'
(the german translation of thin word of course) in the purpose of the
transaction if you pay with a bank transfer. They are used as IDs but I
agree, ID is definitely a better suffix.
> Some possible alternative terms would be "invoice id", "payment token", etc.
ACK
Greetings, Emil Engler
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3199 bytes --]
next prev parent reply other threads:[~2019-10-06 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 21:57 Emil Engler
2019-10-06 11:32 ` Luke Dashjr
2019-10-06 16:06 ` Emil Engler [this message]
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
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=ea664ec6-4485-d925-ada1-d302d6f81eb1@emilengler.com \
--to=me@emilengler$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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