📅 Original date posted:2020-08-16
📝 Original message:Concept ack!
It might be nice to include a few negotiation utility functions either in
this bip or at the same time in a separate bip. An example we might want to
include is a "polite disconnect", whereby a node can register that you
don't want to connect in the future due to incompatibility.
It also might be nice to standardize some naming convention or negotiation
message type so that we don't end up with different negotiation systems.
Then we can also limit the bip so that we're only defining negotiation
message types as ignorable v.s. some other message type (which can also be
ignored, but maybe we want to do something else in the future).
This also makes it easier for old (but newer than this bip) nodes to apply
some generic rules around reporting/rejecting/responding to unknown feature
negotiation v.s. an untagged message which might be a negotiation or
something else.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200816/6fb078d1/attachment.html>;
Jeremy [ARCHIVE] /
npub1q8…8qwta
2023-06-07 18:26:23
in reply to nevent1q…etjz
Author Public Key
npub1q86n5vtxkwerzwfqza3hwls8pl8764244464talfqy2vpj0qaz6q38qwtaSeen on
wss://relay.nostr.bandPublished at
2023-06-07 18:26:23Event JSON
{
"id": "5ae852382d6989763930345c1dcd4ba42a0762013d4ebd3b1e73189c1e72b744",
"pubkey": "01f53a3166b3b23139201763777e070fcfed5555ad7555f7e90114c0c9e0e8b4",
"created_at": 1686162383,
"kind": 1,
"tags": [
[
"e",
"43edfd73733fa9cb455dfd9022ab700e39020c27283a7e2f0343a8c6fb631001",
"",
"root"
],
[
"e",
"9611a64587df776135141874818e01866d3157ba0aa598728bc645b866025457",
"",
"reply"
],
[
"p",
"841503960589cc9bc44213e4addc2aa2fe3fe0727b79f90df3cbd6762875c31e"
]
],
"content": "📅 Original date posted:2020-08-16\n📝 Original message:Concept ack!\n\nIt might be nice to include a few negotiation utility functions either in\nthis bip or at the same time in a separate bip. An example we might want to\ninclude is a \"polite disconnect\", whereby a node can register that you\ndon't want to connect in the future due to incompatibility.\n\nIt also might be nice to standardize some naming convention or negotiation\nmessage type so that we don't end up with different negotiation systems.\nThen we can also limit the bip so that we're only defining negotiation\nmessage types as ignorable v.s. some other message type (which can also be\nignored, but maybe we want to do something else in the future).\n\nThis also makes it easier for old (but newer than this bip) nodes to apply\nsome generic rules around reporting/rejecting/responding to unknown feature\nnegotiation v.s. an untagged message which might be a negotiation or\nsomething else.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200816/6fb078d1/attachment.html\u003e",
"sig": "5b99cd275220747eaf50e3765423b95a48f353e61110e959eefd620be06da96ac50f487d5bf276b40d76246ffa27814ddb0ac9dc79479afd73691449d75c7549"
}