From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Date: Sat, 29 Aug 2015 20:07:26 +0200 [thread overview]
Message-ID: <mrsscu$9oo$1@ger.gmane.org> (raw)
In-Reply-To: <CF21152C-15FA-421C-B369-A9A7DB59865F@ricmoo.com>
On 08/29/2015 06:31 PM, Richard Moore via bitcoin-dev wrote:
> I like the idea of having a standard for this, that all explorers (and
> even core, eventually) would understand.
>
> I would recommend 2 changes though. First, using a real URI scheme,
> blockchain:// so that we can just use normal URL parsing libraries. The
> bitcoin: thing leads to additional code to mutate it into a proper URI
> before passing it to URL parsing. And I think it would be fine to
> include the type looking up. For example:
>
> blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a652af3576600198
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
> blockchain://block/189000
> blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn
Good thinking! It might make sense to look at the existing de-facto
standard (e.g. blockexplorer.com, blockchain.info):
/tx/ for transactions
/block/ for blocks, supports both hash or height
/address/ for address
next prev parent reply other threads:[~2015-08-29 18:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 11:48 [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration Marco Pontello
2015-08-29 16:31 ` Richard Moore
2015-08-29 17:19 ` Matt Whitlock
2015-08-29 19:24 ` Richard Moore
2015-08-29 18:07 ` Andreas Schildbach [this message]
2015-09-01 14:33 ` Marco Pontello
2015-08-29 18:58 ` Btc Drak
2015-08-29 19:01 ` Matt Whitlock
2015-08-29 20:10 ` Jorge Timón
2015-08-30 2:02 ` Chun Wang
2015-08-30 2:20 ` Jorge Timón
2015-09-01 22:56 ` Btc Drak
2015-09-01 14:49 ` Marco Pontello
2015-09-01 21:16 ` Matt Whitlock
2015-09-01 21:25 ` Esteban Ordano
2015-09-01 21:38 ` Marco Pontello
2015-09-01 21:42 ` Matt Whitlock
2015-09-01 21:43 ` Marco Pontello
2015-09-01 22:46 ` Jorge Timón
2015-09-01 23:25 ` Matt Whitlock
2015-09-01 16:12 ` Danny Thorpe
2015-09-01 22:59 ` Btc Drak
2015-09-01 23:57 ` Jorge Timón
2015-08-29 19:28 ` Richard Moore
2015-09-01 14:51 ` Marco Pontello
2015-11-15 2:14 ` Marco Pontello
2015-11-15 11:42 ` Jorge Timón
2015-11-16 0:59 ` Marco Pontello
2015-11-16 14:43 ` Jorge Timón
2015-11-16 22:10 ` Marco Pontello
2015-11-18 11:29 ` Jorge Timón
2015-11-18 12:31 ` Marco Pontello
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='mrsscu$9oo$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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