From: Emil Engler <me@emilengler•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address'
Date: Sat, 5 Oct 2019 23:57:48 +0200 [thread overview]
Message-ID: <58e44347-6eee-a0c3-3b8a-965c7450780e@emilengler.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
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
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.
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
* ...
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
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3199 bytes --]
next reply other threads:[~2019-10-05 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 21:57 Emil Engler [this message]
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
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=58e44347-6eee-a0c3-3b8a-965c7450780e@emilengler.com \
--to=me@emilengler$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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