馃搮 Original date posted:2015-08-29
馃摑 Original message:That's still not right, since "mainnet" and "testnet" are not host names.
You'd have to do something like:
blockchain:?network=testnet&txid=3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
On Saturday, 29 August 2015, at 7:58 pm, Btc Drak via bitcoin-dev wrote:
> What about supporting different networks? What if I want to look up
> testnet for example?
>
> blockchain://mainnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
> blockchain://testnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
>
> or
>
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
> blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a?network=testnet
>
> On Sat, Aug 29, 2015 at 5:31 PM, Richard Moore via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> 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
> >
> > I think this would help the URI be more human understandable as well as give
> > the explorers the ability to optimize a bit what they are looking for when
> > hitting various databases.
> >
> > A possible future path could also include blockchain://tx/123000/4 for block
> > height, tx index... Another possibility could be blockchain://version which
> > would return a list of supported paths, version of the BIP supported, etc.
> >
> > The BIP should also specify little endian searching. I'm not sure, but would
> > it also make sense for this BIP to include what the return results should
> > look like? Maybe another, related BIP.
> >
> > RicMoo
> >
> > Sent from my self-aware iPhone
> >
> > .路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂><(((潞>
> >
> > Richard Moore ~ Founder
> > Genetic Mistakes Software Inc.
> > phone: (778) 882-6125
> > email: ricmoo at geneticmistakes.com
> > www: http://GeneticMistakes.com
> >
> > On Aug 29, 2015, at 7:48 AM, Marco Pontello via bitcoin-dev
> > <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >
> > Hi!
> > My first post here, hope I'm following the right conventions.
> > I had this humble idea for a while, so I thought to go ahead and propose
> > it.
> >
> > BIP: XX
> > Title: URI scheme for Blockchain exploration
> > Author: Marco Pontello
> > Status: Draft
> > Type: Standards Track
> > Created: 29 August 2015
> >
> > Abstract
> > ========
> > This BIP propose a simple URI scheme for looking up blocks, transactions,
> > addresses on a Blockchain explorer.
> >
> > Motivation
> > ==========
> > 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).
> >
> > Currently a Bitcoin client usually point to an arbitrary blockchain
> > explorer when the user look for the details of a transaction (es. Bitcoin
> > Wallet use BitEasy, Mycelium or Electrum use Blockchain.info, etc.).
> > Other times resorting to cut&paste is needed.
> > The same happens with posts and messages that reference some particular
> > txs or blocks, if they provide links at all.
> >
> > Specification
> > =============
> > The URI follow this simple form:
> >
> > blockchain: <hash/string>
> >
> > Examples:
> >
> > blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3576600198
> > blockchain:001949
> > blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
> >
> > Rationale
> > =========
> > I thought about using some more complex scheme, or adding qualifiers to
> > distinguish blocks from txs, but in the end I think that keeping it simple
> > should be practical enough. Blockchain explorers can apply the same
> > disambiguation rules they are already using to process the usual search
> > box.
> >
> > From the point of view of a wallet developer (or other tool 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.
> >
> > 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.
> >
> > 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.
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
Matt Whitlock [ARCHIVE] /
npub17q鈥pwet
2023-06-07 17:38:27
in reply to nevent1q鈥74u
Author Public Key
npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwetPublished at
2023-06-07 17:38:27Event JSON
{
"id": "721aebc937c07eab2a7aa0f487c6a588f4cfbccd5be2dba357f3abcc9cc8bae9",
"pubkey": "f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91",
"created_at": 1686159507,
"kind": 1,
"tags": [
[
"e",
"7cc8d14173d1f56e3744d772d4d70152d07a99a0b5f93142926f4b2f8204351e",
"",
"root"
],
[
"e",
"9cfd2c1975abb5ac7318259062876f14e749a9ee30b0e6b667a212e7d9805717",
"",
"reply"
],
[
"p",
"fdf31024ca0537ed828d895ddc8525f8af023f0dc935a8327a8a496d0d7a9f83"
]
],
"content": "馃搮 Original date posted:2015-08-29\n馃摑 Original message:That's still not right, since \"mainnet\" and \"testnet\" are not host names.\n\nYou'd have to do something like:\n\nblockchain:?network=testnet\u0026txid=3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\n\nOn Saturday, 29 August 2015, at 7:58 pm, Btc Drak via bitcoin-dev wrote:\n\u003e What about supporting different networks? What if I want to look up\n\u003e testnet for example?\n\u003e \n\u003e blockchain://mainnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e blockchain://testnet/txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e \n\u003e or\n\u003e \n\u003e blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a?network=testnet\n\u003e \n\u003e On Sat, Aug 29, 2015 at 5:31 PM, Richard Moore via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e I like the idea of having a standard for this, that all explorers (and even\n\u003e \u003e core, eventually) would understand.\n\u003e \u003e\n\u003e \u003e I would recommend 2 changes though. First, using a real URI scheme,\n\u003e \u003e blockchain:// so that we can just use normal URL parsing libraries. The\n\u003e \u003e bitcoin: thing leads to additional code to mutate it into a proper URI\n\u003e \u003e before passing it to URL parsing. And I think it would be fine to include\n\u003e \u003e the type looking up. For example:\n\u003e \u003e\n\u003e \u003e blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a652af3576600198\n\u003e \u003e blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e \u003e blockchain://block/189000\n\u003e \u003e blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn\n\u003e \u003e\n\u003e \u003e I think this would help the URI be more human understandable as well as give\n\u003e \u003e the explorers the ability to optimize a bit what they are looking for when\n\u003e \u003e hitting various databases.\n\u003e \u003e\n\u003e \u003e A possible future path could also include blockchain://tx/123000/4 for block\n\u003e \u003e height, tx index... Another possibility could be blockchain://version which\n\u003e \u003e would return a list of supported paths, version of the BIP supported, etc.\n\u003e \u003e\n\u003e \u003e The BIP should also specify little endian searching. I'm not sure, but would\n\u003e \u003e it also make sense for this BIP to include what the return results should\n\u003e \u003e look like? Maybe another, related BIP.\n\u003e \u003e\n\u003e \u003e RicMoo\n\u003e \u003e\n\u003e \u003e Sent from my self-aware iPhone\n\u003e \u003e\n\u003e \u003e .路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂\u003e\u003c(((潞\u003e\n\u003e \u003e\n\u003e \u003e Richard Moore ~ Founder\n\u003e \u003e Genetic Mistakes Software Inc.\n\u003e \u003e phone: (778) 882-6125\n\u003e \u003e email: ricmoo at geneticmistakes.com\n\u003e \u003e www: http://GeneticMistakes.com\n\u003e \u003e\n\u003e \u003e On Aug 29, 2015, at 7:48 AM, Marco Pontello via bitcoin-dev\n\u003e \u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\n\u003e \u003e Hi!\n\u003e \u003e My first post here, hope I'm following the right conventions.\n\u003e \u003e I had this humble idea for a while, so I thought to go ahead and propose\n\u003e \u003e it.\n\u003e \u003e\n\u003e \u003e BIP: XX\n\u003e \u003e Title: URI scheme for Blockchain exploration\n\u003e \u003e Author: Marco Pontello\n\u003e \u003e Status: Draft\n\u003e \u003e Type: Standards Track\n\u003e \u003e Created: 29 August 2015\n\u003e \u003e\n\u003e \u003e Abstract\n\u003e \u003e ========\n\u003e \u003e This BIP propose a simple URI scheme for looking up blocks, transactions,\n\u003e \u003e addresses on a Blockchain explorer.\n\u003e \u003e\n\u003e \u003e Motivation\n\u003e \u003e ==========\n\u003e \u003e The purpose of this URI scheme is to enable users to handle all the\n\u003e \u003e requests for details about blocks, transactions, etc. with their preferred\n\u003e \u003e tool (being that a web service or a local application).\n\u003e \u003e\n\u003e \u003e Currently a Bitcoin client usually point to an arbitrary blockchain\n\u003e \u003e explorer when the user look for the details of a transaction (es. Bitcoin\n\u003e \u003e Wallet use BitEasy, Mycelium or Electrum use Blockchain.info, etc.).\n\u003e \u003e Other times resorting to cut\u0026paste is needed.\n\u003e \u003e The same happens with posts and messages that reference some particular\n\u003e \u003e txs or blocks, if they provide links at all.\n\u003e \u003e\n\u003e \u003e Specification\n\u003e \u003e =============\n\u003e \u003e The URI follow this simple form:\n\u003e \u003e\n\u003e \u003e blockchain: \u003chash/string\u003e\n\u003e \u003e\n\u003e \u003e Examples:\n\u003e \u003e\n\u003e \u003e blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3576600198\n\u003e \u003e blockchain:001949\n\u003e \u003e blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e \u003e\n\u003e \u003e Rationale\n\u003e \u003e =========\n\u003e \u003e I thought about using some more complex scheme, or adding qualifiers to\n\u003e \u003e distinguish blocks from txs, but in the end I think that keeping it simple\n\u003e \u003e should be practical enough. Blockchain explorers can apply the same\n\u003e \u003e disambiguation rules they are already using to process the usual search\n\u003e \u003e box.\n\u003e \u003e\n\u003e \u003e From the point of view of a wallet developer (or other tool that need to\n\u003e \u003e show any kind of Blockchain references), using this scheme mean that he\n\u003e \u003e can simply make it a blockchain: link and be done with it, without having\n\u003e \u003e to worry about any specific Blockchain explorer or provide a means for the\n\u003e \u003e user to select one.\n\u003e \u003e\n\u003e \u003e Blockchain explorers in turn will simply offer to handle the blockchain:\n\u003e \u003e URI, the first time the user visit their website, or launch/install the\n\u003e \u003e application, or even set themselves if there isn't already one.\n\u003e \u003e\n\u003e \u003e Users get the convenience of using always their preferred explorer, which\n\u003e \u003e can be especially handy on mobile devices, where juggling with cut\u0026paste\n\u003e \u003e is far from ideal.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "d37ec3e72b6b410933beb094b9723525588184d38158db41cd84032fb16753ff996f352ac918e8a59da89c396c693bdebcd50029286691763ccb2976e5aa9007"
}