--- Log opened Thu Jun 18 00:00:53 2020 00:43 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 01:54 -!- nandubatchu [~nandubatc@ec2-18-138-215-40.ap-southeast-1.compute.amazonaws.com] has joined #c-lightning 01:54 < nandubatchu> Hi 01:56 < nandubatchu> cdecker: how many lightningd nodes can be connected to a single bitcoind node? How scalable is the lightningd setup to cater to multiple users (each with their personalised node)? 02:01 -!- nandubatchu [~nandubatc@ec2-18-138-215-40.ap-southeast-1.compute.amazonaws.com] has quit [Remote host closed the connection] 02:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning [] 02:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning 02:26 <@cdecker> There is no real limit to the number of nodes backed by a single bitcoind, though at some point new blocks would result in all nodes requesting the block at once 02:27 <@cdecker> This is because the poll timers for new blocks would likely slowly synchronize and when a new block comes in you'd have all nodes wanting to download them at the same time 02:28 <@cdecker> You can quite easily counter-act this by building a caching reverse proxy, or an alternative backend plugin that spreads the time the nodes learn about new blocks out a bit 02:28 <@cdecker> That'd also take care of our other frequent poll: feerates. They can be cached trivially, reducing the load on the real bitcoind 02:29 <@cdecker> Personally I've run 250 nodes against a single bitcoind instance without any of the mentioned improvements and no problems, but I'm sure that somewhere there is a limit :-) 02:30 <@cdecker> Hope that helps nandubatchu :-) 02:38 < darosior> cdecker: there is the -rpcthreads limit though 02:38 < darosior> I'm impressed about the 250 nodes ! I'd thought you'd have reached the limit 02:40 < darosior> `bcli` will make parallel requests to `bitcoind` while carefully keeping the number of request <= 4 (the default for -rpcthreads), as `bitcoind` will kindly discard our request without any error otherwise : multiple instances of lightningd (hence bcli) hitting the same bitcoind would *silently* overcome this limit (at least I thought) 02:45 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has joined #c-lightning 02:51 -!- liberliver1 [~Thunderbi@x4e376b1e.dyn.telefonica.de] has joined #c-lightning 02:53 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 258 seconds] 02:53 -!- liberliver1 is now known as liberliver 02:58 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 03:04 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has joined #c-lightning 03:09 -!- liberliver [~Thunderbi@x4e376b1e.dyn.telefonica.de] has quit [Ping timeout: 240 seconds] 03:09 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 03:12 <@cdecker> I might have tweaked te listen() backlog size to something more usable :-) 03:17 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 03:26 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 03:49 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has joined #c-lightning 05:22 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds] 05:24 -!- jonatack [~jon@184.75.221.35] has joined #c-lightning 07:15 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 07:38 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 07:56 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 08:02 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has joined #c-lightning 08:37 -!- kabaum [~kabaum@84.216.157.0] has joined #c-lightning 09:14 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 09:20 < devrandom> cdecker: in https://github.com/ElementsProject/lightning/pull/3745#issuecomment-644308699 - what exactly do you mean by "blob handling"? do you mean persisting the opaque blob, or do you mean unpacking the blob? or something to do with synchronization? 09:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 09:25 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 09:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 09:31 <@cdecker> devrandom: we can hide the blob that encapsulates the context from `lightningd` by having a proxy that adds it to each hsmd call, and strips it from the returned result, thus making it transparent from the point of view of `lightningd` 09:47 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 09:55 -!- leinlawun[m] [leinlawunm@gateway/shell/matrix.org/x-ocuqwjlclssyzsfu] has joined #c-lightning 09:59 -!- kabaum [~kabaum@84.216.157.0] has quit [Ping timeout: 240 seconds] 10:11 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 10:19 < ksedgwic> Would the proxy persist the blob in case the lightning node crashed? 10:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning [] 10:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning 10:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 11:17 -!- jonatack [~jon@184.75.221.35] has quit [Ping timeout: 258 seconds] 11:20 -!- jonatack [~jon@37.170.249.11] has joined #c-lightning 11:55 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:fb44:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 272 seconds] 11:57 -!- fiatjaf [~fiatjaf@2804:7f2:2a85:8ab8:ea40:f2ff:fe85:d2dc] has joined #c-lightning 12:02 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 265 seconds] 12:18 <@cdecker> Yes, that'd be necessary (sicne the HSM doesn't have it stored if it relies on this feature) 12:31 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 12:31 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 13:11 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds] 13:20 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 13:20 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds] 13:48 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Quit: ZNC 1.7.5 - https://znc.in] 13:49 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 14:14 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning 15:09 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds] 15:14 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 15:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:54 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 17:56 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 18:28 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 18:36 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning [] 18:36 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning 18:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 19:34 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Quit: ZNC 1.7.5 - https://znc.in] 19:36 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 21:18 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 21:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 21:24 -!- vasild_ is now known as vasild 23:15 -!- jonatack_ [~jon@37.166.220.215] has joined #c-lightning 23:18 -!- jonatack [~jon@37.170.249.11] has quit [Ping timeout: 264 seconds] --- Log closed Fri Jun 19 00:00:54 2020