From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8E6EC516 for ; Sun, 11 Jun 2017 20:05:33 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wr0-f180.google.com (mail-wr0-f180.google.com [209.85.128.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 804BE8C for ; Sun, 11 Jun 2017 20:05:29 +0000 (UTC) Received: by mail-wr0-f180.google.com with SMTP id v111so76841172wrc.3 for ; Sun, 11 Jun 2017 13:05:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:subject:message-id:to; bh=1b4LI/RLRntuVS2mldb33uq8PnGSHLg+M4l3BLGe9v4=; b=uMAqhniY5OVL/hmM+BbVBGPjbaDNt5CAqg6njsnf53L4elvuJn7tUNatxw0dKKWB18 E9P+gNJq9z0WEqOeVJ4uuJXb6/sH5PxHcounzIc02G2SxmByhxzkZNp4FgAEuzCyWpW4 9Yyzsevlbeln1+tYgUXEeyBnOayd8alRBBgNGq0ctH2vCsme4ov+OHnHlcKiL3n/17Os PvRs4FVWrN+o8c9mwFMT55QgPA4O0ovHLyUlZBFbGmOAa67xrXQ1lODs5AKl44v2bu+V mpWI06jJl7rOfpXsQ44ey+9SgcxljJEZbCvtyUz7dVZtj7Mx9sbavh9WmVu7o4Sb6/2D SnVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:subject:message-id:to; bh=1b4LI/RLRntuVS2mldb33uq8PnGSHLg+M4l3BLGe9v4=; b=eJweGEiBf5ngX+l00zDGEUl1gXyw7uzWHKwDVPvNh7KzVz654ttZkGR3e7dOCcXuv5 3yZYXUrFsbxyhkqXEhUxxtDmgWz9hGyAu8jJt7sGgA/Nc/d8siYmc3S6CS6Cf8dmsm/e 1W3CCp4bDcn7/Dt8bm8KsoI/FeJX9xWhdeo/vk2uY5+/mACIHBsph7S0KtmzS4yDXPkJ xzCLPaYuEOIkyyIMndTdgzO0k5EtmgJhL0owavzHnRDnfPt0zLJ0ULhMSqRYKGjyQla2 rGeYXo07LMQOV/svQb0edkC7J2JB9xdC29jt94y8jduJi6bpJYRxsdMgruCm9sURH8uh 9YIw== X-Gm-Message-State: AODbwcB/QMIxhRiJojdeNFk1rqfmKp7XyUsWmSpawnsJ7WG20O+0wBJr g1GwuO6yShxR6uy1nHk= X-Received: by 10.28.40.198 with SMTP id o189mr5709825wmo.102.1497211526759; Sun, 11 Jun 2017 13:05:26 -0700 (PDT) Received: from [192.168.1.43] ([178.60.38.49]) by smtp.gmail.com with ESMTPSA id a128sm8550802wmh.8.2017.06.11.13.05.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Jun 2017 13:05:25 -0700 (PDT) From: =?utf-8?Q?JOSE_FEMENIAS_CA=C3=91UELO?= 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: To: bitcoin-dev@lists.linuxfoundation.org X-Mailer: Apple Mail (2.3259) X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sun, 11 Jun 2017 20:08:03 +0000 Subject: [bitcoin-dev] Bitcoin pointers X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jun 2017 20:05:33 -0000 --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 = 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 = /biology-exclude-donate Here is a link to the Google Docs document -> = https://docs.google.com/document/d/1wLK2_UrRzK0eshkDntUIbVlIdswzuHmYNELOeP= DjtPY/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 Here is a link to the Google Docs document -> = https://docs.google.com/document/d/1KY7rM090oKzGn8NAz4XFxQnfkyD5gs4V6vpbfd= w92RM/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 Hi,

I=E2=80= =99ve 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

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/biology-exclude-donate

c) Domain = Pointers 
They build on the Domain Name = Registration system to encode a pointer to a Canonical Pointer as = in btc@example.com

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

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--