📅 Original date posted:2019-10-09
📝 Original message:This is an excellent idea and I hope something like this happens.
I've had the idea of using an intermediate name to make the transition
easier, for example "Bitcoin address" becomes "Bitcoin invoice address"
which after 10 years becomes "Bitcoin invoice" (or "Bitcoin invoice").
"Invoice" would also work well because Lightning uses the name invoice
for the object which is used to receive payments. So it's easy to
imagine that the GUI text input presented to users can be called
"invoice" and users can put both kinds of invoices there leaving the
wallet to easily figure out whether it makes an on-chain transaction or
a Lightning Network transaction.
Changing a commonly-used name like this could be very hard, but the
gains in terms of privacy are immense.
On 05/10/2019 22:57, 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
>
> 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
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Chris Belcher [ARCHIVE] /
npub1ek…lnm2u
2023-06-07 18:21:08
in reply to nevent1q…q8j0
Author Public Key
npub1ekvnqhww3aagwuj9t55dgj5y29u8cxdjllfv3vgppt8vc0zljhrs6lnm2uPublished at
2023-06-07 18:21:08Event JSON
{
"id": "0018d5f6cb527b113b288a951e0d4d35714c85a9408658b2ce7ce947b3ee49ad",
"pubkey": "cd99305dce8f7a8772455d28d44a8451787c19b2ffd2c8b1010acecc3c5f95c7",
"created_at": 1686162068,
"kind": 1,
"tags": [
[
"e",
"2ceb005983bccb8ed869797f1f19e941c30d02f7f4665d5fde474752d18fab44",
"",
"root"
],
[
"e",
"233dcc0c2058cb90c62ce0cda39d2b2821ad5addc47c9242032c94f41ec8b7aa",
"",
"reply"
],
[
"p",
"6020dca142bfa9e8b09e00fa64ed9b062c57b63ab8b04e05667e4f849475103f"
]
],
"content": "📅 Original date posted:2019-10-09\n📝 Original message:This is an excellent idea and I hope something like this happens.\n\nI've had the idea of using an intermediate name to make the transition\neasier, for example \"Bitcoin address\" becomes \"Bitcoin invoice address\"\nwhich after 10 years becomes \"Bitcoin invoice\" (or \"Bitcoin invoice\").\n\n\"Invoice\" would also work well because Lightning uses the name invoice\nfor the object which is used to receive payments. So it's easy to\nimagine that the GUI text input presented to users can be called\n\"invoice\" and users can put both kinds of invoices there leaving the\nwallet to easily figure out whether it makes an on-chain transaction or\na Lightning Network transaction.\n\nChanging a commonly-used name like this could be very hard, but the\ngains in terms of privacy are immense.\n\nOn 05/10/2019 22:57, Emil Engler via bitcoin-dev wrote:\n\u003e Hello dear mailing list subscribers.\n\u003e Before I'll explain my idea here, I need to define a term first\n\u003e \n\u003e 'address':\n\u003e When I use the terms address, pubkey, etc., I mean the same: The Base58\n\u003e string\n\u003e \n\u003e Ok now let's get into it:\n\u003e As you should know, sending bitcoins to an address more than once is a\n\u003e very bad approach.\n\u003e In my opinion the problem why so many people are still doing this is\n\u003e because of the term 'address' which is used in lots of wallets,\n\u003e implementations, BIP 21 and so on. It is a design issue.\n\u003e With the term 'address' most people identify things that are fixed and\n\u003e don't change really often (e.g postal address, IP address [depends on\n\u003e provider], Domain, E-Mail address, ...).\n\u003e Because of this most people compare bitcoin addresses with e-mail\n\u003e addresses and use this address to send the recipient money multiple times.\n\u003e \n\u003e My suggestion would be to change the term address in wallets, the URI\n\u003e scheme and so on to something of the following options by a\n\u003e Informational/Process BIP:\n\u003e \n\u003e * Payment Password\n\u003e * Transaction Password\n\u003e * ...\n\u003e \n\u003e The guideline for the term should indicate that it is:\n\u003e * temporary\n\u003e * Something that identifies the recipient\n\u003e \n\u003e I've chosen 'password' because they can be used as a pseudonym to\n\u003e identify a person.\n\u003e This is already used in stuff like bank transfers where something like\n\u003e the transaction id should be used as the purpose or at universities\n\u003e there are student numbers.\n\u003e The first is probably a better example because student numbers aren't\n\u003e temporary.\n\u003e \n\u003e What do you think? Should I write a BIP for this or use another term?\n\u003e Feedback is most welcome :)\n\u003e \n\u003e Greetings,\n\u003e Emil Engler\n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "439a3902e3e73bf632b4dbae3beb2a80f5360a25035bbae28fec54ae93c569c69da55699ef9775b3575a154173c3f4c65fcc12faf6e2c9eebd8a12f517e89ba9"
}