Rusty Russell [ARCHIVE] on Nostr: ๐
Original date posted:2019-01-21 ๐ Original message: Hi all, I have a concrete ...
๐
Original date posted:2019-01-21
๐ Original message:
Hi all,
I have a concrete proposal for feature bits.
1. Rename 'local features' to 'peer features'.
2. Rename 'global features' to 'routing features'.
3. Have them share a number space (ie. peer and routing features don't
overlap).
4. Put both in `features` in node announcements, but never use even bits
for peer features.
This means we can both use node_announcement as "connect to a peer which
supports feature X" and "can I route through this node?".
Similarly, (future) DNS seed filtering might support filtering only by
pairs of bits (ie. give me peers which support X, even or odd).
Cheers,
Rusty.
Published at
2023-06-09 12:54:02Event JSON
{
"id": "ede8b003354b249bb737bf8606c6fc786db7759ffc637628cf3d2dc7737d3caa",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686315242,
"kind": 1,
"tags": [
[
"e",
"b4b226e6ac704989b68c2ea53f4bc48ee4ce0583ba9189179d03ea124b64ac50",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "๐
Original date posted:2019-01-21\n๐ Original message:\nHi all,\n\n I have a concrete proposal for feature bits.\n\n1. Rename 'local features' to 'peer features'.\n2. Rename 'global features' to 'routing features'.\n3. Have them share a number space (ie. peer and routing features don't\n overlap).\n4. Put both in `features` in node announcements, but never use even bits\n for peer features.\n\nThis means we can both use node_announcement as \"connect to a peer which\nsupports feature X\" and \"can I route through this node?\".\n\nSimilarly, (future) DNS seed filtering might support filtering only by\npairs of bits (ie. give me peers which support X, even or odd).\n\nCheers,\nRusty.",
"sig": "2d7ee6664d73bed177664e562ebdea0e87eea79d8fc70c4726785a71a9f04fcdfa5492e8657893328d8d9245fc977046adaa7894ea992431c9ddb5dfe1b86bb6"
}