From: "JOSE FEMENIAS CAÑUELO" <jose.femenias@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Bitcoin pointers
Date: Sun, 11 Jun 2017 22:05:24 +0200 [thread overview]
Message-ID: <FD96E80B-A6ED-436D-876D-423A3C3E7566@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
Hi,
I’ve been doing some work lately to create a specification for bitcoin pointers.
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/1PBN4wKFYtgvDxV4DrWUdNe9Xqmb8GVxoIGDKRkY9Xr4/edit?usp=sharing <https://docs.google.com/document/d/1PBN4wKFYtgvDxV4DrWUdNe9Xqmb8GVxoIGDKRkY9Xr4/edit?usp=sharing>
b) Mnemonic Pointers
They build on Canonical Pointers and the dictionary provided in bip39 to use words instead of numbers.
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_UrRzK0eshkDntUIbVlIdswzuHmYNELOePDjtPY/edit?usp=sharing <https://docs.google.com/document/d/1wLK2_UrRzK0eshkDntUIbVlIdswzuHmYNELOePDjtPY/edit?usp=sharing>
c) Domain Pointers
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/1KY7rM090oKzGn8NAz4XFxQnfkyD5gs4V6vpbfdw92RM/edit?usp=sharing <https://docs.google.com/document/d/1KY7rM090oKzGn8NAz4XFxQnfkyD5gs4V6vpbfdw92RM/edit?usp=sharing>
I haven’t had any peer review yet, so it is very likely that some small or big problems can be found.
I’d welcome any feedback from the community.
Best regards,
José Femenías Cañuelo
[-- Attachment #2: Type: text/html, Size: 2975 bytes --]
next reply other threads:[~2017-06-11 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 20:05 JOSE FEMENIAS CAÑUELO [this message]
2017-06-11 20:19 ` Jonas Schnelli
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=FD96E80B-A6ED-436D-876D-423A3C3E7566@gmail.com \
--to=jose.femenias@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