--- Log opened Fri Jan 08 00:00:09 2021
00:01 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning
00:17 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 246 seconds]
00:18 -!- jonatack [~jon@104.254.90.195] has joined #c-lightning
00:20 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
00:39 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
00:47 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
01:12 -!- ShotokanZH [~ShotokanZ@unaffiliated/shotokanzh] has joined #c-lightning
01:12 < ShotokanZH> hi evryone!
01:14 < ShotokanZH> How do I transfer the BTC that I have in a lightning wallet to a regular BTC wallet?
01:21 < nibbier> ShotokanZH: if the funds are in a channel, you first have to close the channel to get them back on chain, then transfer them wherever you want. also there are services  that bridge for you, but they are not "standard" and not trustless etc.
01:22 < ShotokanZH> nibbier, the funds are in multiple channels, do you have any guide that shows how to send the btc to a regular wallet once the channels have been closed?
01:23 < nibbier> HelloShitty: RAID works on the block device level, so is file system agnostic. some file systems implement raid functionality on file system level also, btrfs, zfs i guess.
01:26 < nibbier> ShotokanZH: it's a simple call, https://lightning.readthedocs.io/lightning-txprepare.7.html https://lightning.readthedocs.io/lightning-txsend.7.html
01:27 < nibbier> ShotokanZH: also you can use spark wallet, which gives you a nice web gui for plenty of stuff
01:28 < ShotokanZH> nibbier, thank you <3
01:56 < ShotokanZH> nibbier, can i force-close a channel in less than 24h?
01:56 < ShotokanZH> like if i run `lightning-cli close id 1h` do you see any possible issue?
01:58 < nibbier> ShotokanZH: unilateraltimeout is on top of the closing time of the channel, which was negotiated while the peer was still online and is usually a day or so, some peers set it way higher iirc
01:59 < nibbier> it waits to see if the peer comes online again to close it in cooperation with the peer, which does then make the funds available quickly - but only if peer comes online and cooperates
02:00 < ShotokanZH> nibbier, so it's preferable to leave it to 48h and it will probably close in less time?
02:00 < ShotokanZH> (apparently the default it's 48h)
02:01 < nibbier> if you know thatthe peer is dead and won't come back, set it to 0. if you don't have knowledge about the peer, why it's offline etc.... your guess is as good as mine. 
02:03 < nibbier> I'd love to have easy statistics, each channel, how much uptime the last day, last week, last month, to make informed decisions on issues like that. guess there are monitoring solutions for that, maybe 1ml offers those stats? no idea
02:05 -!- kexkey [~kexkey@static-198-54-132-171.cust.tzulo.com] has quit [Ping timeout: 246 seconds]
02:13 < HelloShitty> hi
02:14 < HelloShitty> ShotokanZH: I think the default is 144 blocks just has darosior told me yesterday
02:14 < HelloShitty> there is a setting we can use to change it
02:14 < HelloShitty> --watchtime-blocks
02:17 < ShotokanZH> thanks
02:18 < ShotokanZH> the connected ones are answering rapidly
02:18 < HelloShitty> https://lightning.readthedocs.io/lightningd-config.5.html?highlight=watchtime
02:18 < ShotokanZH> i will monitor 1ml
02:18 < HelloShitty> But what is your goal?
02:20 < HelloShitty> My case was that I had a corrupted file in my bitoin core database and used the command -reindex to recover the atabase and it took a bit over 4 days to recover the entire database
02:20 < ShotokanZH> retrieving everything from my lightning wallet
02:20 < HelloShitty> I had channels open and when I got the node back up, only 2 channels were open
02:20 < HelloShitty> And are all peers online?
02:23 < ShotokanZH> HelloShitty, most of them, yes
02:24 < ShotokanZH> HelloShitty, i still have 2 channels with bits in there according to spark
02:24 < HelloShitty> An I'm not sure you're aware but after the channels close, all the funds will be available in regular BTC addresses which you can move aroun as you will
02:25 < HelloShitty> Because for each channel, only 2 transactions are on-chain. The one used to open/fund the channel and the one used to close/settle the channel
02:25 < HelloShitty> meaning they are normal BTC transactions
02:25 < HelloShitty> But I'm pretty sure you are aware of that
02:26 < ShotokanZH> please tell me that i will see the outputs gradually, because as of now spark says that I'm missing roughly 1.1BTC
02:26 < ShotokanZH> lol
02:26 < HelloShitty> ouch
02:28 < HelloShitty> I think you need add up the amount of BTC in each channel that is not as "CLOSED" state
02:29 < HelloShitty> To be honest, I still don't have deep knowledge about all rules that govern the opening and closing channels
02:29 < HelloShitty> And it's not easy to grasp them all just by reading code
02:30 < HelloShitty> An I'm also not sure if there are docs that explains in a chronological manner, what happens since de openning until the closure of the channel
02:35 < ShotokanZH> oh yeah it just appeared in the output lol
02:40 < HelloShitty> ok, ShotokanZH 
02:41 < HelloShitty> Do you know about 'listpeers', 'listfunds', etc, right?
02:42 < HelloShitty> Also, there is one plugin you can use, 'summary, that gives you a terminal style graphic of your open channels and sizes, etc
02:42 < ShotokanZH> HelloShitty, yep, i was managing those via a python script
02:58 < HelloShitty> ah ok
03:11 < ShotokanZH> HelloShitty, if i check on 1ml i see that there are still 2 channels open
03:11 < ShotokanZH> but if i run `listfunds` i see something like ~20 channels
03:11 < ShotokanZH> many with state: ONCHAIN
03:33 < HelloShitty> So, those I think are the closed ones
03:33 < HelloShitty> Because open channels don't have onchain transactions
03:34 < HelloShitty> I mean, I'm not sure I'm using the correct wording, but an open channel don't issue any transaction on the bitcoin blockchain
03:35 < HelloShitty> ShotokanZH: if I'm not mistaken
03:35 < HelloShitty> open channels have a filed in the JSON object called 'state'
03:35 < HelloShitty> the closed channels don't have that field
03:36 < HelloShitty> Can you confirm that on your node?
03:36 < HelloShitty> I'm using only the command line. I'm not using any front ends
03:36 < ShotokanZH> HelloShitty, "ONCHAIN" is the "state" key xD
03:37 < HelloShitty> I don't have any channel on that state
03:37 < HelloShitty> I have 2 open channels and they say:
03:38 < HelloShitty> "state": "CHANNELD_NORMAL"
03:38 < ShotokanZH> oh yep i confirm that
03:38 < ShotokanZH> now those are turning to CHANNELD_SHUTTING_DOWN
03:38 < ShotokanZH> so in a few hours i should be ok I guess
03:39 < HelloShitty> I think so
03:39 < HelloShitty> And if you sum the sats on those channels in that state
03:40 < HelloShitty> will they sum up to the amount you're saying you're missing?
03:48 -!- jonatack [~jon@104.254.90.195] has quit [Quit: jonatack]
03:49 -!- gleb [~gleb@178.150.137.228] has joined #c-lightning
03:52 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
03:56 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 240 seconds]
03:57 -!- jonatack [~jon@184.75.221.43] has joined #c-lightning
04:13 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
04:28 < gleb> Hi! I started playing with c-lightning, and lightnind dies with something like `txprepare: Failed to parse RPC JSON response '2021-01-08T12:11:06.848Z UNUSUAL plugin-bcli: bitcoin-cli -testn'` after a minute of operation
04:29 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
04:29 < gleb> This started to happen after I opened a channel and the funding transaction was locked I believe.
04:29 < gleb> Could anyone help?
04:34 < darosior> gleb: could you run with log-level=io and open an issue with the logs before the crash (or mail them if privacy concern..)
04:35 < gleb> Ah, I just looked at the full log, and the issue is with pruning. I managed to run c-lightning with pruned blocks up to this point, but now it seems not sufficient
04:35 < darosior> It'll output the actual invalid JSON response
04:36 < darosior> Hmm it does not seem immediately related to me: iirc the only issue with pruning is for historical scid lookup (which bitcoind pruned, but that's not fatal)
04:36 < gleb> UNUSUAL plugin-bcli: bitcoin-cli -testnet getblock 000000000000005648c2fa7aedb2946606e825c09c622b674072e8297f7c44a6 0 exited with status 1
04:37 < darosior> Ah ok :)
04:38 < darosior> Your lightningd couldn't sync to the tip that your bitcoind pruned the block. Once lightningd is synced, it's "safe" to run with pruning
04:38 < darosior> (if it doesn't goes backward on startup...)
04:41 < gleb> Is it possible that the issue was with my custom plugin?
04:41 < gleb> It's just not really intuitive where I should search for the error, but it seems so.
04:42 < gleb> Hm, no, not with the plugin.
04:47 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 260 seconds]
04:50 < gleb> daorsior: is blockheight=1902981 in getinfo sufficient to make sure lightningd synced the tip?
04:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
04:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
05:01 < HelloShitty> I also have a question about openning channels. Does it makes any difference between openning a single larger channel (as to liquidity  concerns) or openning multiple smaller channels?
05:01 < HelloShitty> Mostly, I'm interested in routing and obviously the fees one could collect
05:02 < HelloShitty> probably for routing is better a couple of smaller channels to different nodes, no?
05:04 < darosior> HelloShitty: these are questions difficult to answer otherwise than by "it depends". You should probably start by looking at https://github.com/ZmnSCPxj/clboss
05:06 < darosior> gleb: yes
05:22 < gleb> darosior: so apparently it is synced according to you, but logs says that lightningd tries to do getblock 1638132 every minute. I'm planning to just disable pruning and do full sync, hoping it would solve the problem. The actual problem I'm having is of course not these logs, but listnodes=[2] and not updating.
05:23 < gleb> according to getinfo*
05:32 < ShotokanZH> HelloShitty, sorry I missed your reply
05:32 < ShotokanZH> by the way, the "outputs" sum is correct, I think it includes the earned bits from the channels
05:33 < ShotokanZH> (0.04BTC, not bad!)
05:38 < darosior> gleb: then getblock 1638132 is because of gossip and is harmless. It should not crash your node.
05:38 < ShotokanZH> so, in theory everything that's in the "output" section is usable, and I can already retrieve those, right?
05:40 < darosior> ShotokanZH: yes
05:41 < darosior> gleb: if it's for testing you can also use an Esplora backend (even tho testnet sync is fast)
05:41 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:41 < ShotokanZH> darosior, but I still have two channels that are listed as "closing" with a positive number of btc in "channel_sat"
05:41 < ShotokanZH> that's weird, or I just almost doubled by btcs
05:47 < ShotokanZH> am i missing something? maybe the channel wasn't opened by me so the BTCs listed in there are actually just of the target? or I am just confused af.
05:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:54 < darosior> ShotokanZH: https://lightning.readthedocs.io/lightning-listfunds.7.html
06:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
06:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
06:24 < HelloShitty> darosior: if my node collects let's say 10k sats from forwarding several transcations, where are those 10k sats stored?
06:27 < darosior> In your channel
06:28 < darosior> (the incoming one)
06:28 < darosior> As a simple instance: you are B. A sends you 11sats you forwards 10sats to B. +11 incoming -10 outgoing overall +1
06:28 < darosior> 10sats to C
06:28 < darosior> *
06:30 -!- kexkey [~kexkey@static-198-54-132-123.cust.tzulo.com] has joined #c-lightning
06:41 < gleb> darosior: you're right, it was not crashing. But that's probably also answers why I wasn't getting listnodes filled.
06:41 < gleb> I wish I had enough cycles to go contribute to c-lightning to make it more intuitive, perhaps sometime I will :)
06:42 < HelloShitty> darosior: what about if that incoming channel was closed? In my case, I had someone with an open channel to me. I collected a few sats but that channel was closed in the meantime
06:42 < HelloShitty> where are those sats collected?
06:53 < darosior> Well if you collected >1sat they are now onchain
06:55 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
07:08 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
07:27 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
07:41 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
08:05 < HelloShitty> yes, but in which address?
08:44 -!- kexkey [~kexkey@static-198-54-132-123.cust.tzulo.com] has quit [Ping timeout: 264 seconds]
08:55 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
08:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
08:55 -!- vasild_ is now known as vasild
09:25 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds]
09:43 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
09:48 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection]
09:48 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
09:50 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection timed out]
09:50 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
10:12 -!- kexkey [~kexkey@static-198-54-132-109.cust.tzulo.com] has joined #c-lightning
11:22 < HelloShitty> darosior: but onchain in which address? And I have one other question
11:23 < HelloShitty> IF I want to move funds in one of my c-lightning node addresses, to some other address, where can I dump the PK for that address with my c-lightning node?
11:57 -!- jonatack [~jon@184.75.221.43] has quit [Quit: jonatack]
12:09 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
12:14 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 240 seconds]
12:16 -!- jonatack [~jon@213.152.162.89] has joined #c-lightning
12:56 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
13:09 -!- Ademan [~ademan@47.185.102.158] has joined #c-lightning
13:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
13:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
13:19 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Quit: %bye%]
13:19 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
13:43 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
13:45 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #c-lightning
14:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
14:59 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
15:13 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Read error: Connection reset by peer]
15:14 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
15:42 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
15:43 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
16:17 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Ping timeout: 240 seconds]
16:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
16:58 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
18:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:11 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving]
21:28 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
21:28 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
21:50 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
21:52 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
21:53 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
21:54 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
22:15 -!- user__ [~user@mail.deeplinkmedia.com] has joined #c-lightning
22:19 -!- user__ [~user@mail.deeplinkmedia.com] has quit [Client Quit]
23:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
23:01 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
23:01 -!- vasild_ is now known as vasild
23:32 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
23:34 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
--- Log closed Sat Jan 09 00:00:10 2021