From: Jonas Schnelli <dev@jonasschnelli.ch>
To: "JOSE FEMENIAS CAÑUELO" <jose.femenias@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin pointers
Date: Sun, 11 Jun 2017 22:19:20 +0200 [thread overview]
Message-ID: <F096F6D8-4091-43F8-AE7F-90D52417A7FE@jonasschnelli.ch> (raw)
In-Reply-To: <FD96E80B-A6ED-436D-876D-423A3C3E7566@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
Hi José
> 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>
A similar/related proposal got posted last month : https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014396.html <https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014396.html>
The Bech32 encoded transaction position reference allows to solve similar use cases (tx pointers) with a strong error-detection/correction using just 14 chars (encoded state, including error correction / unencoded 40bits).
/jonas
[-- Attachment #1.2: Type: text/html, Size: 1446 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-11 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 20:05 [bitcoin-dev] Bitcoin pointers JOSE FEMENIAS CAÑUELO
2017-06-11 20:19 ` Jonas Schnelli [this message]
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=F096F6D8-4091-43F8-AE7F-90D52417A7FE@jonasschnelli.ch \
--to=dev@jonasschnelli.ch \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jose.femenias@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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