--- Log opened Thu Aug 01 00:00:27 2019 00:10 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds] 00:17 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 00:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 01:40 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 272 seconds] 01:47 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 02:00 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Ping timeout: 245 seconds] 02:19 -!- Kostenko [Kostenko@gateway/vpn/nordvpn/kostenko] has quit [Ping timeout: 248 seconds] 02:21 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 02:33 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning 02:39 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning 03:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 272 seconds] 03:06 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 03:18 <@cdecker> e4xit: the `htlc_accepted` hook is probably what you want, it's not at the messaging layer, but you get the info about the HTLC, the onion and can forward it using another transport layer, and then return the final decision on what to do with the HTLC 03:19 <@cdecker> It was primarily implemented for use-cases such as cross-chain atomic swaps (which bitonic-cjp is working on), and allows you to get notified about an HTLC, forward it in another network and then report back success or failure 03:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning [] 04:31 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8e3:af4f:841e:206a] has joined #c-lightning 04:39 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8e3:af4f:841e:206a] has quit [Ping timeout: 264 seconds] 04:43 < e4xit> cdecker: niftynei, thanks, but I would actually like to take control of the messages' routes, and pass them out of band to another node, recieving responses through the same out-of-band channel. 05:09 <@cdecker> e4xit: in that case you might want to implement a man-in-the-middle proxy that talks to c-lighting, forwarding any messages over the alternative transport and injecting received messages back in. Routing all messages through a plugin is unlikely to be an option, since it adds loads of complexity and delays 06:25 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 272 seconds] 06:31 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 07:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds] 07:57 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 09:33 -!- darosior [~darosior@107.175.255.247] has joined #c-lightning 09:43 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has joined #c-lightning 11:17 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 11:21 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 245 seconds] 11:26 -!- reallll is now known as belcher 11:30 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 12:10 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 244 seconds] 12:31 < blockstream_bot> [Bjørn Olav Jalborg, Blockstream] I heard the other day that c-lightning fuzzes amounts, to protect the users privacy. Does anyone have more details as to how this works? I imagine the recipient doesn’t know the amount is fuzzed. Is it then fussed along the route? 13:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 14:12 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds] 14:31 -!- Kostenko [~Kostenko@195.12.50.233] has quit [Ping timeout: 272 seconds] 14:32 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 14:53 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning 14:55 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Ping timeout: 248 seconds] 17:59 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:01 -!- Kostenko [~Kostenko@195.12.50.233] has quit [Ping timeout: 248 seconds] 18:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 260 seconds] 18:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:49 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has joined #c-lightning 19:12 -!- RonNa [~quassel@2001-b011-4004-07f4-51b9-4582-d6f8-cb5c.dynamic-ip6.hinet.net] has quit [Ping timeout: 250 seconds] 19:38 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning 19:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:50 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning [] 19:50 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning 20:35 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning [] 20:35 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning 21:19 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Ping timeout: 258 seconds] 21:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:39 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning 21:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 23:19 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning --- Log closed Fri Aug 02 00:00:28 2019