Andreas Schildbach [ARCHIVE] on Nostr: 📅 Original date posted:2015-08-29 📝 Original message:On 08/29/2015 06:31 PM, ...
📅 Original date posted:2015-08-29
📝 Original message: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
Published at
2023-06-07 17:38:26Event JSON
{
"id": "37dffcc7c159f1789f04cde0f41813379072789a9ccb08bab0510edf7f7c03f5",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686159506,
"kind": 1,
"tags": [
[
"e",
"7cc8d14173d1f56e3744d772d4d70152d07a99a0b5f93142926f4b2f8204351e",
"",
"root"
],
[
"e",
"6dc4a9225d9ca9ed6484927a88b37f509d929e63210e6d91da29bbdabb003011",
"",
"reply"
],
[
"p",
"1981fc26b3575cfe0cdafd51e1cac49a0eda39ffb00379f4981e2e4bc5aeb2c5"
]
],
"content": "📅 Original date posted:2015-08-29\n📝 Original message:On 08/29/2015 06:31 PM, Richard Moore via bitcoin-dev wrote:\n\n\u003e I like the idea of having a standard for this, that all explorers (and\n\u003e even core, eventually) would understand.\n\u003e \n\u003e I would recommend 2 changes though. First, using a real URI scheme,\n\u003e blockchain:// so that we can just use normal URL parsing libraries. The\n\u003e bitcoin: thing leads to additional code to mutate it into a proper URI\n\u003e before passing it to URL parsing. And I think it would be fine to\n\u003e include the type looking up. For example:\n\u003e \n\u003e blockchain://blockhash/00000000000000001003e880d500968d51157f210c632e08a652af3576600198\n\u003e blockchain://txid/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e blockchain://block/189000\n\u003e blockchain://address/1RicMooMWxqKczuRCa5D2dnJaUEn9ZJyn\n\nGood thinking! It might make sense to look at the existing de-facto\nstandard (e.g. blockexplorer.com, blockchain.info):\n\n/tx/ for transactions\n/block/ for blocks, supports both hash or height\n/address/ for address",
"sig": "366b8c16a358e571442e4b3cb0b2c8dfc547b2690fef3fca1adb3c846a6a362d90d93bf5210966622bbb36554cb80f0cdc4988298afcbade0dc1309c3b8cc2d3"
}