📅 Original date posted:2015-10-19
📝 Original message:
On Mon, Oct 19, 2015 at 11:18:30AM +1030, Rusty Russell wrote:
> > (1) Pubkey-Channel-Relationships (see other post on ML)
> > Very static, relayed every 10 days // 264 Bytes
> > (2) Node addresses/IP
> > ... approx every 12h // 133 Bytes [...]
> > (3) Channel-Status (capacity, fee, ...)
> > ... once an hour? // 176 Bytes [...]
> These estimates seem about the right ballpark to me. But once per hour
> may be extremely optimistic when channels approach exhaustion.
> Yeah, my design point has been 1M nodes. Ideally, on a cell phone :)
> In the very short term, Bitcoin used IRC as the peer protocol. It has
> the advantage of being really easy to debug, and trivial to implement,
> so I'm going to aim at that while we research our more ambitious
> proposals...
I'm totally a fan of being able to log the entire network dynamics too...
So doing the above over IRC means maybe doubling the byte size to encode
keys/sigs into hex, and adding maybe 32B per message for IRC protocol
overhead. So:
560B/channel/10 days
298B/node/12h
384B/channel/1h
Assume ~10 channels per node and converting to bytes/node/day:
560B/node/day
564B/node/day
92,160B/node/day
= 93,284B/node/day total
which is about 1.054 KiB/s per thousand nodes. If it's a single server
relaying that to a thousand nodes, that's 8.2 megabit/s outgoing
already. So that plan probably maxes out somewhere between 500-3000 nodes?
>From what I gather bitcoin only used IRC to get IP addresses to connect
to, which were encoded in the nicks used, rather than anything being
actually said. It seems like that got up to 10000 nodes [0]. Hopefully
lightning's irc usage doesn't get misdetected as botnet C&C :)
[0] https://bitcointalk.org/index.php?topic=9240.0
Cheers,
aj
Anthony Towns [ARCHIVE] /
npub17r…x9l2h
2023-06-09 12:44:52
in reply to nevent1q…wyxl
Author Public Key
npub17rld56k4365lfphyd8u8kwuejey5xcazdxptserx03wc4jc9g24stx9l2hPublished at
2023-06-09 12:44:52Event JSON
{
"id": "91c3b7055456c7af03928d3d2cb3224b924a7b31a3a43677af7aa2d0239f46ad",
"pubkey": "f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab",
"created_at": 1686314692,
"kind": 1,
"tags": [
[
"e",
"0702ca6d920739e71123cfb8aac3090846d575270e54e6a6dbe4f2e97cc141f7",
"",
"root"
],
[
"e",
"00a7155ca0eea7fffd2df79d6ec14549537e21ec8c8406b67609106ae5293da0",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2015-10-19\n📝 Original message:\nOn Mon, Oct 19, 2015 at 11:18:30AM +1030, Rusty Russell wrote:\n\u003e \u003e (1) Pubkey-Channel-Relationships (see other post on ML)\n\u003e \u003e Very static, relayed every 10 days // 264 Bytes\n\u003e \u003e (2) Node addresses/IP\n\u003e \u003e ... approx every 12h // 133 Bytes [...]\n\u003e \u003e (3) Channel-Status (capacity, fee, ...)\n\u003e \u003e ... once an hour? // 176 Bytes [...]\n\u003e These estimates seem about the right ballpark to me. But once per hour\n\u003e may be extremely optimistic when channels approach exhaustion.\n\n\u003e Yeah, my design point has been 1M nodes. Ideally, on a cell phone :)\n\n\u003e In the very short term, Bitcoin used IRC as the peer protocol. It has\n\u003e the advantage of being really easy to debug, and trivial to implement,\n\u003e so I'm going to aim at that while we research our more ambitious\n\u003e proposals...\n\nI'm totally a fan of being able to log the entire network dynamics too...\n\nSo doing the above over IRC means maybe doubling the byte size to encode\nkeys/sigs into hex, and adding maybe 32B per message for IRC protocol\noverhead. So:\n\n 560B/channel/10 days\n 298B/node/12h\n 384B/channel/1h\n\nAssume ~10 channels per node and converting to bytes/node/day:\n\n 560B/node/day\n 564B/node/day\n 92,160B/node/day\n= 93,284B/node/day total\n\nwhich is about 1.054 KiB/s per thousand nodes. If it's a single server\nrelaying that to a thousand nodes, that's 8.2 megabit/s outgoing\nalready. So that plan probably maxes out somewhere between 500-3000 nodes?\n\n\u003eFrom what I gather bitcoin only used IRC to get IP addresses to connect\nto, which were encoded in the nicks used, rather than anything being\nactually said. It seems like that got up to 10000 nodes [0]. Hopefully\nlightning's irc usage doesn't get misdetected as botnet C\u0026C :)\n\n[0] https://bitcointalk.org/index.php?topic=9240.0\n\nCheers,\naj",
"sig": "72e338a0b475a4b8b8d9f04207080d88ab44dcef10e7975befdf6186b430035069e12e9c347ca5fa9e78bc78336c4dfba27a3ad162210baaa1049ebd680460e3"
}