Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2012-05-16 📝 Original message:On Wednesday, May 16, 2012 ...
📅 Original date posted:2012-05-16
📝 Original message:On Wednesday, May 16, 2012 6:18:27 PM Jeff Garzik wrote:
> Instead of further overloading service bits in the version message, or
> altering the version message, let us instead make feature discovery an
> easy, flexible, extensible process.
>
> We can add new commands without impacting older nodes, so let's create
> a new command "get-features" (or pick your name) that returns a list
> of key/value pairs. The key is a string, the value type is determined
> by the key.
That assumes you already have a connection to the peer in question.
As I understand it, the service bits are propagated as part of the address,
so you can see at a glance which nodes you want to connect to for some
special service. Passing a huge list along might be unwieldy (though it
makes sense for protocol changes that don't add new services).
Published at
2023-06-07 10:09:01Event JSON
{
"id": "0056cec098c5a749704f9192212575f930d254f7cca4f886d02c41aa85156417",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686132541,
"kind": 1,
"tags": [
[
"e",
"e69d3a3e0957b3c1430bed5ac6d94159b1bf527c79622eaf72c853e486c89cde",
"",
"root"
],
[
"e",
"91887c49badb0b48153a96a6595aa04b2fe4e307d08115e5d70776e887a8cc23",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2012-05-16\n📝 Original message:On Wednesday, May 16, 2012 6:18:27 PM Jeff Garzik wrote:\n\u003e Instead of further overloading service bits in the version message, or\n\u003e altering the version message, let us instead make feature discovery an\n\u003e easy, flexible, extensible process.\n\u003e \n\u003e We can add new commands without impacting older nodes, so let's create\n\u003e a new command \"get-features\" (or pick your name) that returns a list\n\u003e of key/value pairs. The key is a string, the value type is determined\n\u003e by the key.\n\nThat assumes you already have a connection to the peer in question.\nAs I understand it, the service bits are propagated as part of the address, \nso you can see at a glance which nodes you want to connect to for some \nspecial service. Passing a huge list along might be unwieldy (though it \nmakes sense for protocol changes that don't add new services).",
"sig": "9ff26c0c8660fe7ce3b88bf2bd3fce214954c36f51170b26ad0ded48d700fa501d9c723bf3e11dff9514be8c191d219fe8daa176e8207adbaa2357b0785abf19"
}