--- Log opened Sun Feb 10 00:00:45 2019
01:13 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has joined #c-lightning
01:15 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Remote host closed the connection]
01:18 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
01:19 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
01:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
02:24 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
02:44 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:54 <@cdecker> thorie: were the channels in state CHANNELD_NORMAL?
02:56 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds]
03:00 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
03:17 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:23 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.3]
03:46 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
04:22 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
04:26 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Remote host closed the connection]
04:27 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #c-lightning
06:54 < m-schmoock> Hey, my daemon still shows a channel in `listfunds`. but the funding has been spend. I cant close the channel as the cli tells me channel not found or peer has no active channels. 
06:54 < m-schmoock> are finished channels still listed in listfunds and the funding spend seend was actually my own daemon?
06:57 < m-schmoock> how can I check if the channel was closed correctly?
07:23 <@cdecker> What does `listpeers` show? It may still be closing, and we keep track of channels for up to 100 blocks even after close succeeds (just in case we have a reorg)
07:25 < m-schmoock>             "ONCHAIN:Tracking our own unilateral close", 
07:25 < m-schmoock>             "ONCHAIN:1 outputs unresolved: in 44 blocks will spend DELAYED_OUTPUT_TO_US (54940e4613c70588b1e5e54428ae472efe4b6ff31f8ac7fae9f2c834ecf3a9b7:0) using OUR_DELAYED_RETURN_TO_WALLET"
07:25 < m-schmoock> seems like the spend did go to my own wallet
07:26 < m-schmoock> I can see in a blockexplorer that it was not spend yet, but my clightning does not schow it as avalable funds...
07:26 < m-schmoock> yes i know, a lot of money for funny testing :D
07:26 <@cdecker> Yep, that channel is still being listed in listfunds until we forget it. We could probably be smarter in listfunds
07:26 < m-schmoock> nvm. a status field would be good in listfunds
07:27 <@cdecker> The funds are not yet returned to the wallet since they are on a delayed output
07:27 <@cdecker> In 44 blocks they'll get swept by c-lightning automatically and then they're available to you again
07:28 < m-schmoock> so anyway, the funds were supposedly released to one of my addresses. how can I check this? as you can see its already 400+ confirms
07:28 < m-schmoock> https://blockchair.com/bitcoin/address/bc1q8e7eslst8mqdfwes8jcwv77n6nlvajxwfyvckcc547ge4upphd6qrt586c
07:30 < m-schmoock> since they are unspend, I should see them in listfunds in outputs somewhere. but they are not. or amy I wrong?
07:31 < m-schmoock> can I safely do a `dev-rescan-outputs` ?
07:42 < thorie> @cdecker which channels? I have a variety of states now
07:52 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:11 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
08:26 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
08:40 <@cdecker> thorie: The failure was referring to channel 556292x777x1 (with peer 038df0bd2fad1bfe42d177f18ea5e33543e2b855ef369d06bd94b81d2c87187c82) I assumed that peer was not online at the time you tried to pay
08:40 <@cdecker> Did you try again afterwards?
08:41 <@cdecker> m-schmoock: `dev-rescan-outputs` is always safe (unless you have a channel pending confirmation in which case it might results in the funds being marked as unspent and may be used for future fundings or withdrawals, but no real issue)
08:44 < m-schmoock> im just waiting the 40 blocks. if issue persists, we need some debugging. at least my daemon is not able to detect that it does have is unilateral close tx already onchain for over 400 (hundrets) blocks and he still waits for another 44
08:44 < m-schmoock> there is somewhere a bugged condition
08:45 < m-schmoock> cdecker: since you are here, maybe you can answer me: https://github.com/ElementsProject/lightning/issues/2316#issuecomment-462140327
09:04 <@cdecker> m-schmoock: that address (bc1q8e7eslst8mqdfwes8jcwv77n6nlvajxwfyvckcc547ge4upphd6qrt586c) is a multi-sig output that still needs to be claimed (in 40 blocks according to your node). They'll automatically be forwarded once more to a wallet address
09:05 <@cdecker> We don't show them in your outputs since they can't be unilaterally be spent in their current state, but after the move they will be.
09:07 <@cdecker> Replied to #2316, good observations btw
09:24 < m-schmoock> thx
09:25 < m-schmoock> should I change the fee_base type to u32 as I am already changing stuff?
09:26 < m-schmoock> why was the negative routing fee abandoned? Sounds like a carefully to handle but nice feature. Is it abandoned by BOLT spec or by clightning implementation?
09:32 <@cdecker> We dropped it at the spec level, turns out that negative fees are a really blunt instrument to encourage channel rebalancings (require broadcast of a channel_update, basically promises money to other people that we don't have control over, and may still not result in the channel being rebalanced)
09:33 <@cdecker> Active rebalancings (routing in a cycle) is way more direct and gives you all the control you need, at a potentially lower price
09:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
10:02 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
10:19 < thorie> @cdecker I don't understand "with peer 038df..." that is my node ID
10:20 < thorie> I've tried many times afterwards, it's still giving me the same error
10:20 < thorie> "No connection to first peer"
10:53 < thorie> Why is the first peer myself?
10:54 -!- ctrlbreak_MAD is now known as ctrlbreak
10:54 < ctrlbreak> Ummm... this normal?  
10:54 < ctrlbreak>       "global_features": "",
10:54 < ctrlbreak>       "local_features": "808082",
10:54 < ctrlbreak>       "globalfeatures": "",
10:54 < ctrlbreak>       "localfeatures": "808082",
10:58 < molz> what are those features for, ctrlbreak ?
10:58 < ctrlbreak> heh... I haven't a clue :-S
11:00 < molz> would be nice if c-lightning can separate the lurking peers from peers who have channels with your node
12:48 < t0mix> my lightning daemon died. I don't know why, in log I see:
12:48 < t0mix> lightning_gossipd(11366): Could not fit scids for single block 17302728
12:48 < t0mix> lightning_gossipd(11366): FATAL SIGNAL 6 (version v0.6.3)
12:48 < t0mix> lightning_gossipd(11366): STATUS_FAIL_INTERNAL_ERROR: FATAL SIGNAL
12:48 < t0mix> anybody saw that already?
12:54 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
13:03 < t0mix> molz, ctrlbreak, I looked for features here https://github.com/lightningnetwork/lightning-rfc/blob/master/09-features.md
13:03 < t0mix> seems there's a lot written about features. although, I don't get it (yet).
13:36 < molz> t0mix, not sure what you mean
13:39 < molz> ah those local and global features.. i think i can live without them
13:39 < molz> they just make it more difficult to look at the list of channels
13:44 < t0mix> yup, those one
14:57 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:02 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
15:03 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:03 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
16:04 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:22 < molz> t0mix, can you connect to this node:  02df5ffe895c778e10f7742a6c5b8a0cefbe9465df58b92fadeb883752c8107c8f@35.232.170.67:9735
17:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
17:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:24 < molz> ah the port is closed
17:40 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
17:43 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:47 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
17:49 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:53 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
17:57 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:59 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
18:05 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:12 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:20 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:26 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
18:32 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:37 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds]
18:40 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:44 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:50 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:53 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 240 seconds]
18:57 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
19:01 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
19:15 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:17 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:25 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:26 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:30 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
19:34 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:39 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:46 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:50 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:56 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:59 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
20:00 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:01 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:04 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
20:08 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
20:08 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:12 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:13 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:17 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:26 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
20:27 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
20:38 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:41 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:48 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:51 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:55 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
20:59 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
21:06 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
21:06 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
23:16 -!- deusexbeer [~deusexbee@093-092-176-118-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
23:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
--- Log closed Mon Feb 11 00:00:46 2019