--- Log opened Thu May 27 00:00:20 2021 00:36 -!- Guest79 [~Guest79@n.bublina.eu.org] has joined #c-lightning 01:10 -!- reallll [~belcher@user/belcher] has joined #c-lightning 01:12 -!- vincenzopalazzo [~vincenzop@host-79-23-113-134.retail.telecomitalia.it] has joined #c-lightning 01:12 < vincenzopalazzo> hello world! 01:13 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 264 seconds] 01:25 < Guest79> Hello world! 01:41 -!- jasanxyz [~jasanxyz@n.bublina.eu.org] has joined #c-lightning 01:41 < jasanxyz> Hello World! 01:43 * Guest79 was always starting from scratch every year, this time the whole world starts from scratch... 01:44 < Guest79> even without me 01:44 < jasanxyz> haha 01:44 < jasanxyz> luckily Bitcoin is unshaked by all this 01:47 -!- Guest79 [~Guest79@n.bublina.eu.org] has quit [Quit: Client closed] 02:01 -!- jasanxyz [~jasanxyz@n.bublina.eu.org] has quit [Remote host closed the connection] 02:05 -!- jasan [~jasan@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning 02:05 < jasan> /NAMES 02:06 < jasan> \:) 02:13 -!- jasan1 [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning 02:13 -!- jasan [~jasan@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has quit [Remote host closed the connection] 02:13 -!- jasan1 is now known as jasan 02:17 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 02:39 -!- reallll is now known as belcher 03:14 -!- michaelfolkson [~michael@2a00:23c7:60c5:ad01:5db2:a238:1b75:5efc] has joined #c-lightning 03:17 -!- gijswijs [~gijswijs3@175.137.240.253] has joined #c-lightning 03:19 -!- gijswijs [~gijswijs3@175.137.240.253] has left #c-lightning [] 03:20 -!- gijswijs [~gijswijs3@175.137.240.253] has joined #c-lightning 03:22 < gijswijs> Hey! I have a question about sendpay_success notification that I use in my plugin. 03:22 < gijswijs> What I want to know is the route the successful payment took. 03:23 < gijswijs> Currently the only way of doing this (I think) is intercepting the createonion with the rpc_command hook. 03:24 < gijswijs> Unpack the payloads and remember them untill you get the sendpay_succes notification 03:25 < gijswijs> Is there an easier way? 03:33 -!- cdecker [~cdecker@243.86.254.84.ftth.as8758.net] has quit [Quit: The Lounge - https://thelounge.chat] 03:34 -!- cdecker [~cdecker@243.86.254.84.ftth.as8758.net] has joined #c-lightning 03:39 -!- cdecker [~cdecker@243.86.254.84.ftth.as8758.net] has quit [Quit: The Lounge - https://thelounge.chat] 03:39 -!- cdecker [~cdecker@243.86.254.84.ftth.as8758.net] has joined #c-lightning 04:29 -!- gijswijs [~gijswijs3@175.137.240.253] has quit [Ping timeout: 264 seconds] 04:58 -!- shesek [~shesek@185.3.145.30] has joined #c-lightning 05:05 -!- gijswijs [~gijswijs3@175.137.240.253] has joined #c-lightning 05:10 -!- shesek [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 05:10 -!- shesek [~shesek@185.3.145.30] has joined #c-lightning 05:41 -!- shesek [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 05:42 -!- shesek [~shesek@185.3.145.30] has joined #c-lightning 06:02 < andrewtoth> sendpay takes a route as its first argument. So you must already have the successful route when calling, unless I'm not understanding. 06:03 < gijswijs> Yeah, I thought so too. 06:04 < gijswijs> But I don't see sendpay passing through the rpc_command hook. 06:04 < gijswijs> Intercepting sendpay was my first thought too. 06:16 < gijswijs> Let me clarify that, if you use the (higher level) pay command, the sendpay command isn't passed through the rpc_command hook. (I thought pay used sendpay after finding a route) 06:18 -!- vincenzopalazzo [~vincenzop@host-79-23-113-134.retail.telecomitalia.it] has quit [Quit: Leaving] 06:24 < Ademan> could someone check to see if they have (functional) tor peers with "netaddr": ["127.0.0.1:XXXX"] ? 06:30 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has quit [Quit: ZNC 1.8.0 - https://znc.in] 06:30 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning 06:48 -!- shesek [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 06:48 -!- shesek [~shesek@185.3.145.30] has joined #c-lightning 07:02 -!- shesek [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 07:03 -!- shesek [~shesek@185.3.145.30] has joined #c-lightning 07:08 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 07:09 -!- shesek [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 07:16 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 07:16 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 07:33 < Ademan> I imagine c-lightning is pretty robust to this due to the plugin interface over stdin/stdout but can a poorly behaved plugin hang c-lightning in any way other than resource exhaustion? 07:42 -!- gijswijs [~gijswijs3@175.137.240.253] has quit [Quit: Leaving] 07:43 < darosior> Ademan: yes, a plugin could register a hook and never answer 07:44 < darosior> Or create a re-entrant command (would be a fun experiment) 07:46 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 07:46 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 07:49 < andrewtoth> gijswijs I believe it uses waitsendpay, instead of sendpay. 07:55 -!- michaelfolkson [~michael@2a00:23c7:60c5:ad01:5db2:a238:1b75:5efc] has quit [Quit: I am away from my computer] 07:57 < Ademan> darosior: oh? I am just starting to look I just kind of assumed all notifications from the daemon were async. Good point about commands though... 07:59 -!- michaelfolkson [~michael@2a00:23c7:60c5:ad01:5db2:a238:1b75:5efc] has joined #c-lightning 07:59 < andrewtoth> What would be a reason why calling getroute for a peer you have a direct channel with will return a route that doesn't use the direct channel? There is more than enough outbound liquidity for the amount. 08:01 < darosior> Ademan: you have two kinds of "notifications": https://lightning.readthedocs.io/PLUGINS.html#hooks 08:16 < Ademan> darosior: ah wow! That's a lot of flexibility. Thanks! 08:25 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 08:28 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 08:42 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 08:42 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 08:58 -!- _0x0ff [~0x0ff@user/0x0ff/x-0302470] has joined #c-lightning 08:59 -!- livestradamus [~quassel@user/livestradamus] has quit [Remote host closed the connection] 09:00 -!- livestradamus [~quassel@user/livestradamus] has joined #c-lightning 09:06 -!- michaelfolkson [~michael@2a00:23c7:60c5:ad01:5db2:a238:1b75:5efc] has quit [Quit: I am away from my computer] 10:53 -!- michaelfolkson [~michael@2a00:23c7:60c5:ad01:5db2:a238:1b75:5efc] has joined #c-lightning 11:16 < niftynei> rusty: -NickServ- You are logged in as niftynei. 11:16 < niftynei> is ChanServ a different thing? 11:48 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 11:48 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 11:56 < darosior> niftynei: maybe you hadn't register with the email thing when he tried? 12:53 -!- michaelfolkson [~michael@2a00:23c7:60c5:ad01:5db2:a238:1b75:5efc] has quit [Quit: I am away from my computer] 13:46 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 13:46 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 13:57 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 14:01 -!- shesek`` [~shesek@185.3.145.30] has quit [Ping timeout: 264 seconds] 14:04 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 14:05 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 14:22 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 14:22 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 14:52 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 14:52 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 15:33 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 15:34 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 15:45 < Ademan> I am a moron, I didn't realize listchannels listed every known channel lol 15:46 < Ademan> I just saw a lot of results and filtered for ones with me as the source, and assumed I had a lot of inbound channels for no good reason lol 15:46 < Ademan> then I noticed there were 75k of them... 16:26 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 16:26 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning --- Log closed Thu May 27 16:27:35 2021 --- Log opened Thu May 27 16:27:35 2021 16:44 -!- kanzure [~kanzure@user/kanzure] has joined #c-lightning --- Log closed Thu May 27 16:48:47 2021 --- Log opened Thu May 27 16:48:47 2021 --- Log closed Thu May 27 16:59:04 2021 --- Log opened Thu May 27 16:59:04 2021 17:02 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 17:03 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 17:05 -!- rusty [~rusty@pa49-178-4-6.pa.nsw.optusnet.com.au] has joined #c-lightning --- Log closed Thu May 27 17:05:55 2021 --- Log opened Thu May 27 17:05:55 2021 17:16 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 17:17 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 17:36 -!- rusty [~rusty@pa49-178-4-6.pa.nsw.optusnet.com.au] has quit [Ping timeout: 264 seconds] 17:57 -!- gijswijs [~gijswijs3@175.137.240.253] has joined #c-lightning 18:03 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 244 seconds] 18:10 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 18:10 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 18:44 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 18:44 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 19:04 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning 19:11 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning 19:14 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 265 seconds] 19:32 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 19:33 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 19:44 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 19:48 -!- shesek` [~shesek@185.3.145.30] has quit [Ping timeout: 272 seconds] 19:52 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 19:56 -!- shesek`` [~shesek@185.3.145.30] has quit [Ping timeout: 248 seconds] 20:01 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 20:01 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 20:31 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 20:31 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 20:44 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 20:44 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 20:54 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 20:56 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 21:02 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 21:02 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 21:15 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 21:16 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 21:28 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 21:29 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 21:38 -!- shesek`` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 21:39 -!- shesek`` [~shesek@185.3.145.30] has joined #c-lightning 21:39 -!- gijswijs [~gijswijs3@175.137.240.253] has quit [Ping timeout: 264 seconds] 21:51 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 21:55 -!- shesek`` [~shesek@185.3.145.30] has quit [Ping timeout: 248 seconds] 22:00 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 22:00 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 22:04 -!- gijswijs [~gijswijs3@175.137.240.253] has joined #c-lightning 22:39 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 264 seconds] 22:59 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 22:59 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 23:12 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 23:13 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 23:52 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 23:53 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning 23:57 -!- shesek` [~shesek@185.3.145.30] has quit [Read error: Connection reset by peer] 23:58 -!- shesek` [~shesek@185.3.145.30] has joined #c-lightning --- Log closed Fri May 28 00:00:21 2021