--- Day changed Wed Jun 06 2018 00:31 -!- tiagotrs [~user@p5DC4664B.dip0.t-ipconnect.de] has joined #c-lightning 00:31 -!- tiagotrs [~user@p5DC4664B.dip0.t-ipconnect.de] has quit [Changing host] 00:31 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 00:50 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:49 < bitonic-cjp> Where is transaction forwarding implemented? 01:50 < bitonic-cjp> I would have expected that, on receiving an incoming HTLC, channeld (responsible for managing a single channel?) sends a message to lightningd, which then does forwarding. 01:51 < bitonic-cjp> Since a tx should only be forwarded when incoming funds are committed to, I guess the channeld/lightningd message of interest should be WIRE_CHANNEL_GOT_COMMITSIG, right? 02:03 -githubby:#c-lightning- [lightning] jsarenik closed pull request #1542: external/Makefile: Simplify build and fix race condition (master...jasan/simplify) https://git.io/vh4U3 02:04 -githubby:#c-lightning- [lightning] jsarenik closed pull request #1533: external/Makefile: Change MAKE_HOST and BUILD to CROSS_* (master...jasan/make_host_2nd) https://git.io/vhZKw 02:06 < bitonic-cjp> In lightningd, I think I followed the trace to channel_added_their_htlc. There the trace stops: 02:06 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 245 seconds] 02:08 < bitonic-cjp> The added HTLC (including routing data) is added to a htlc_in structure (hin), which is then added to the wallet. 02:14 < bitonic-cjp> htlc_in.onion_routing_packet seems to be used in peer_accepted_htlc (in peer_htlcs.c) in what seems to be the forwarding algorithm. 02:16 < bitonic-cjp> peer_accepted_htlc is only called in peer_got_revoke, which handles the WIRE_CHANNEL_GOT_REVOKE message from channeld, ... oh wait: 02:16 < bitonic-cjp> I see what is going on. Of course you can only trust an incoming HTLC after the old channel state is revoked by the peer. 02:57 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 03:11 < Lightblock> @rompert mostly for my own research (with regards to your question what I am after) 04:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 04:20 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:04 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:54 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 06:07 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 07:08 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 07:08 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds] 08:20 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 08:42 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 265 seconds] 08:59 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 08:59 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 09:01 -!- tiagotrs [~user@p5DC47AA0.dip0.t-ipconnect.de] has joined #c-lightning 09:01 -!- tiagotrs [~user@p5DC47AA0.dip0.t-ipconnect.de] has quit [Changing host] 09:01 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 09:11 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:15 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 10:31 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 13:00 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 13:47 -!- tiagotrs [~user@p5DC47AA0.dip0.t-ipconnect.de] has joined #c-lightning 13:47 -!- tiagotrs [~user@p5DC47AA0.dip0.t-ipconnect.de] has quit [Changing host] 13:47 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 13:56 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 245 seconds] 14:33 < Lightblock> Also it was mentioned before that node provides most of the info, however seems like c-lightning lacks some of the data about particular channel in comparison to other implementations. 14:33 < Lightblock> For example how to see a funding tx ID of some random channel? 14:44 < molz> Lightblock, what do you mean? 15:03 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 15:05 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 15:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 15:26 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 16:06 -!- contrapumpkin is now known as filthySJW 16:06 -!- filthySJW is now known as contrapumpkin 17:11 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 264 seconds] 17:25 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 17:29 < grafcaps> so it's been a while since I ran my c-lightning node...does it still default to testnet? 19:53 -!- antanst [~antanst@62.169.219.213] has quit [Ping timeout: 265 seconds] 19:55 -!- antanst [~antanst@62.169.219.213] has joined #c-lightning 19:59 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 256 seconds] 20:37 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:53 < molz> grafcaps, if you put 'network=bitcoin' in your config, it should be on mainnet 21:08 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 264 seconds] 21:08 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 23:36 < Lightblock> @molz 23:37 < Lightblock> There is some random channel, I want to know to what was the funding transaction id for it, how do I do it via c-lightning cli? 23:37 < Lightblock> there seems to be no command for that