--- Log opened Wed Oct 21 00:00:53 2020
00:06 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
00:17 -!- jonatack [~jon@37.165.188.225] has joined #c-lightning
01:00 -!- jonatack [~jon@37.165.188.225] has quit [Read error: Connection reset by peer]
01:31 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
01:32 -!- jonatack [~jon@37.165.188.225] has joined #c-lightning
01:34 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
01:36 -!- belcher_ is now known as belcher
01:45 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has joined #c-lightning
02:04 -!- kexkey [~kexkey@89.36.78.166] has quit [Ping timeout: 260 seconds]
02:13 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
02:48 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
02:49 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has quit [Quit: jasan]
02:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
02:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
03:06 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
03:07 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
03:07 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:11 -!- vasild_ is now known as vasild
03:12 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
03:12 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
03:24 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
03:29 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
03:29 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning
03:46 <@cdecker> Hadn't noticed since we tuned down the verbosity, but I should have the data to verify
03:48 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
04:03 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
04:04 -!- mrostecki_ is now known as mrostecki
04:24 -!- jonatack [~jon@37.165.188.225] has quit [Ping timeout: 260 seconds]
04:39 < m-schmoock> The tests/test_wallet.py recent changes on PSBT stuff fails 
04:39 < m-schmoock> specifically:
04:39 < m-schmoock> tests/test_wallet.py::test_fundpsbt
04:40 < m-schmoock> tests/test_wallet.py::test_utxopsbt
04:40 < m-schmoock> tests/test_wallet.py::test_sign_and_send_psbt
04:40 < m-schmoock>  bitcoin.rpc.JSONRPCError: {'code': -22, 'message': 'TX decode failed PSBT is not sane.: iostream error'}  
04:40 < m-schmoock> do I need a more recent bitcoind?
04:43 < zmnscpxj__> Maybe a *less* recent one? what version do you use? bitcoind RPC is notoriously unstable across versions sigh
04:43 < m-schmoock> v0.19.1.0-a28ea316e 
04:44 < zmnscpxj__> Using 0.20.1 myself.  hmm. lemme see
04:44 < m-schmoock> can you run these tests locally (just added on master recently)
04:45 < zmnscpxj__> but last I checked our CI uses even older, 0.16 I think?
04:45 < m-schmoock> dunno
04:50 <@cdecker> Travis uses 0.20.1
04:50 <@cdecker> It was recently updated to check the changes in the RPC interface
04:50 < zmnscpxj__> ah
04:50 < m-schmoock> let me check if it works with 0.20.1 but not with 0.19
04:50 < zmnscpxj__> not getting the same error as m-schmoock, instead got pyln.client.lightning.RpcError: RPC call failed: method: listcoinmoves_plugin, payload: {}, error: {'code': -32601, 'message': "Unknown command 'listcoinmoves_plugin'"}
04:59 < m-schmoock> cdecker: confirmed, the test run with 0.20.1 but not with 0.19.1 ... theres some interdependency.
04:59 < m-schmoock> worth invetigating?
05:06 -!- user____ [~user@mail.deeplinkmedia.com] has joined #c-lightning
05:09 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
05:15 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 244 seconds]
05:17 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
05:18 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning
05:20 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning
05:23 -!- user____ [~user@mail.deeplinkmedia.com] has left #c-lightning []
05:45 <@cdecker> Sure, having a regression is not a good look :-)
05:52 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has joined #c-lightning
06:02 -!- user____ [~user@mail.deeplinkmedia.com] has joined #c-lightning
06:04 -!- user____ [~user@mail.deeplinkmedia.com] has left #c-lightning []
06:09 -!- user____ [~user@mail.deeplinkmedia.com] has joined #c-lightning
06:11 -!- user____ [~user@mail.deeplinkmedia.com] has left #c-lightning []
06:16 -!- user____ [~user@mail.deeplinkmedia.com] has joined #c-lightning
06:18 -!- user____ [~user@mail.deeplinkmedia.com] has quit [Client Quit]
06:19 -!- user____ [~user@mail.deeplinkmedia.com] has joined #c-lightning
06:28 -!- user____ [~user@mail.deeplinkmedia.com] has left #c-lightning []
06:32 -!- user____ [~user@mail.deeplinkmedia.com] has joined #c-lightning
06:32 -!- user____ [~user@mail.deeplinkmedia.com] has quit [Client Quit]
06:39 < m-schmoock> cdecker: I added https://github.com/ElementsProject/lightning/issues/4144 to track it
06:44 -!- jonatack [~jon@109.202.107.5] has joined #c-lightning
06:50 -!- wxss [~user@mail.deeplinkmedia.com] has quit [Quit: leaving]
06:54 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
06:59 -!- wxss [~user@mail.deeplinkmedia.com] has left #c-lightning []
07:01 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
07:02 < darosior> m-schmoock, cdecker: i assumed it was expected but i'm not mistaken the PSBT call used in these tests are just not available in earlier versions of bitcoind
07:02 < darosior> But they are only used in tests
07:02 <@cdecker> Ah ok, thanks for checking though ^^
07:02 < darosior> And do not affect our MSBitcoindV
07:03 -!- wxss [~user@mail.deeplinkmedia.com] has left #c-lightning []
07:07 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
07:10 -!- wxss [~user@mail.deeplinkmedia.com] has quit [Client Quit]
07:11 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
07:14 < darosior> 🎉
07:15 < darosior> Will address your review in a followup asap
07:28 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds]
07:29 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
07:37 -!- wxss [~user@mail.deeplinkmedia.com] has quit [Quit: leaving]
07:38 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
08:09 < m-schmoock> darosior: keep me in the loop :D
08:10 < m-schmoock> really busy right now, but I'm very interested in this
08:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:56 < darosior> Sure! :)
09:44 -!- jonatack [~jon@109.202.107.5] has quit [Quit: jonatack]
09:44 -!- wxss [~user@mail.deeplinkmedia.com] has quit [Quit: leaving]
09:45 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
09:52 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
10:03 -!- jonatack [~jon@213.152.161.40] has joined #c-lightning
10:25 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
10:27 <@niftynei> you need 0.20.1 bticoind for the PSBT stuff
10:28 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Ping timeout: 240 seconds]
10:29 <@niftynei> relevant PR from bitcoin-core https://github.com/bitcoin/bitcoin/pull/19215
10:30 <@niftynei> will comment on issue also
10:49 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
11:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
11:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
11:12 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds]
11:13 < HelloShitty> Hello peeps. Someone oepened a channel with me of 100k sats. Shouldn't I be able to receive funds through this channel that was opened with me?
11:15 < HelloShitty> Hello peeps. Someone oepened a channel with me of 100k sats. Shouldn't I be able to receive funds through this channel that was opened with me?
11:15 < HelloShitty> soory the dupe
11:24 <@niftynei> yes! but your ability to utilize that channel to receive payments will depend on how much inbound liquidity *their* node might have
11:25 <@niftynei> in other words, if the person who's trying to pay you can't send payments down that channel then you wouldn't be able to receive payment
11:46 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
11:48 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
12:05 -!- jasan [~jasan@bband-dyn51.178-41-118.t-com.sk] has joined #c-lightning
12:05 < HelloShitty> niftynei: it's me. I'm trying to send a payment from one wallet on my phone
12:05 < HelloShitty> to my wallet in my c-lightning node, which is Spark-wallet
12:05 < HelloShitty> the first attempt, I got no payament in
12:06 < HelloShitty> despite the fact my wallet on my phone popping a message saying "In transit"
12:06 < HelloShitty> Then, I tried a secon time, some time later
12:06 < HelloShitty> and the payment went through
12:17 -!- jasan [~jasan@bband-dyn51.178-41-118.t-com.sk] has quit [Quit: Night here.]
12:22 <@niftynei> oh nice, sounds like you got it done
12:27 < HelloShitty> I guess so niftynei 
12:27 < HelloShitty> but I still got that problem earlier of bad gossip order in channel announcement
12:27 < HelloShitty> I'm not sure you're aware of this
12:28 < HelloShitty> darosior: created an issue on github a few days ago
12:28 < HelloShitty> however, connections to peers are not dropping while channels are open, I guess
12:29 < HelloShitty> And, I have one more question: can we observe all trasactions made from and into the node? I mean, off-chain transactions?
12:30 < HelloShitty> I would like to try to figure out and match the values I get from 'listfund' commands and what I see in Spark-Wallet. I want to understand the values
12:59 < az0re> HelloShitty: There is `listpays` and `listforwards`.  I guess that's what you want?
12:59 < HelloShitty> ok, I'll read those
13:06 -!- sword_smith [sword_smit@bitcoinfundamentals.org] has joined #c-lightning
13:07 < sword_smith> Does this mean that my node cannot find this other node, that they are not even connected? "gossipd: find_route: cannot find 02adbb6ef878b81697b68c4b33c41259e79177a05517948cbcf178673827ba1c94"
13:07 < sword_smith> gossipd: Trying to find a route from (me) to 02adbb6ef878b81697b68c4b33c41259e79177a05517948cbcf178673827ba1c94 for 833333000msat
13:07 < sword_smith> gossipd: REPLY WIRE_GOSSIPD_GETROUTE_REPLY with 0 fds
13:22 < az0re> sword_smith: I'm not sure, but I suspect it just means it can't find a route with 833ksats capacity.  Can you try a smaller amount?
13:23 < sword_smith> az0re: I also looked for this node on block explorers (same public key) and couldn't find it.
13:36 < az0re> Oh
13:36 < az0re> Then yeah, the node really can't be found
13:38 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
13:39 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
14:28 < HelloShitty> az0re: sword_smith: can it be offline?
14:29 < az0re> I don't think so, it would be a different error
14:29 < HelloShitty> o you know what means 'fdds' in the error message?
14:30 < az0re> HelloShitty: File descriptors?
14:30 < HelloShitty> ah ok
14:30 < HelloShitty> my keyboard is more and more stupid by the day
14:30 < az0re> Re: being offline -- Also, I get an error on https://1ml.com/node/02adbb6ef878b81697b68c4b33c41259e79177a05517948cbcf178673827ba1c94
14:31 < az0re> I know 1ml.com keeps records of all nodes it's seen
14:31 < HelloShitty> hum, ok
14:31 < HelloShitty> so, even if it was online, it still would show up there
14:31 < az0re> So this node appears simply not reachable by public routes
14:31 < az0re> Maybe they have a private channel with some node that sword_smith isn't connected to?
14:32 < HelloShitty> an that coul be the only route possible
14:32 < HelloShitty> making it impossible to route without going throught that node/channel
14:32 < HelloShitty> yeah, that actually is a very reasonable possible cause
14:33 < az0re> I think some more context on why the payment is happening (rebalance? actual payment?) and how sword_smith got that node ID would be helpful
14:33 < HelloShitty> indeed
14:40 < sword_smith> az0re: I got this invoice sent from a former colleague
14:46 < darosior> What's the name of the guy who did the postrgesql guide again ? Can not find it anymore
14:46 < sword_smith> lnbc8333330n1p0cnfjhpp5lrs366kj4q9wl782yzpku6hvzgepawxd8fuyk69f7zq0xxa002lqdqc2p5x7etwd9uzqurp09kk2mn5xqrrss9qtzqqqqqq9qsqsp58flvc4kuexx4c7xg5gt563ul8jt6skd64k6qvh6y02mjz23fkfdsrzjqwryaup9lh50kkranzgcdnn2fgvx390wgj5jd07rwr3vxeje0glcllmcvuuz0wsujsqqqqlgqqqqqeqqjqq9u5w26ua4puyx0xzlrn4hght3nz4y467h08wa7nwwhuhu9qeggppswtxtkqwjcz7mlq63g9hrfupxamhn8tyyanj7y99eysptr2c7gq8hrq35
14:49 < darosior> Got it! That's gabridome and the link is https://github.com/gabridome/docs/blob/master/c-lightning_with_postgresql_reliability.md
14:49 < sword_smith> The description for this invoice is "Phoenix payment".
14:53 -!- kexkey [~kexkey@37.120.205.214] has quit [Quit: Scaling pentatonically]
14:55 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
15:08 < az0re> sword_smith: So it looks to me like your former colleague has only a private channel to ACINQ (pubkey 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f)
15:08 < az0re> I'm not sure exactly how payment works here, so take what I say with a grain of salt
15:09 < az0re> But 1. Do you have a channel to ACINQ?  Or 833ksat of capacity to ACINQ?
15:09 < az0re> 2. The short channel id suggested, "16742503x3680186x7316", looks very wrong to me.  Maybe this is something to do with it being a private channel?
15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
15:15 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
15:17 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
15:41 < blockstream_bot> [Tim Ho, Blockstream] Question, how do I know if a channel closing is complete and funds are back in my wallet? I ran listfunds and I see some channels in state of `AWAITING_UNILATERAL`, `CHANNELD_SHUTTING_DOWN`, and `CLOSINGD_COMPLETE`.
15:45 < az0re> Tim Ho: in `listfunds`, you can see your UTXOs in the "outputs" field as an array of objects.  Each object has a "status" field (in addition to "txid", "output", "value", etc.) that will be "confirmed" when the funds are on the chain.
15:48 < blockstream_bot> [Tim Ho, Blockstream] They are all "confirmed" but I don't know if that makes sense. Because I just started a forced unilateral close and I think that takes many blocks to finalize, right?
15:53 < az0re> Did you look up the txid on a block explorer?
15:54 < blockstream_bot> [Tim Ho, Blockstream] You mean the opening funding_txid ?
15:54 < az0re> I don't think it takes many blocks to finalize a unilateral close
15:54 < az0re> I meant the commitment txid
15:54 < blockstream_bot> [Tim Ho, Blockstream] Where do I find that?
15:54 < az0re> Once it gets on the chain, that should be it (but maybe I'm wrong)
15:56 < blockstream_bot> [Tim Ho, Blockstream] Oh maybe it's this "close_to_addr" part in the listpeers output
15:56 < az0re> Not sure where to find it
15:56 < az0re> Yeah look in listpeers - channels
15:56 < az0re> errrr listpeers - peers - channels
15:56 < blockstream_bot> [Tim Ho, Blockstream] Yeah it says 0 confirmations for the bc1... address, one with CHANNELD_SHUTTING_DOWN.
15:58 < blockstream_bot> [Tim Ho, Blockstream] I wonder how it calculates fees for the closing transaction.
15:59 < blockstream_bot> [Tim Ho, Blockstream] ```               "status": [
15:59 < blockstream_bot>                   "ONCHAIN:Tracking our own unilateral close",
15:59 < blockstream_bot>                   "ONCHAIN:3 outputs unresolved: in 2014 blocks will spend DELAYED_OUTPUT_TO_US (0b3f4bf8407c14ee192452cd81c7ea7154c4ae0b3753f426c32a22fb72a16cfe:0) using OUR_DELAYED_RETURN_TO_WALLET"
15:59 < blockstream_bot>                ],```
15:59 < blockstream_bot> [Tim Ho, Blockstream] 2,014 blocks ~335 hours ~13 days
16:00 < az0re> Never had that happen :)
16:00 < az0re> Every time I've done a unilateral close or had one done to me there was no delayed output
16:01 < az0re> Maybe you had some HTLCs in flight?
16:01 < blockstream_bot> [Tim Ho, Blockstream] Not sure. None that I know of.
16:01 < az0re> Maybe look in `listforwards` near the end.  Maybe there is some interesting message there.
16:03 < az0re> WRT fee choices for closing, look in plugins/bcli.c
16:04 < blockstream_bot> [Tim Ho, Blockstream] I'm not sure what to look for. I see wire_temporary_channel_failure and other failed ones
16:04 < az0re> I think they're set around lines 502-504, and estimated elsewhere in that file
16:05 < az0re> Filter them out so you're only looking at forward attempts from/to the channel you unilaterally closed
16:05 < blockstream_bot> [Tim Ho, Blockstream] No reference to the channel in listforwards
16:06 < az0re> Well, iunno :)
16:06 < blockstream_bot> [Tim Ho, Blockstream] Oh well, I'll check back in 2 weeks to see what happpens
16:06 < az0re> Not sure what's going on there, maybe someone else can enlighten us
16:36 -!- kexkey [~kexkey@37.120.205.214] has quit [Quit: Scaling pentatonically]
16:37 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
16:40 -!- kexkey [~kexkey@37.120.205.214] has quit [Client Quit]
16:52 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
16:57 -!- kexkey [~kexkey@37.120.205.214] has quit [Quit: Scaling pentatonically]
16:59 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
17:00 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
17:25 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 264 seconds]
17:33 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
17:33 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
17:36 -!- kexkey [~kexkey@37.120.205.214] has quit [Client Quit]
17:40 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
17:55 -!- kexkey [~kexkey@37.120.205.214] has quit [Quit: Scaling pentatonically]
18:31 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning
19:08 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
19:08 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
19:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
19:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
21:02 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
21:02 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
22:04 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 272 seconds]
22:29 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
23:41 -!- jonatack [~jon@213.152.161.40] has quit [Ping timeout: 256 seconds]
23:43 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
23:52 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
--- Log closed Thu Oct 22 00:00:54 2020