--- Log opened Wed Oct 28 00:00:59 2020
00:07 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
00:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
00:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
01:55 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning
02:05 -!- kexkey [~kexkey@static-198-54-132-126.cust.tzulo.com] has quit [Ping timeout: 264 seconds]
02:25 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
02:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
02:35 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
02:35 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
02:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
03:08 -!- 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:31 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has joined #c-lightning
03:31 < jasan> Good morning! Thank you niftynei for the note about Changelog-None. Are there any more magic keywords /me should use?
03:39 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has quit [Quit: leaving]
03:40 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning
03:41 < m-schmoock> jasan: check doc/STYLE.md line 217
04:02 < jasan> m-schmoock: thanks!
04:04  * jasan is reading it all
04:51 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
04:54 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
05:15 -!- jonatack [~jon@213.152.161.239] has quit [Ping timeout: 260 seconds]
05:39 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
05:39 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning
05:58 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has quit [Quit: jasan]
06:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
06:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
06:24 -!- jonatack [~jon@109.232.227.138] has joined #c-lightning
06:33 -!- jonatack [~jon@109.232.227.138] has quit [Ping timeout: 260 seconds]
06:34 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
07:01 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
07:19 -!- jonatack [~jon@213.152.162.154] has joined #c-lightning
07:28 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
07:30 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
07:41 -!- jonatack [~jon@213.152.162.154] has quit [Quit: jonatack]
07:46 -!- jonatack [~jon@213.152.161.133] has joined #c-lightning
07:55 -!- belcher_ is now known as belcher
08:29 -!- kexkey [~kexkey@static-198-54-132-142.cust.tzulo.com] has joined #c-lightning
08:32 -!- michaelfolkson2 is now known as michaelfolkson
08:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
08:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
08:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
09:22 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.9]
09:34 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
09:53 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
10:07 -!- ksedgwic [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal]
10:17 <@cdecker> HelloShitty c-lightning doesn't keep signed commitment transactions around exactly to prevent users from accidentally cheating, however you can ask your node to sign the last commitment transaction, store it somewhere and then broadcast it at a later point in time (don't to it though, since you will lose money!)
10:23 -!- ksedgwic [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has joined #c-lightning
10:43 < grubles> is there anything i can do on my end to help troubleshoot the "bad file descriptor" error i'm running into 
10:53 <@cdecker> Any idea which process gives you that error? (not familiar with *bsd)
10:54 <@cdecker> One thing that might be worth trying is to strace lightningd (bsds seem to have an equivalent called truss to traces system calls)
10:55 <@cdecker> `truss -f lightningd` should trace both the main process and any subprocess (will cause a lot of output, so redirect or `tee` to a file so we can filter it later)
11:08 < grubles> ok i'll give that a shot
11:09 < grubles> i believe it's connectd giving the error?
11:09 < grubles> -connectd
11:09 < grubles> : Failed connected out: 34.239.230.56:9735: Connection establishment: Bad file descriptor. 
11:25 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds]
11:27 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
11:29 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
11:41 < grubles> ok the ktrace (openbsd's strace) file is 135 MB
11:43 < grubles> 42.7M compressed. not bad. where should i upload this?
11:55 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
11:55 -!- midnight_ is now known as midnight
11:56 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
12:07 -!- berndj [~berndj@ns2.linksynergy.co.za] has quit [Read error: Connection reset by peer]
12:08 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Ping timeout: 240 seconds]
12:11 -!- berndj [~berndj@ns1.linksynergy.co.za] has joined #c-lightning
12:34 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has joined #c-lightning
12:34 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has quit [Client Quit]
13:00 -!- MasterdonX [~masterdon@titan.pathogen.is] has quit [Ping timeout: 256 seconds]
13:01 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
13:03 -!- MasterdonX [~masterdon@titan.pathogen.is] has joined #c-lightning
13:04 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
13:07 -!- willcl_ark_ [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
13:08 -!- MasterdonX [~masterdon@titan.pathogen.is] has quit [Ping timeout: 264 seconds]
13:08 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
13:21 -!- MasterdonX [~masterdon@titan.pathogen.is] has joined #c-lightning
13:25 -!- MasterdonX [~masterdon@titan.pathogen.is] has quit [Read error: Connection reset by peer]
13:26 -!- MasterdonX [~masterdon@89.187.168.52] has joined #c-lightning
13:48 -!- masterdonx2 [~masterdon@titan.pathogen.is] has joined #c-lightning
13:49 -!- MasterdonX [~masterdon@89.187.168.52] has quit [Ping timeout: 260 seconds]
13:56 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
13:56 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has joined #c-lightning
14:31 < HelloShitty> cdecker: az0re: so those commitment transactions that are in between the funding and the closing transaction, also have a bitcoin network valid hash that can actually be broadcasted to the onchain network?
14:32 < az0re> Yes
14:32 < HelloShitty> hum, ok
14:33 < az0re> The point is the parties always maintain valid, signed transactions to settle the chanbnel "fairly"
14:33 < HelloShitty> I understand
14:33 < az0re> They just choose not to broadcast them
14:33 < HelloShitty> but that arises another question
14:34 < HelloShitty> If those in between transactions should not be ever boradcasted to the bitcoin network, couldn't they 'happen' in a different format so that it would be impossible to broadcast them ?
14:35 < az0re> Well, they *can* be broadcast to the network.  That would unilaterally close the channel.
14:35 < HelloShitty> And only the funding and the closing (or whatever is the correct term) transactions woul be in a format compatible with the bitcoin network
14:35 < HelloShitty> yes, but that could be a "lie" about the true/real channel balance
14:36 < az0re> Each party needs to maintain the ability to unilaterally close the channel and recover their funds at any time, so they always need to have a valid signed transaction that they can broadcast in order to do that.
14:36 < HelloShitty> Anyways, I don't want to discuss this because I'm sure there are a thousand reasons that things are the way they are
14:37 < HelloShitty> But that transaction is supposed to be always the last one, right? Only the last one is valid, correct?
14:37 < HelloShitty> At least, is what I've already read somewhere
14:38 < HelloShitty> that all in between transactions are made kinda invalid by the latest one, so that there is "no chance", neither by accident or on purpose that those older transactions can be broadcasted
14:40 < az0re> They are not made invalid.  Instead there is a revocation key that is kept secret for the latest commitment transaction.  When the parties process a payment and update their channel balances (and so sign a new commitment transaction), they exchange those revocation keys.  Commitment transactions can be revoked within a certain number of blocks after the commitment transaction was confirmed.  It is up to the party being cheated to use the known 
14:40 < az0re> revocation key to construct a revocation transaction that takes all funds (including the cheater's) and gives them to the revoker and broadcast it within that time limit.
14:45 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
14:45 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning
14:46 -!- kristapsk_ is now known as kristapsk
14:56 < HelloShitty> hum, ok. I think I'm still missing some bits in the middle of the whole proccess, but I think I'll get there in time
14:59 -!- Netsplit *.net <-> *.split quits: @cdecker
14:59 -!- mode/#c-lightning [+o cdecker] by ChanServ
14:59 -!- Netsplit over, joins: cdecker
15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:13 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
16:04 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
16:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
16:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
16:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
16:56 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
18:06 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
18:07 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has joined #c-lightning
19:00 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-mxlomfeqruovckob] has quit [Ping timeout: 272 seconds]
19:00 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-xsmtlxhhfuereiur] has joined #c-lightning
19:48 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
21:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
23:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
23:44 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
23:51 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds]
--- Log closed Thu Oct 29 00:00:00 2020