From: =?utf-8?Q?JOSE_FEMENIAS_CA=C3=91UELO?= <jose.femenias@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_025DF0D6-DB30-42E3-8984-87352D208DB7"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Sun, 11 Jun 2017 22:05:24 +0200
Message-Id: <FD96E80B-A6ED-436D-876D-423A3C3E7566@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Bitcoin pointers
Precedence: list


--Apple-Mail=_025DF0D6-DB30-42E3-8984-87352D208DB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

I=E2=80=99ve been doing some work lately to create a specification for =
bitcoin pointers.=20

They can be used to point to transactions, inputs, outputs or some =
internal items within them.
The proposals strive for simplicity and user friendliness over =
compactness or other attributes.

There are three proposals, each of which builds upon the previous one, =
namely:

a) Canonical Pointers
The basic proposal.They look like this example: btc@170.1/179-631-520
Here is a link to the Google Docs document ->  =
https://docs.google.com/document/d/1PBN4wKFYtgvDxV4DrWUdNe9Xqmb8GVxoIGDKRk=
Y9Xr4/edit?usp=3Dsharing =
<https://docs.google.com/document/d/1PBN4wKFYtgvDxV4DrWUdNe9Xqmb8GVxoIGDKR=
kY9Xr4/edit?usp=3Dsharing>

b) Mnemonic Pointers=20
They build on Canonical Pointers and the dictionary provided in bip39 to =
use words instead of numbers.=20
The previous Canonical pointer can thus be expressed as btc@best.ability =
<mailto:btc@best.ability>/biology-exclude-donate
Here is a link to the Google Docs document ->  =
https://docs.google.com/document/d/1wLK2_UrRzK0eshkDntUIbVlIdswzuHmYNELOeP=
DjtPY/edit?usp=3Dsharing =
<https://docs.google.com/document/d/1wLK2_UrRzK0eshkDntUIbVlIdswzuHmYNELOe=
PDjtPY/edit?usp=3Dsharing>

c) Domain Pointers=20
They build on the Domain Name Registration system to encode a pointer to =
a Canonical Pointer as in btc@example.com <mailto:btc@example.com>
Here is a link to the Google Docs document -> =
https://docs.google.com/document/d/1KY7rM090oKzGn8NAz4XFxQnfkyD5gs4V6vpbfd=
w92RM/edit?usp=3Dsharing =
<https://docs.google.com/document/d/1KY7rM090oKzGn8NAz4XFxQnfkyD5gs4V6vpbf=
dw92RM/edit?usp=3Dsharing>

I haven=E2=80=99t had any peer review yet, so it is very likely that =
some small or big problems can be found.=20

I=E2=80=99d welcome any feedback from the community.

Best regards,


Jos=C3=A9 Femen=C3=ADas Ca=C3=B1uelo=

--Apple-Mail=_025DF0D6-DB30-42E3-8984-87352D208DB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi,<div class=3D""><br class=3D""></div><div class=3D"">I=E2=80=
=99ve been doing some work lately to create a specification for bitcoin =
pointers.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">They can be used to point to transactions, inputs, outputs or =
some internal items within them.</div><div class=3D"">The proposals =
strive for simplicity and user friendliness over compactness or other =
attributes.</div><div class=3D""><br class=3D""></div><div =
class=3D"">There are three proposals, each of which builds upon the =
previous one, namely:</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">a)&nbsp;<b class=3D"">Canonical =
Pointers</b></div><div class=3D"">The basic proposal.They look like this =
example:&nbsp;<b class=3D"">btc@170.1/179-631-520</b></div><div =
class=3D"">Here is a link to the Google Docs document -&gt; &nbsp;<a =
href=3D"https://docs.google.com/document/d/1PBN4wKFYtgvDxV4DrWUdNe9Xqmb8GV=
xoIGDKRkY9Xr4/edit?usp=3Dsharing" =
class=3D"">https://docs.google.com/document/d/1PBN4wKFYtgvDxV4DrWUdNe9Xqmb=
8GVxoIGDKRkY9Xr4/edit?usp=3Dsharing</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">b)&nbsp;<b class=3D"">Mnemonic =
Pointers&nbsp;</b></div><div class=3D"">They build on Canonical Pointers =
and the dictionary provided in bip39 to use words instead of =
numbers.&nbsp;</div><div class=3D"">The previous Canonical pointer can =
thus be expressed as&nbsp;<b class=3D""><a =
href=3D"mailto:btc@best.ability" =
class=3D"">btc@best.ability</a>/biology-exclude-donate</b></div><div =
class=3D"">Here is a link to the Google Docs document -&gt; &nbsp;<a =
href=3D"https://docs.google.com/document/d/1wLK2_UrRzK0eshkDntUIbVlIdswzuH=
mYNELOePDjtPY/edit?usp=3Dsharing" =
class=3D"">https://docs.google.com/document/d/1wLK2_UrRzK0eshkDntUIbVlIdsw=
zuHmYNELOePDjtPY/edit?usp=3Dsharing</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">c)&nbsp;<b class=3D"">Domain =
Pointers&nbsp;</b></div><div class=3D"">They build on the Domain Name =
Registration system to encode a pointer to a Canonical Pointer as =
in&nbsp;<a href=3D"mailto:btc@example.com" =
class=3D"">btc@example.com</a></div><div class=3D"">Here is a link to =
the Google Docs document -&gt;&nbsp;<a =
href=3D"https://docs.google.com/document/d/1KY7rM090oKzGn8NAz4XFxQnfkyD5gs=
4V6vpbfdw92RM/edit?usp=3Dsharing" =
class=3D"">https://docs.google.com/document/d/1KY7rM090oKzGn8NAz4XFxQnfkyD=
5gs4V6vpbfdw92RM/edit?usp=3Dsharing</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">I haven=E2=80=99t had any peer review =
yet, so it is very likely that some small or big problems can be =
found.&nbsp;</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">I=E2=80=99d welcome any feedback from the =
community.</div><div class=3D""><br class=3D""></div><div class=3D"">Best =
regards,</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Jos=C3=A9 Femen=C3=ADas =
Ca=C3=B1uelo</div></body></html>=

--Apple-Mail=_025DF0D6-DB30-42E3-8984-87352D208DB7--