📅 Original date posted:2015-08-09
📝 Original message:I'm cautious of using human-meaningful identifiers, especially any that
might require a central repository, due to name collisions. Examples
that could be complicated include BitcoinDark, Litedoge, and other names
that base on existing coins. I think the ability to differentiate
between test networks is also useful.
Could certainly just use the genesis hash as network ID, that would
work. Bit long, but suspect 64 bytes isn't the end of the world! I'll
see if any more responses come in then raise a BIP for using genesis
hash as an alternative to short names.
Ross
On 09/08/2015 15:29, Mike Hearn wrote:
>
> I'd appreciate initial feedback on the idea, and if there's no
> major objections I'll raise this as a BIP.
>
>
> The reason BIP 70 doesn't do this is the assumption that alt coins are
> ... well .... alt. They can vary in arbitrary ways from Bitcoin, and
> so things in BIP70 that work for Bitcoin may or may not work for other
> coins.
>
> If your alt coin is close enough to BIP 70 that you can reuse it "as
> is" then IMO we should just define a new network string for your alt.
> network = "dogecoin-main" or whatever.
>
> You could also use the genesis hash as the network name. That works
> too. But it's less clear and would involve lookups to figure out what
> the request is for, if you find such a request in the wild. I don't
> care much either way.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150809/5e746ec0/attachment.html>;
Ross Nicoll [ARCHIVE] /
npub10p…pfaef
2023-06-07 19:34:29
in reply to nevent1q…mer2
Author Public Key
npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaefPublished at
2023-06-07 19:34:29Event JSON
{
"id": "784e69287456f43f7effcb81e2cea2652bfa8a17c143c246922c9f5a40112cb3",
"pubkey": "787ecd48da0d9610d322fb67c86ad23a5287d688559b2ff8ee546721fd990129",
"created_at": 1686159269,
"kind": 1,
"tags": [
[
"e",
"a705c666a2ba5f9b9fec1e15ec37ee592936203f74c541b73847f917a0090786",
"",
"root"
],
[
"e",
"7f6abc0f52c3dc7e09c1d0d7e4ef7fa2b384ba362e681024a528d3376e4163bc",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2015-08-09\n📝 Original message:I'm cautious of using human-meaningful identifiers, especially any that \nmight require a central repository, due to name collisions. Examples \nthat could be complicated include BitcoinDark, Litedoge, and other names \nthat base on existing coins. I think the ability to differentiate \nbetween test networks is also useful.\n\nCould certainly just use the genesis hash as network ID, that would \nwork. Bit long, but suspect 64 bytes isn't the end of the world! I'll \nsee if any more responses come in then raise a BIP for using genesis \nhash as an alternative to short names.\n\nRoss\n\nOn 09/08/2015 15:29, Mike Hearn wrote:\n\u003e\n\u003e I'd appreciate initial feedback on the idea, and if there's no\n\u003e major objections I'll raise this as a BIP.\n\u003e\n\u003e\n\u003e The reason BIP 70 doesn't do this is the assumption that alt coins are \n\u003e ... well .... alt. They can vary in arbitrary ways from Bitcoin, and \n\u003e so things in BIP70 that work for Bitcoin may or may not work for other \n\u003e coins.\n\u003e\n\u003e If your alt coin is close enough to BIP 70 that you can reuse it \"as \n\u003e is\" then IMO we should just define a new network string for your alt. \n\u003e network = \"dogecoin-main\" or whatever.\n\u003e\n\u003e You could also use the genesis hash as the network name. That works \n\u003e too. But it's less clear and would involve lookups to figure out what \n\u003e the request is for, if you find such a request in the wild. I don't \n\u003e care much either way.\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150809/5e746ec0/attachment.html\u003e",
"sig": "5aec31d272115aae8d71a416907d873197e6ceee2bd135ab7f1a5ebab2ff761e763a1bd64322e2e88e6d9f5b8185724817adc0ea5d484dadaaf9da60880ae0c4"
}