--- Log opened Fri Dec 20 00:00:42 2019
00:11 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: No Ping reply in 180 seconds.]
00:13 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning
00:47 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
00:47 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
00:53 < m-schmoock> cdecker: strange question, is there any way to guesstimate the HTLC fees of a remote connected node when receiving a (circular) payment from that node?
00:57 < m-schmoock> when writing tests for my drain/fill plugin, i discovered that it fails when filling a channel to 100% using chunked payments that would result in multiple HTLCs at the side where the channel is drained
00:57 < m-schmoock> test:  https://github.com/lightningd/plugins/pull/71/files#diff-88f5d9948c5e37be5dc85a7dfbfc4503R114
00:58 < m-schmoock> it will actually fail at lin 161 where a CAPACITY_EXCEEDED is raised in l4  because the plugin in l1 is not able to calculate the resulting HTLC fees at l4
00:59 < m-schmoock> https://travis-ci.org/lightningd/plugins/jobs/624968255#L4437
01:06 < m-schmoock> since the node where the capacity error is raised is directly connected via the channel where it fails, l1 should be able to 'know' the resulting HTLC fees that go ontop of the reserve somehow
01:07 < m-schmoock> same as we fine tuned the 'spendable_msat' for accounting htlc fees earlier this year just in the other direction 
01:10 < m-schmoock> maybe I should just go for '2 times reserve' or add some very complicated remote HTLC fee calculator
01:15 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
01:22 -!- darosior [~darosior@194.36.189.246] has quit [Quit: darosior]
01:26 -!- darosior [~darosior@194.36.189.246] has joined #c-lightning
01:27 -!- darosior [~darosior@194.36.189.246] has quit [Client Quit]
01:28 -!- darosior [~darosior@194.36.189.246] has joined #c-lightning
01:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
01:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
01:58 -!- MrHash [~mrhash@host31-52-68-33.range31-52.btcentralplus.com] has quit [Ping timeout: 268 seconds]
02:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
02:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:03 -!- dr-orlovsky [~dr-orlovs@89.143.12.62] has quit [Quit: My MacBook has gone to sleep. ZZZzzz...]
03:23 -!- Jmabsd [~jmabsd@unaffiliated/jmabsd] has joined #c-lightning
03:24 -!- phwalkr [~phwalkr@2001:1284:f01c:264c:69de:2b35:ece9:5564] has joined #c-lightning
03:36 -!- phwalkr [~phwalkr@2001:1284:f01c:264c:69de:2b35:ece9:5564] has quit [Ping timeout: 248 seconds]
03:46 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
03:59 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 248 seconds]
05:22 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has joined #c-lightning
05:40 -!- phwalkr [~phwalkr@2001:1284:f01c:264c:10e7:f1f6:d194:2b4b] has joined #c-lightning
05:41 < phwalkr> Hey. I have a HTLC question
05:41 < phwalkr> I don't understand the role and purpose of HTLC outputs in Lightning. Say I'm doing a transfer A->D via A->B, B->C, C->D.   Which are the HTLC:s and during what time interval do they exist? What's the point
06:02 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds]
06:07 < darosior> phwalkr: The point is to *atomically* transfer sats between commitment transactions pairs along the path
06:08 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
06:09 < darosior> phwalkr: "Say I'm doing a transfer A->D via A->B, B->C, C->D.   Which are the HTLC" ==> Basically, an HTLC out on your commit tx, an HTLC in on B's commit tx, an HTLC out on B's commit tx with C, an HTLC in in C's commit tx, etc...
06:09 < darosior> D resolving its in HTLC makes C resolves its own, then B its own, etc..
06:10 < darosior> "during what time interval do they exist" => That's a config option.
06:11 < darosior> Ah mickael already answered on #lightning-dev... Don't ask two times..
06:13 < phwalkr> darosior: Sorry about that, I'll not ask twice in the future.
06:42 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
07:01 -!- rottensox [~rottensox@unaffiliated/rottensox] has left #c-lightning ["Bye"]
07:02 -!- Jmabsd [~jmabsd@unaffiliated/jmabsd] has quit [Ping timeout: 260 seconds]
07:29 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has quit [Ping timeout: 260 seconds]
07:39 -!- phwalkr [~phwalkr@2001:1284:f01c:264c:10e7:f1f6:d194:2b4b] has quit [Read error: Connection reset by peer]
07:39 -!- phwalkr [~phwalkr@168.181.51.205] has joined #c-lightning
08:57 -!- phwalkr [~phwalkr@168.181.51.205] has quit [Quit: Leaving...]
09:02 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
09:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
09:47 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds]
09:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
10:25 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
10:32 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
10:39 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
10:40 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
10:42 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
10:57 <@niftynei> i read somewhere last week that the reason bitcoind sets the sequence number to FEFFFFFF is so that you can also set the locktime to the current block
10:57 <@niftynei> the rationale for this is that it makes it harder to re-org since the set of txs available to use in block construction is limited by
10:57 <@niftynei> the locktimes they've set
10:58 <@niftynei> if we enable rbf for things, it seems prudent to also start setting the locktime for txs to the current blockheight
10:58 <@niftynei> ugh i should check to see if bitcoind does this shouldnt i lol
11:04 <@niftynei> update: this is infact the default behavior of sendtoaddress; experimentally it appears that they're setting the locktime to about 5 blocks prior to the current chaintip
11:05 <@niftynei> actually it's 6 blocks, idky i want it to be 5 (locktime is 1632427, chaintips shows 1632433)
11:06 <@niftynei> at the very least, seems like something we could implement for withdrawals
11:06 <@niftynei> it also seems prudent to include in the rbf proposal
11:19 -!- devrandom [~devrandom@unaffiliated/niftyzero1] has quit [Ping timeout: 260 seconds]
11:27 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
11:37 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
11:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
11:53 -!- devrandom [~devrandom@unaffiliated/niftyzero1] has joined #c-lightning
12:23 -!- devrandom [~devrandom@unaffiliated/niftyzero1] has quit [Read error: Connection reset by peer]
12:28 -!- devrandom [~devrandom@unaffiliated/niftyzero1] has joined #c-lightning
12:36 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
12:53 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
13:27 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
13:30 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds]
13:49 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
13:52 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
13:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 268 seconds]
14:00 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
14:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds]
14:09 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
14:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:03 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:18 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
15:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:15 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 265 seconds]
16:20 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
17:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
17:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
18:12 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
19:32 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
--- Log closed Fri Dec 20 19:36:00 2019
--- Log opened Fri Dec 20 19:36:00 2019
20:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
20:53 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer]
21:09 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
21:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
21:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds]
22:55 <@niftynei> this seems like a dumb question, but do i need to listen to ipv6 on a different port than ipv4?
23:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
23:21 <@niftynei> PSA if you're running a clightning node on testnet, i pulled a list of all the nodes advertising useless ip addresses. maybe check if you're on it? https://gist.github.com/niftynei/2207f41184e1374bd2ad705b2efa9641
23:21 <@niftynei> this is just testnet, i'll run the mainnet one tmw maybe
23:37 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
--- Log closed Sat Dec 21 00:00:44 2019