📅 Original date posted:2015-09-01 📝 Original message:On Sat, Aug 29, 2015 at ...

Marco Pontello [ARCHIVE] /

npub12sr…dn3h

2023-06-07 17:39:07

in reply to nevent1q…lc37

📅 Original date posted:2015-09-01
📝 Original message:On Sat, Aug 29, 2015 at 10:10 PM, Jorge Timón <
bitcoin-dev at lists.linuxfoundation.org> wrote:

>
> I would really prefer chain=<chainID> over network=<chainPetnameStr>
> By chainID I mean the hash of the genesis block, see
>
> https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39
> I'm completely fine with doing that using an optional parameter (for
> backwards compatibility).
>

I see that using the genesis block hash would be the perfectly rigorous way
to do it, but what do you think about the possibility of letting also use
the name constants, as a simple / more relaxed alternative? That would
spare a source lookup just to write a correct reference to a tx, maybe in a
forum or a post.

So a reference to a certain tx could be either:

blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f

blockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

blockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=main

(or a different element name maybe)

--
Try the Online TrID File Identifier
http://mark0.net/onlinetrid.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150901/68c31b7b/attachment.html>;

Author Public Key

npub12srjs7mc5grqhm86mngax037h3v75wvx8tpd55cfhmkj6dagqxrqmwdn3h

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 17:39:07

Kind type

1 Short Text Note

Event JSON

{ "id": "e61201ee1026ab3fbd341a01edd7c6fac9de4f4865dddf65632099474910fecd", "pubkey": "5407287b78a2060becfadcd1d33e3ebc59ea39863ac2da5309beed2d37a80186", "created_at": 1686159547, "kind": 1, "tags": [ [ "e", "adae20868ecaee3485c1f73b7cbb076c6c1ffdd38a33c7ea438129dbb9aa31c8", "", "root" ], [ "e", "5caaaa26592e2ea6f1c9296ea25005f152825c46cb3de031bca2848d8bcbf013", "", "reply" ], [ "p", "5407287b78a2060becfadcd1d33e3ebc59ea39863ac2da5309beed2d37a80186" ] ], "content": "📅 Original date posted:2015-09-01\n📝 Original message:On Sat, Aug 29, 2015 at 10:10 PM, Jorge Timón \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e\n\u003e I would really prefer chain=\u003cchainID\u003e over network=\u003cchainPetnameStr\u003e\n\u003e By chainID I mean the hash of the genesis block, see\n\u003e\n\u003e https://github.com/jtimon/bitcoin/commit/3191d5e8e75687a27cf466b7a4c70bdc04809d39\n\u003e I'm completely fine with doing that using an optional parameter (for\n\u003e backwards compatibility).\n\u003e\n\nI see that using the genesis block hash would be the perfectly rigorous way\nto do it, but what do you think about the possibility of letting also use\nthe name constants, as a simple / more relaxed alternative? That would\nspare a source lookup just to write a correct reference to a tx, maybe in a\nforum or a post.\n\nSo a reference to a certain tx could be either:\n\nblockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f\n\nblockchain://tx/ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f\n\nblockchain://ca26cedeb9cbc94e030891578e0d2b688a28902114f6ad2f24ecd3918f76c17f?chain=main\n\n(or a different element name maybe)\n\n-- \nTry the Online TrID File Identifier\nhttp://mark0.net/onlinetrid.aspx\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150901/68c31b7b/attachment.html\u003e", "sig": "1e86f0075245147bee01a84b18f81509fbfee7367010b5a2429dfe2851811d0a93d0475f777fb10e2d9aed4c54b55c55bc69e4317f5d375977fa9c3c320014c3" }