From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Emil Engler <me@emilengler•com>
Subject: Re: [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address'
Date: Sun, 6 Oct 2019 11:32:33 +0000 [thread overview]
Message-ID: <201910061132.39215.luke@dashjr.org> (raw)
In-Reply-To: <58e44347-6eee-a0c3-3b8a-965c7450780e@emilengler.com>
On Saturday 05 October 2019 21:57:48 Emil Engler via bitcoin-dev wrote:
> Hello dear mailing list subscribers.
> Before I'll explain my idea here, I need to define a term first
>
> 'address':
> When I use the terms address, pubkey, etc., I mean the same: The Base58
> string
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.
> Ok now let's get into it:
> As you should know, sending bitcoins to an address more than once is a
> very bad approach.
> In my opinion the problem why so many people are still doing this is
> because of the term 'address' which is used in lots of wallets,
> implementations, BIP 21 and so on. It is a design issue.
> With the term 'address' most people identify things that are fixed and
> don't change really often (e.g postal address, IP address [depends on
> provider], Domain, E-Mail address, ...).
> Because of this most people compare bitcoin addresses with e-mail
> addresses and use this address to send the recipient money multiple times.
That problem would require using a different term than "address" to address.
A BIP is unlikely to do the job (though it may help).
> My suggestion would be to change the term address in wallets, the URI
> scheme and so on to something of the following options by a
> Informational/Process BIP:
>
> * Payment Password
> * Transaction Password
> * ...
Neither the address nor pubkey are a password...
Some possible alternative terms would be "invoice id", "payment token", etc.
> The guideline for the term should indicate that it is:
> * temporary
> * Something that identifies the recipient
>
> I've chosen 'password' because they can be used as a pseudonym to
> identify a person.
> This is already used in stuff like bank transfers where something like
> the transaction id should be used as the purpose or at universities
> there are student numbers.
> The first is probably a better example because student numbers aren't
> temporary.
>
> What do you think? Should I write a BIP for this or use another term?
> Feedback is most welcome :)
>
> Greetings,
> Emil Engler
next prev parent reply other threads:[~2019-10-06 11:39 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 [this message]
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
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=201910061132.39215.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=me@emilengler$(echo .)com \
/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