--- Log opened Mon Apr 01 00:00:32 2019
00:21 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
00:21 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
00:22 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 268 seconds]
00:27 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
00:28 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
01:18 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
01:41 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
01:41 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
01:42 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
01:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
01:50 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:51 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
03:23 -!- rafalcpp_ is now known as rafalcpp
03:57 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
04:12 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:26 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has quit [Excess Flood]
04:44 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has joined #c-lightning
04:46 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has quit [Read error: Connection reset by peer]
04:46 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has joined #c-lightning
06:25 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
06:56 < m-schmoock> cdecker: for the channel_accecpt_hook (issue 
06:57 < m-schmoock> cdecker: for the channel_accecpt_hook (https://github.com/ElementsProject/lightning/issues/2483) would it be feasible to implement it synchroniously?
06:57 < m-schmoock> meaning once registered lnd will wait for a plugin response before accepting the channel towards the peer?
07:04 < m-schmoock> sry, just found out the only hook peer_connected IS also just synchronious
07:05 < m-schmoock> will do it like this
08:41 < blockstream_bot> [ecurrencyhodler, Blockstream] Hey friends.  The Bolt-A-Thon conference schedule (April 5-7) has been finalized!  We’ll be featuring speakers like Blockstreams very own Rusty Russell.  Webinar tickets are only $10 per session.  You can also participate in the hackathon for a chance to win 0.3 BTC.  Hope you check it out!  https://www.reddit.com/r/Bitcoin/comments/b83fy5/boltathon_finalized_conference_schedule_apr
09:05 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:17 <@cdecker> Yep, hooks by definition are synchronous, but other channels may proceed :-)
11:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:00 -!- niftynei [~niftynei@104.131.77.55] has joined #c-lightning
12:00 -!- mode/#c-lightning [+o niftynei] by ChanServ
13:27 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has quit [Excess Flood]
13:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
13:50 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
13:58 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:07 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:11 -!- Joel123_ [808a4171@gateway/web/freenode/ip.128.138.65.113] has joined #c-lightning
14:18 < Joel123_> Is there a simnet for c lightning or something like it?
14:21 <@cdecker> Joel123_: there's regtest
14:22 < Joel123_> Thanks. I am going to run some nodes on localhost and didn't want to download the testnet blockchain.
14:28 < fiatjaf> can a payment be marked as 'failed' in listpayments and then suddenly change to 'complete'?
14:28 < fiatjaf> because that just happened
14:34 < fiatjaf> see the two outputs here: https://www.pastery.net/fsargw+uffgun/#fsargw
14:34 < fiatjaf> one taken from my program logs where I poll listpayments until I get 'failed' and then cancel the outgoing transaction and refund the user balance.
14:34 < fiatjaf> the other taken from the lightning-cli output now, when the user notified me of the bug.
14:35 < fiatjaf> maybe I should open an issue
14:41 < fiatjaf> https://github.com/ElementsProject/lightning/issues/2521
14:45 -!- Joel123_ [808a4171@gateway/web/freenode/ip.128.138.65.113] has quit [Ping timeout: 256 seconds]
15:06 -!- Joel123 [808a41cb@gateway/web/freenode/ip.128.138.65.203] has joined #c-lightning
15:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
15:12 -!- Joel123 [808a41cb@gateway/web/freenode/ip.128.138.65.203] has quit [Ping timeout: 256 seconds]
15:23 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
15:57 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:14 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:18 <@niftynei> rusty, thanks for the reviews. i'm working on redoing the rfc's csv extraction script atm, i'll update them to reflect it before i merge them in :)
16:19 <@niftynei> out of curiosity, what's the rationale for favoring 'bare fields' over returned structs?
16:21 < rusty> niftynei: it works better with refactoring.  If you add a new field, all callers break.  If you add a new field to a struct, that doesn't happen.
16:23 <@niftynei> and in the case, having all the callers break is desired behavior?
16:24 <@niftynei> that's pretty smart, but it gets so gross for these TLV things.
16:24 <@niftynei> the nice thing about structs for optional messages is that it buckets all the optionality up
16:25 <@niftynei> like, it's super easy to check if a field was included based on whether or not it got added to the struct
16:38 < rusty> niftynei: yes, and handing 10 parameters is kinda gross.  But then, having 10 options is kinda inherently gross...
16:46 <@niftynei> hehehe
16:46 <@niftynei> i guess it kind of depends on how 'fleshed out' you see the sub-structs in a tlv huh
16:47 <@niftynei> i was envisioning them as (possibly?) being fully fleshed out messages in their own right, with multiple fields per each one
16:48 <@niftynei> basically a 'subtype' but buried inside the tlv field. in that case having a struct per is sensible
16:51 <@niftynei> otoh if each of the 'tlv messages' is really just a single optional field, it really doesn't warrant so much struct infrastructure
16:51 <@niftynei> 'infra-struct-ure' :)
16:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:02 -!- StopAndDecrypt_ [~StopAndDe@96.44.189.226] has joined #c-lightning
17:02 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds]
17:05 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
17:14 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
23:12 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning
23:26 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
--- Log closed Tue Apr 02 00:00:33 2019