--- Log opened Tue Apr 30 00:00:59 2019
00:35 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
01:22 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
02:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
03:04 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:09 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
06:12 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
06:14 < bitonic-cjp> I have a feeling that UTF-8 still isn't handled correctly in pylightning.
06:14 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 246 seconds]
06:14 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
06:31 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:01 < m-schmoock> My logs is full of "Broadcasting tx 020000000001013a316044a102039b... : 25 error code: -25?error message:?Missing inputs?"
07:01 < m-schmoock> what does it mean?
07:11 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 268 seconds]
08:27 -!- cubancorona2 [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #c-lightning
08:27 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
08:27 -!- booyah [~bb@193.25.1.157] has joined #c-lightning
08:30 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Ping timeout: 246 seconds]
08:33 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
08:33 -!- booyah [~bb@193.25.1.157] has joined #c-lightning
09:02 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:27 -!- cubancorona2 [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Quit: Leaving]
09:29 <@cdecker> That usually just means that you are trying to close a channel, but your peer has already broadcast the same tx
09:30 <@cdecker> Alternatively it also means that your node just tries to broadcast a tx that already is in the mempool but not yet confirmed
09:32 < m-schmoock> so nothing to worry, right=?
09:34 <@cdecker> Shouldn't be anything serious, it
09:34 <@cdecker> it's mostly debug output
09:34 < m-schmoock> the affected channel told: "to_us_msat" : "404638117msat"
09:34 < m-schmoock> but I only have 317878 sat in my listfunds
09:35 <@cdecker> I think listfunds already removes an eventual fee which may be a bit weird
09:36 <@cdecker> That's a huge fee in that case though
09:36 < m-schmoock> im not sure what excatly happend
09:36 < m-schmoock> nvm
09:37 < m-schmoock> several times 'newaddress'  and then dev-rescan-outputs   should recover anything if theres somethign missing. right ?
09:38 <@cdecker> Yep
09:38 < m-schmoock> kk. gotta go. thx
09:39 <@cdecker> Unless the the output was from a unilateral close on the remote end (that has a secret mixed in which is an annoying quirk)
09:39 < m-schmoock> "ONCHAIN:Tracking our own unilateral close"   ""ONCHAIN:All outputs resolved: waiting 71 more blocks before forgetting channel"
09:40 < m-schmoock> or are funds then released in 71 blocks ??
09:43 <@cdecker> They should be back already, we just delay removing the DB entry by 100 blocks for safety
09:44 < m-schmoock> aaahh. then I think my TX is stuck in mempool
09:46 < m-schmoock> the scratch_txid of that channel has already 366 confirms (7d12bb9d0f7bed2c3dbbefeba45887b64cd168aebc26657cb609919e251d4891)
09:46 < m-schmoock> my daemon still tries to Broadcasting tx 0200000000010191481d259e... rror message:?Missing inputs
09:51 < m-schmoock> ah, the first 4 outputs of 7d12bb9d0f7bed2c3dbbefeba45887b64cd168aebc26657cb609919e251d4891 are still script outputs
09:52 < m-schmoock> I think it more or less adds up :D 
09:53 < m-schmoock> I think my node does fishy stuff: https://blockstream.info/tx/7d12bb9d0f7bed2c3dbbefeba45887b64cd168aebc26657cb609919e251d4891
09:56 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
09:58 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning
09:58 < m-schmoock> rebooted
10:03 < m-schmoock> still 55 "Broadcasting tx" in log after daemon restart
10:03 < m-schmoock> is this still 'normal' ?=
10:07 < m-schmoock> *its only 30 times Broadcasting tx without input
10:32 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
10:41 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
11:10 < m-schmoock> i think it retries to rebroadcast the failng TX each time a block is found
11:12 < m-schmoock> -think. it does rebroadcast 30 times failing TX (missing input) each time a block is found
11:13 < m-schmoock> and those 30 times constist of 2 different TX that are (tried) broadcasted 15 times each
11:46 <@cdecker> Yep, we're not (yet) very clever about TX conflicts, hence we just try to rebroadcast at every opportunity
12:09 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
12:10 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds]
12:10 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
12:11 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
12:26 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
12:46 < m-schmoock> cdecker: how will the problem go away? I rescanned and consolidated all my utxo into a single new address but it still prints these messages each block. 
12:46 < m-schmoock> im not 100% sure if I have all my funds, but its not much thats missing in any case
12:46 < m-schmoock> still the logs are annoying and there must be a reason they persist
13:02 -!- berndj-blackout [~berndj@azna.co.za] has joined #c-lightning
13:03 -!- berndj [~berndj@azna.co.za] has quit [Ping timeout: 264 seconds]
13:04 -!- berndj-blackout is now known as berndj
13:57 <@cdecker> Nah, we just like writing logs :-)
14:11 < m-schmoock> :D
14:14 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
14:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:02 < m-schmoock> cdecker: so, i decoded the TX my nodes wallet constantly retries to broadcast. turned out my own nodes wallet already did spend this, which is why it cant validate (missing input). Good thing, nodbody lost any money. bad thing: my logs are being spammed :D
15:04 < m-schmoock> I maybe need some sqlite magic to fix it...
15:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
15:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:31 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
15:39 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:03 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
17:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:25 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
17:42 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
17:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
19:30 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
19:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
20:13 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
20:14 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
21:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
21:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
--- Log closed Wed May 01 00:00:00 2019