|
10 | 10 |
|
11 | 11 | ==Abstract==
|
12 | 12 |
|
13 |
| -This BIP propose an URI scheme for looking up blocks, transactions, addresses on a Blockchain explorer, or in general to make proper Blockchain references |
| 13 | +This BIP proposes a URI scheme for looking up blocks, transactions and addresses on a Blockchain explorer, or in general to make proper Blockchain references. |
14 | 14 |
|
15 | 15 | ==Motivation==
|
16 | 16 |
|
17 | 17 | The purpose of this URI scheme is to enable users to handle all the requests for details about blocks, transactions, etc. with their preferred tool (being that a web service or a local application).
|
18 |
| -Currently a Bitcoin client usually points to an arbitrary blockchain explorer when the user looks for the details of a transaction, or let him choose from a limited list of possible alternatives. |
19 |
| -Other times resorting to cut&paste is needed. |
| 18 | +Currently a Bitcoin client usually points to an arbitrary blockchain explorer when the user looks for the details of a transaction or allows the user to choose from a set of alternatives. |
| 19 | +Resorting to copy + paste into a browser is often required. |
20 | 20 | The same happens with posts and messages that reference some particular txs or blocks, if they provide links at all.
|
21 | 21 |
|
22 | 22 | ==Specification==
|
|
30 | 30 | {| class="wikitable"
|
31 | 31 | ! style="text-align: center;" | Element
|
32 | 32 | ! colspan="2" style="text-align: center;" | Description
|
33 |
| -! |
| 33 | +! Required? |
34 | 34 | |-
|
35 | 35 | | chain
|
36 | 36 | | colspan="2" | '''chain ID''' (see below) of the desired chain, leading 0s included. If omitted (which would be the usual case), Bitcoin main net is assumed.
|
|
39 | 39 | | rowspan="3" | type
|
40 | 40 | | tx
|
41 | 41 | | for transactions.
|
42 |
| -| rowspan="3" | |
| 42 | +| rowspan="3" | required |
43 | 43 | |-
|
44 | 44 | | block
|
45 | 45 | | for blocks (supports both hash or height).
|
|
49 | 49 | |-
|
50 | 50 | | hash
|
51 | 51 | | colspan="2" | the relevant hash to refer to (leading zeros included), or block height.
|
52 |
| -| |
| 52 | +| required |
53 | 53 | |}
|
54 | 54 |
|
55 | 55 | ====ABNF grammar====
|
@@ -104,20 +104,20 @@ A transaction on Bitcoin test net:
|
104 | 104 |
|
105 | 105 | ==Rationale==
|
106 | 106 |
|
107 |
| -From the point of view of a wallet (or other Blockchain related tool) developer that need to show any kind of Blockchain references, using this scheme mean that he can simply make it a blockchain: link and be done with it, without having to worry about any specific Blockchain explorer or provide a means for the user to select one. |
| 107 | +From the point of view of a wallet (or other Blockchain related tool) developers which need to reference Blockchain data, using this scheme mean that he can simply make it a `blockchain:` link without having to worry about any specific Blockchain explorer or provide a means for the user to select one. |
108 | 108 |
|
109 |
| -Blockchain explorers in turn will simply offer to handle the blockchain: URI, the first time the user visit their website, or launch/install the application, or even set themselves if there isn't already one. |
| 109 | +Blockchain explorers in turn will simply offer to handle the `blockchain:` URI schema, the first time the user visit their website, or launch/install the application, or even set themselves if there isn't already one. |
110 | 110 |
|
111 |
| -Users get the convenience of using always their preferred explorer, which can be especially handy on mobile devices, where juggling with cut&paste is far from ideal. |
| 111 | +Users can link directly to their preferred block explorer (avoiding copy + paste which can be awkward on mobile devices). |
112 | 112 |
|
113 | 113 | == Sample implementation ==
|
114 | 114 |
|
115 | 115 | [https://github.com/MarcoPon/blockchain-exploration Demo Blockchain: URI handler on GitHub]
|
116 | 116 |
|
117 | 117 | ==Acknowledgements==
|
118 |
| -Thanks to Btc Drak for suggesting to provide support for different networks. |
119 |
| -Thanks to Jorge Timon for the idea of using genesis blocks hashes to identify them. |
120 |
| -Thanks to Richard Moore, Matt Whitlock, Andreas Schildbach for suggestions about the structure and hierarchy of the URI scheme. |
| 118 | + |
| 119 | +Thanks to Btc Drak for suggesting support for different networks and Jorge Timon for the suggestion that we could identify each network by its genesis block hash. |
| 120 | +Thanks to Richard Moore, Matt Whitlock, Andreas Schildbach for help with the structure and hierarchy of the URI scheme. |
121 | 121 |
|
122 | 122 | ==Copyright==
|
123 | 123 |
|
|
0 commit comments