--- Log opened Wed Jul 28 00:00:21 2021 00:00 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 01:21 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 268 seconds] 01:32 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning 01:36 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 244 seconds] 01:40 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 02:04 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 245 seconds] 03:02 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 03:06 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 250 seconds] 03:26 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 03:32 < nathanael> hmm, does c-lightning something every 24 hours? 03:32 < nathanael> i am running a pruned bitcoind and get my log spanned about a missing block every day around the same time 03:32 < nathanael> /s/spanned/spammed/ 03:32 < nathanael> after a restart everything is normal 03:48 < darosior> nathanael: fetching the gossip is done periodically. Missing block is nonfatal, it's to check for announced channel funding tx 03:52 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 04:25 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection] 04:25 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning 04:25 < nathanael> darosior: but every day at around the same time it looks for the same block - and also my logfile grows to MBs cause it logs that every second (with log-level=info) 04:26 < nathanael> 24h intervall - is gossip fetched only every 24h? 05:12 -!- livestradamus [~quassel@user/livestradamus] has joined #c-lightning 05:25 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection] 05:26 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning 05:52 -!- Dan[m] [~drobertsm@2001:470:69fc:105::c80] has quit [Quit: You have been idle for 30+ days] 07:53 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 240 seconds] 08:57 -!- jarthur [~jarthur@2603-8080-1540-002d-8433-02bf-c0e0-ee2c.res6.spectrum.com] has joined #c-lightning 09:03 -!- roasbeef [~roasbeef@104.131.26.124] has quit [Ping timeout: 240 seconds] 09:13 -!- roasbeef [~roasbeef@104.131.26.124] has joined #c-lightning 11:17 -!- rich- [rich@2600:3c00::f03c:92ff:fe8e:dce6] has joined #c-lightning 11:18 -!- belcher [~belcher@user/belcher] has joined #c-lightning 11:39 -!- rich- is now known as sandipndev 11:43 -!- sandipndev [rich@2600:3c00::f03c:92ff:fe8e:dce6] has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in] 12:03 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection] 12:04 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning 12:08 -!- yakshaver [rich@2600:3c00::f03c:92ff:fe8e:dce6] has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in] 12:08 -!- yakshaver [yakshaver@2600:3c00::f03c:92ff:fe8e:dce6] has joined #c-lightning 13:28 < vincenzopalazzo> nathanael: maybe it is looked for the same block because one transaction to verify some of your channel is always there? Not sure about that 14:29 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 245 seconds] 15:52 -!- jarthur_ [~jarthur@2603-8080-1540-002d-45eb-dc20-018b-c9ba.res6.spectrum.com] has joined #c-lightning 15:53 -!- jarthur [~jarthur@2603-8080-1540-002d-8433-02bf-c0e0-ee2c.res6.spectrum.com] has quit [Ping timeout: 240 seconds] 16:20 -!- Guest65 [~Guest65@154.6.16.36] has joined #c-lightning 16:21 < Guest65> hi all, i have a question. I tried closing a channel with: lightning-cli close 0 10% but then i realized that my peer node was offline. I tried again to close it with lightning-cli close 1 10% because i thought that I could force close this way and get my funds back because i wasn't sure when my peer would come 16:21 < Guest65> back online 16:22 < Guest65> This caused my funds to be sent to another address. Did i inadvertently get punished cause it looked like i was trying to steal funds? 16:22 < Guest65> and is there a way i can get my funds back? 16:51 < rusty> Guest65: The second one did a unilateral close which doesn't get to choose the destination, unfortunately. 16:51 < rusty> Guest65: however, you will still be able to spend the funds after the unilateral close timeout 16:52 < rusty> Guest65: listpeers peerid will show you... 16:59 < Guest65> thanks for the response rusty. In the status field, i'm seeing "ONCHAIN:2 outputs unresolved: in 123 blocks will spend DELAYED_OUTPUT_TO_US (hash:0) using OUR_DELAYED_RETURN_TO_WALLET" so i guess i just need to be patient :] 16:59 < rusty> Yep, 123 blocks of patience! 17:13 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning 17:14 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds] 17:15 -!- jarthur_ [~jarthur@2603-8080-1540-002d-45eb-dc20-018b-c9ba.res6.spectrum.com] has quit [Quit: jarthur_] 17:16 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 245 seconds] 18:44 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 19:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 19:17 -!- Guest48 [~Guest48@2601:184:4a7f:6b00:93ed:3064:25b:b11b] has joined #c-lightning 19:17 < Guest48> Hello 19:18 < Guest48> Small question if I may :) 19:19 < Guest48> When doing: lightning-cli listforwards 19:20 < Guest48> What will I see if the forward is failed because I don't have enough sats in the node that I need to forward the transaction to? 19:20 < Guest48> Will I see: 19:20 < Guest48> local_failed without the name of the next node? 19:21 < Guest48> or failed? 19:21 < Guest48> Thanks 19:22 -!- Guest48 is now known as Ligor 19:24 < ufotofu> c-lightning will by default create an offer that doesn't reveal the originating node ID right 19:24 -!- Guest65 [~Guest65@154.6.16.36] has quit [Quit: Client closed] 20:05 < ufotofu> anyone want to test out my offer and i'll send 100 sats back? 20:05 < ufotofu> lno1pqpsrp4qpgxxc6tzv4exzgr0venx2us7yzjx2aedg4skhakgg59xjxgahreulrx2r8leyyu8xh74782rdljdeuzqfsdy3ycd8turk3ctt4nlv6hes7hnwhnpe5vms0fyerdvzxuqq655jm46lk6m7m742rtf4zk4q3sjne46g6d5q26mqu9xlrc6h4hj6sc 20:21 < Ligor> Can I do it with 0.10? 20:39 < ufotofu> yeah with --experimental-offers 20:40 < rusty> ufotofu: it *does* contain node_id! See `lightning-cli decode lno1pqpsrp4qpgxxc6tzv4exzgr0venx2us7yzjx2aedg4skhakgg59xjxgahreulrx2r8leyyu8xh74782rdljdeuzqfsdy3ycd8turk3ctt4nlv6hes7hnwhnpe5vms0fyerdvzxuqq655jm46lk6m7m742rtf4zk4q3sjne46g6d5q26mqu9xlrc6h4hj6sc`: 20:41 < ufotofu> right but it's blinded? 20:42 < ufotofu> ah you're right it's there unblinded 20:43 < rusty> ufotofu: what lightning version? Looks like an old offer? 20:44 < ufotofu> v0.10.0 20:45 < rusty> ufotofu: cool, thought so. I'm about to release v0.10.1rc2 in a few hours, I recommend upgrading. Unfortunately the draft changed and broke offers, *and* AdityaSharma[m]1 just found a bug in -rc1 which means rc2 will break again... 20:45 < rusty> (This is the "experimental" part of the config option, sorry :( 20:46 < ufotofu> ok does that have some patches for blinding the node id? 20:47 < rusty> ufotofu: not yet. I mean, all the *code* exists, because we use blinding for the replies already (so they can't tell what node requested the invoice for the offer), but I'll open an issue for implementing it in the `offer` command. Thanks! 20:49 < ufotofu> ok ^_^ 20:54 < rusty> ufotofu: https://github.com/ElementsProject/lightning/issues/4689 21:28 < ufotofu> great! 23:23 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 245 seconds] 23:28 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning 23:34 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning --- Log closed Thu Jul 29 00:00:22 2021