From: Lloyd Fournier <lloyd.fourn@gmail•com>
To: Emil Engler via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPable-idea: Consistent and better definition of the term 'address'
Date: Fri, 11 Oct 2019 12:13:40 +1100 [thread overview]
Message-ID: <CAH5Bsr2mtec+QT3wmnoSkRPwuHu2_4qn4zysqChkpFdaeqP1Cg@mail.gmail.com> (raw)
In-Reply-To: <20824fa5-e3fa-8d4e-1678-4c2048b49b6b@emilengler.com>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
Hi Thread,
This may not be the most practical information, but there actually did
exist an almost perfect analogy for Bitcoin addresses from the ancient
world: From wikipedia https://en.wikipedia.org/wiki/Bulla_(seal)
"Transactions for trading needed to be accounted for efficiently, so the
clay tokens were placed in a clay ball (bulla), which helped with
dishonesty and kept all the tokens together. In order to account for the
tokens, the bulla would have to be crushed to reveal their content. This
introduced the idea of impressing the token onto the wet bulla before it
dried, to insure trust that the tokens hadn't been tampered with and for
anyone to know what exactly was in the bulla without having to break it."
You could only use the bulla once because it had to be destroyed in order
to get the tokens out! I think there are even examples of bulla with a kind
of "signature" on them (an imprint with the seal of a noble family etc).
"send me a Bitcoin bulla" has a nice ring to it!
Sincerely,
LL
On Fri, Oct 11, 2019 at 2:44 AM Emil Engler via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> * 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3081 bytes --]
next prev parent reply other threads:[~2019-10-11 1:14 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
2019-10-09 19:32 ` Chris Belcher
2019-10-10 15:05 ` Emil Engler
2019-10-11 1:13 ` Lloyd Fournier [this message]
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=CAH5Bsr2mtec+QT3wmnoSkRPwuHu2_4qn4zysqChkpFdaeqP1Cg@mail.gmail.com \
--to=lloyd.fourn@gmail$(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