MIME-Version: 1.0
References: <58e44347-6eee-a0c3-3b8a-965c7450780e@emilengler.com>
	<6fe67006-7131-a861-61fa-65392d5be069@riseup.net>
	<20824fa5-e3fa-8d4e-1678-4c2048b49b6b@emilengler.com>
In-Reply-To: <20824fa5-e3fa-8d4e-1678-4c2048b49b6b@emilengler.com>
From: Lloyd Fournier <lloyd.fourn@gmail.com>
Date: Fri, 11 Oct 2019 12:13:40 +1100
Message-ID: <CAH5Bsr2mtec+QT3wmnoSkRPwuHu2_4qn4zysqChkpFdaeqP1Cg@mail.gmail.com>
To: Emil Engler via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000009fb740594983c90"
Subject: Re: [bitcoin-dev] BIPable-idea: Consistent and better definition of
 the term 'address'
Precedence: list

--00000000000009fb740594983c90
Content-Type: text/plain; charset="UTF-8"

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
>

--00000000000009fb740594983c90
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Thread,<div><br></div><div>This may not be the most pra=
ctical information, but there actually did exist an almost perfect analogy =
for Bitcoin addresses from the ancient world: From wikipedia=C2=A0<a href=
=3D"https://en.wikipedia.org/wiki/Bulla_(seal)">https://en.wikipedia.org/wi=
ki/Bulla_(seal)</a></div><div><br></div><div><span style=3D"font-family:san=
s-serif;font-size:14px">&quot;Transactions for trading needed to be account=
ed 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 bull=
a before it dried, to insure trust that the tokens hadn&#39;t been tampered=
 with and for anyone to know what exactly was in the bulla without having t=
o break it.&quot;</span></div><div><br></div><div>You could only use the bu=
lla once because it had to be destroyed in order to get the tokens out! I t=
hink there are even examples of bulla with a kind of &quot;signature&quot; =
on them (an imprint with the seal of a noble family etc).</div><div><br></d=
iv><div>&quot;send me a Bitcoin bulla&quot; has a nice ring to it!</div><di=
v><br></div><div>Sincerely,</div><div><br></div><div>LL</div><div><br></div=
><div><br></div><div><span style=3D"font-family:sans-serif;font-size:14px">=
<br></span></div><div><span style=3D"font-family:sans-serif;font-size:14px"=
><br></span></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, Oct 11, 2019 at 2:44 AM Emil Engler via bitcoin-d=
ev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev=
@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">* Sorry if this mail was sent multiple times, my =
E-Mail client went crazy *<br>
<br>
Thanks for all your feedback.<br>
I came to the decision to write a BIP for this, even if it might not be<br>
implemented by many wallets, a standardization is never wrong and this<br>
would be the first step in the correct direction for better on-chain<br>
privacy.<br>
<br>
However currently we still need a good term for the &#39;address&#39; repla=
cement.<br>
<br>
The current suggestions are:<br>
* Invoice ID<br>
* Payment Token<br>
* Bitcoin invoice (address)<br>
* Bitcoin invoice (path)<br>
<br>
Because of the LN term invoice I really like the term &#39;Bitcoin Invoice&=
#39;<br>
by Chris Belcher.<br>
<br>
So how do find a consensus about these terms?<br>
<br>
Greetings<br>
Emil Engler<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--00000000000009fb740594983c90--