--- Day changed Sat Jan 27 2018
00:07 < nothingmuch> cubancorona: a functional blockstream node
00:08 < cubancorona> lol     
00:08 < nothingmuch> (multiple people have had issues with their node)
00:08 < nothingmuch> so much for hub and spoke conspiracy theories =/
00:15 < cubancorona> it may be natural for the network connections to follow a power law distribution
00:18 < cubancorona> should be easy to route around monopolistic hubs
00:19 < cubancorona> good reading: https://www.amazon.com/Linked-Science-Networks-Albert-laszlo-Barabasi/dp/0738206679
00:22 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
00:48 -!- Packman [1812c90a@gateway/web/freenode/ip.24.18.201.10] has quit [Ping timeout: 260 seconds]     
01:02 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 264 seconds]     
01:04 -!- kexkey [~kexkey@173.209.61.61] has quit [Ping timeout: 268 seconds]     
01:53 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds]     
02:32 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
02:34 -!- moctost_ [~moctost@209.95.50.117] has joined #c-lightning     
02:36 -!- moctost [~moctost@173.244.200.120] has quit [Ping timeout: 256 seconds]     
02:36 -!- moctost_ is now known as moctost     
02:38 -!- moctost [~moctost@209.95.50.117] has quit [Client Quit]     
02:38 -!- moctost [~moctost@209.95.50.117] has joined #c-lightning     
03:31 -!- mudley [~mudley@Mail.stienstra.me] has joined #c-lightning     
04:34 -!- mudley [~mudley@Mail.stienstra.me] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]     
04:35 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Remote host closed the connection]     
04:35 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
04:40 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 264 seconds]     
04:48 < mn3monic> mmh     
04:48 < mn3monic> lightningd is _stressing_ bitcoind a lot, with a big amount of getblock calls..
04:49 < mn3monic> looks like it's fetching 5blocks\s, this is unhealty for the bitcoind server
04:50 < mn3monic> and afaik it's not trying to sync, since it's requesting 2-3000 blocks behind the lightningd height (which is, actually, 100 blocks behind bitcoind, but this is already told in the #749)
05:19 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
05:24 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 268 seconds]     
05:29 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
05:32 -githubby:#c-lightning- [lightning] cdecker pushed 5 new commits to master: https://git.io/vNM2H
05:32 -githubby:#c-lightning- lightning/master 8c527f3 ZmnSCPxj: common/json: Implement json_add_snum for signed numbers.
05:32 -githubby:#c-lightning- lightning/master b2133e9 ZmnSCPxj: jsonrpc: Trivial compliance with JSON-RPC Error Object.
05:32 -githubby:#c-lightning- lightning/master 551dfed ZmnSCPxj: jsonrpc: Internal: Support changing the error code internally.
05:42 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
06:06 -!- RvMp [~Qint@unaffiliated/qint] has quit [Read error: Connection reset by peer]     
06:06 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
06:15 -!- justus_ [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
06:18 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 240 seconds]     
06:31 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-sdpmqewsbgtqrfcr] has quit [Quit: Connection closed for inactivity]     
06:39 -!- aergerg [d9272dee@gateway/web/freenode/ip.217.39.45.238] has joined #c-lightning     
06:42 < RvMp> could someone explain to me what "{ "command" : "listnodes", "description" : "Show all nodes in our local network view" }, " means. Am I seeing all the nodes known worldwide or is it just based on location? or?
06:46 -!- fizzwont [~irc3@unaffiliated/fizzwont] has joined #c-lightning     
06:54 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
06:56 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
06:59 -!- RvMp [~Qint@unaffiliated/qint] has quit [Client Quit]     
07:00 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
07:05 -!- RvMp [~Qint@unaffiliated/qint] has quit [Client Quit]     
07:10 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
07:11 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds]     
07:12 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
07:14 -!- RvMp [~Qint@unaffiliated/qint] has quit [Client Quit]     
07:17 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
07:22 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
07:26 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning     
07:28 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
07:35 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
07:36 -!- aergerg [d9272dee@gateway/web/freenode/ip.217.39.45.238] has quit [Quit: Page closed]     
07:44 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
07:45 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
07:46 -!- RvMp [~Qint@unaffiliated/qint] has quit [Client Quit]     
07:48 < grubles> so, i paid an invoice from a c-lightning node and it seems to have borked my lnd node
07:48 < grubles> lnd is now outputting tons of "PEER: Peer shutting down, could not enqueue msg." 
07:48 -!- justus_ [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 240 seconds]     
07:49 < grubles> the invoice was for 1 satoshi, so i wonder if that is the cause
07:57 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Remote host closed the connection]     
07:58 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
07:59 -githubby:#c-lightning- [lightning] gdassori opened pull request #805: Update pylightning with current lightningd RPC commands (master...pylightning) https://git.io/vNMPn
08:03 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 260 seconds]     
08:06 -!- Alex_ [~Alex@79.125.251.64] has joined #c-lightning     
08:07 -!- aryseralin [b8428232@gateway/web/freenode/ip.184.66.130.50] has left #c-lightning []     
08:08 -!- alexann [~Alex@77.29.147.121] has quit [Ping timeout: 240 seconds]     
08:23 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
08:26 -!- cubancorona [49ca9483@gateway/web/freenode/ip.73.202.148.131] has quit [Quit: Page closed]     
08:49 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
08:54 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 264 seconds]     
09:05 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
09:08 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
09:13 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
09:14 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
09:15 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
09:19 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 256 seconds]     
09:25 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
09:29 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 265 seconds]     
09:33 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has joined #c-lightning     
09:39 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
09:45 -!- mudley [~mudley@Mail.stienstra.me] has joined #c-lightning     
09:52 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
09:57 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 248 seconds]     
10:06 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
10:13 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 256 seconds]     
10:34 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
10:38 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 256 seconds]     
10:39 -githubby:#c-lightning- [lightning] cdecker opened pull request #813: Return an error if we can't connect and limit the number of retries (master...limit-connect) https://git.io/vNMQI
10:42 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
10:47 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
11:01 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lowmfcybswyklflg] has joined #c-lightning     
11:20 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
11:24 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has joined #c-lightning     
11:26 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Remote host closed the connection]     
11:27 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
11:31 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 240 seconds]     
11:31 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has joined #c-lightning     
12:13 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
12:20 < fizzwont> new channel are stuck in { "state" : "CHANNELD_AWAITING_LOCKIN"  - for hours...any ideas?
12:21 < windsok> grab the funding txid and take a look at it on a block explorer like btc.com
12:21 < fizzwont> thanks
12:21 < windsok> it's probably unconfirmed
12:21 < newbold> mine took a while
12:21 < newbold> because the fee was pretty low
12:22 < fizzwont> shows 6 confirms
12:23 < windsok> is this testnet or mainnet? do cli/lightning-cli getinfo and check what your blockheight is
12:23 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
12:24 < fizzwont> mainnet, shows 506404 height
12:25 < windsok> sounds correct, hmm not sure what else to check
12:26 < newbold> fizzwont: does it show the peer as connected?
12:26 < newbold> "connected: true" or whatever in listpeers
12:27 < fizzwont> yes connected: true on both
12:27 < newbold> you could try restarting c-lightning
12:27 < newbold> (can't hurt)
12:27 < fizzwont> will do thx
12:27 < newbold> actually
12:28 < newbold> you might want to enable the debug log level, and start it such that you're dumping its output to a file
12:28 < newbold> then we can grep that for tx info and see if there's any other errors/details
12:28 < fizzwont> i have log-level=debug and haven't seen anything, but not to a file
12:28 < newbold> yeah, it seems to log to stdout :(
12:29 < newbold> try ./lightningd --network=bitcoin --log-level=debug > clightninglog.txt
12:29 < newbold> or whatever :)
12:29 < fizzwont> cool thanks will try
12:29 < newbold> then you can tail -f clightninglog.txt to keep an eye in real time, or do: less clightninglog.txt | grep <txid>
12:29 < newbold> that second command will show logs related to the funding tx
12:29 < newbold> (I wouldn't try that until after the node is fully up with all blocks added though)
12:30 < fizzwont> thx, my other channels that show "CHANNELD_NORMAL" should be fine, yes?
12:30 < windsok> just beware that debug log can get big :) mine is up to 600MB already
12:35 < newbold> CHANNELD_NORMAL is perfect
12:35 < newbold> windsok: when was the last time you did a build? they updated some code recently to reduce log spam
12:36 < fizzwont> restarted, the one channel still "state" : "CHANNELD_AWAITING_LOCKIN"
12:36 < newbold> might do a git pull, make, and then see if that helps
12:36 < windsok> not for about a day, I should update thanks
12:36 < newbold> fizzwont: ok, try less clightninglog.txt | grep <txid>
12:36 < newbold> or whatever you called the log file
12:37 < newbold> hmm, windsok, you're having the same problem as someone in less clightninglog.txt | grep <txid>
12:37 < newbold> er     
12:37 < newbold> in #lightning-dev-irc
12:38 < newbold> (lol, paste fail)
12:39 < newbold> sorry, #lightining-dev
12:39 < fizzwont> thanks, sorry took me a while to find, made a typo in name
12:39 < fizzwont> lightningd(26144): Owning output 1 297395 (SEGWIT) txid 1009e769bc98857395b388a7cb17ea755fd87486738e4ef4a3cd52d2165b08ca
12:39 < fizzwont> lightningd(26144): peer 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432: Got depth change 0->8 for 1009e769bc98857395b388a7cb17ea755fd87486738e4ef4a3cd52d2165b08ca
12:39 < fizzwont> lightningd(26144): peer 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432: Funding tx 1009e769bc98857395b388a7cb17ea755fd87486738e4ef4a3cd52d2165b08ca depth 8 of 3
12:39 < fizzwont> (sorry for spam)
12:39 < newbold> ok, that's all normal
12:39 < newbold> hmm     
12:40 < windsok> depth change sounds like it's  number of confirms
12:40 < windsok> it has 8 of 3 required
12:41 < fizzwont> ya, shows 8 confirms, channel still waiting lockin
12:41 < newbold> yep     
12:41 < fizzwont> other channel was fine at 3 confirms
12:41 < fizzwont> connected:true - could the node be having other problems?
12:46 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has joined #c-lightning     
12:52 -!- bahadir [b2e905d7@gateway/web/freenode/ip.178.233.5.215] has joined #c-lightning     
12:56 -!- napalm` [~client@185.56.20.132] has joined #c-lightning     
13:01 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has quit [Ping timeout: 260 seconds]     
13:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lowmfcybswyklflg] has quit [Quit: Connection closed for inactivity]     
13:27 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
13:52 -!- djh82uk [51627cc9@gateway/web/freenode/ip.81.98.124.201] has joined #c-lightning     
13:52 < djh82uk> Hey, can anyone advise how I set IP/URI and Alias for broadcast?
13:53 < djh82uk> Just cannot find it documented anywhere, im sure im missing something simple
13:54 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has quit [Ping timeout: 256 seconds]     
13:57 < ebx> djh82uk, `--ipaddr=`, `--uri=`, `--alias=` when launching lightningd
13:58 < djh82uk> perfect, thank you, was obfuscated as im running it via docker
14:06 < djh82uk> ok, got it accepting ipaddr and alias but it says uri is an invalid option
14:09 < djh82uk> ah, no worries, it's showing up with the URI automatically now on the browser
14:12 < ebx> ah yeah sorry -- had a bit of a brainfart there, not sure why I was thinking there was a --uri switch
14:22 -githubby:#c-lightning- [lightning] practicalswift opened pull request #816: Fix typos (master...fix-typos) https://git.io/vNDv2
14:32 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has joined #c-lightning     
14:37 -!- mudley [~mudley@Mail.stienstra.me] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]     
14:41 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #c-lightning     
14:46 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 268 seconds]     
14:48 -!- RvMp [~Qint@unaffiliated/qint] has joined #c-lightning     
14:49 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has quit [Quit: Textual IRC Client: www.textualapp.com]     
14:50 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #c-lightning     
14:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
15:07 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
15:08 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-knonxquuifmwywux] has joined #c-lightning     
15:24 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Quit: Leaving]     
15:55 -!- bryan_w [~is@2600:2108:9:8a90:72a3:5780:f492:1888] has joined #c-lightning     
16:41 -githubby:#c-lightning- [lightning] cdecker closed pull request #792: Explain table vars (master...patch-1) https://git.io/vN1B1
16:53 -!- RvMp [~Qint@unaffiliated/qint] has quit [Quit: Vires in numeris]     
17:00 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has quit [Ping timeout: 256 seconds]     
17:00 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection]     
17:04 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
17:11 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Ping timeout: 252 seconds]     
17:12 < djh82uk> np, thanks for the help
17:17 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
17:18 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-knonxquuifmwywux] has quit [Quit: Connection closed for inactivity]     
17:18 -!- justus [~justus@x4db3e3b7.dyn.telefonica.de] has joined #c-lightning     
17:22 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Quit: Leaving.]     
17:22 -!- justus [~justus@x4db3e3b7.dyn.telefonica.de] has quit [Ping timeout: 256 seconds]     
17:23 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Ping timeout: 246 seconds]     
17:26 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has quit [Quit: Leaving]     
17:29 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
17:29 -githubby:#c-lightning- [lightning] dongcarl opened pull request #819: Submodulize libwally-core for LTO removal. (master...libwally-LTO) https://git.io/vNDqh
17:34 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Ping timeout: 268 seconds]     
17:35 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
17:42 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection]     
17:44 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 256 seconds]     
17:46 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has joined #c-lightning     
17:46 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has quit [Changing host]     
17:46 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning     
17:52 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
17:52 < newbold> anyone mess with invoicing in c-lightning?
17:54 < fizzwont> yes     
17:55 < fizzwont> not very successfully, some fees issues and random bugs
17:55 < grubles> oh what issues were you having?
17:57 < fizzwont> couldn't get paid but we didn't have direct link, didn't have a lot of time to debug
17:57 < grubles> yeah i was having the same issue
17:57 < grubles> { "code" : -1, "message" : "failed: WIRE_FEE_INSUFFICIENT (reply from remote)" }
17:57 < grubles> ^^^ from someone trying to pay an invoice i sent them
17:58 < newbold> hmmm, can c-lightning actually generate a bolt11 invoice? when I mess with the invoice commands, I don't ever get that back in response
17:58 < newbold> only a payment_hash
17:59 < newbold> unless I'm overlooking a command or something
17:59 < newbold> grubles: did you actually generate the invoice in c-lightning?
17:59 < grubles> yes     
17:59 < newbold> tell me your secrets!
18:00 < grubles> lightning-cli invoice
18:00 < grubles> lol     
18:00 < grubles> not sure what you mea
18:00 < grubles> n     
18:00 < newbold> I do that, but I don't get the bolt11 data
18:00 < newbold> oh wait
18:00 < newbold> now I do.
18:00 < newbold> loool
18:00 < newbold> wtf.
18:01 < fizzwont> yep it's there
18:01 < grubles> lol     
18:01 -!- djh82uk [51627cc9@gateway/web/freenode/ip.81.98.124.201] has quit [Ping timeout: 260 seconds]     
18:01 < newbold> but you only get it that one time upon creation, right? listinvoices doesn't seem to show it again
18:02 < grubles> correct. seems like it.
18:03 < litch> If I see a message of: `Owning subdaemon lightning_channeld died`, is that a problem on my end, or their end?  Did they go away?  Or is my system screwy?
18:04 < newbold> litch: oh man, this is my issue
18:04 < newbold> litch: hang on
18:04 < newbold> litch: https://github.com/ElementsProject/lightning/issues/793
18:04 < newbold> wait nevermind
18:05 < newbold> that's not my issue
18:05 < newbold> mine was lightning_onchaind died lol
18:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]     
18:07 < grubles> i'm having an issue with my channel becoming inactive as well
18:07 < grubles> active: false
18:10 < newbold> sweet, I got it working! on-demand invoice creation: https://random.newbold.co/lightning/
18:12 < fizzwont> very nice!
18:14 -!- cubancorona_ [49ca9483@gateway/web/freenode/ip.73.202.148.131] has joined #c-lightning     
18:16 < newbold> I wonder if I can pay myself through my own node
18:17 < newbold> can you open a channel with yourself? :P
18:18 < ebx> I tried making a payment to myself when testing store integration and it didn't work :P
18:18 < ebx> which... I guess makes sense
18:20 < ebx> gives a "could not find route" message if I remember correctly
18:24 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection]     
18:25 < litch> So here's a bit more logs of my problem when I try to start a payment:
18:25 < litch> lightningd(20627): Sending 192143674 over 4 hops to deliver 192138369
18:25 < litch> lightning_channeld(20100): STATUS_FAIL_PEER_IO: peer read failed: Success
18:25 < litch> lightningd(20627): peer 0292ee280619b700bbbdfe4e6e92bdb894f77eb50d91d88c1803338c28df448f9f: Peer transient failure in CHANNELD_NORMAL: Owning subdaemon lightning_channeld died (33792)
18:25 < litch> lightning_channeld(27234): STATUS_FAIL_PEER_IO: bad reestablish msg: WIRE_ERROR 00110000000000000000000000000000000000000000000000000000000000000000000e496e7465726e616c206572726f72
18:26 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
18:27 < litch> that's a great site newbold - thanks 
18:30 < fizzwont> yeah, i've seen the WIRE ERROR before
18:36 < bloxton> Hi all.  I've funded a channel to SLEEPYARK with a value of 300000 sats.  The funding transaction is 8 confirmations deep.  Both bitcoind and lightningd are up-to-date wrt the blockchain.  But the channel is still CHANNELD_AWAITING_LOCKIN?
18:37 < litch> bloxton I haven't been able to get a channel to confirm open to SLEEPYARK either
18:37 < litch> (nor have a bunch of people here)
18:37 < bloxton> Ah.  I see.
18:38 < bloxton> Amongst other values, listpeers shows: "msatoshi_to_us" : 300000000, "msatoshi_total" : 300000000
18:38 < litch> I'm getting that WIRE_ERROR on testnet and mainnet =/ similar repro path.  Connect to peer works fine, opening channel works fine, WIRE_ERROR shows up
18:38 < bloxton> Are these "milli-satoshis"?
18:38 < litch> I'm getting that WIRE_ERROR on testnet and mainnet =/ similar repro path.  Connect to peer works fine, opening channel works fine, then I try to actually send a payment
18:39 < litch> Oops, sorry for that spam - re-acquanting myself with IRC.  And yes, milli-satoshis bloxton
18:39 < bloxton> So 300,000 satoshis becomes 300,000,000 milli-sats?  So, fractions of a satoshi?
18:41 < newbold> yep     
18:41 < newbold> lightning is wild
18:43 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection]     
18:56 -!- cubancorona_ [49ca9483@gateway/web/freenode/ip.73.202.148.131] has quit [Ping timeout: 260 seconds]     
19:19 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
19:19 < windsok> if anyone would like to help test c-lightning on litecoin testnet - https://github.com/ElementsProject/lightning/pull/715#issuecomment-361035002
19:33 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection]     
19:34 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
19:43 -githubby:#c-lightning- [lightning] Sgt-Miller opened pull request #820: Allow pong when in CHANNELD_AWAITING_LOCKIN (master...patch-2) https://git.io/vNDsZ
20:07 -!- alexann [~Alex@79.125.205.109] has joined #c-lightning     
20:10 -!- Alex_ [~Alex@79.125.251.64] has quit [Ping timeout: 260 seconds]     
20:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
20:20 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Quit: Leaving]     
20:20 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection]     
20:21 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #c-lightning     
20:32 < newbold> hmm... can an invoice be reused?
20:33 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qunqmfyikqagahew] has joined #c-lightning     
20:50 -!- jb55 [~jb55@24.87.206.252] has joined #c-lightning     
20:52 < rusty> newbold: no...
20:53 < rusty> newbold: at least, not once it's paid.
20:53 < tweaks> including invoices with "any" amount?
20:54 < tweaks> for donation invoices and the like
20:56 < rusty> tweaks: unfortunately, yes.  Until we start using scriptless scripts, there's no good way to do this.  If you want a receipt (to prove payment) you need a separate invoice.
20:57 < rusty> We could hack up a donation method, (by encrypting the secret itself in the payment onion) but then you lose ability to prove you made the payment.
20:58 < tweaks> ya, makes sense
20:59 < newbold> "payment onion" is such an awesome term
21:00 < newbold> rusty: look what I stuck on top of c-lightning! :D https://random.newbold.co/lightning/
21:00 < newbold> it's crappy php but I'm having a blast
21:00 < rusty> newbold: nice!!
21:05 < cryptapus> is there a good document on descriptions of the channel states?
21:06 < windsok> There is a little bit of info in this PR. BOLT's also have some info https://github.com/lightningnetwork/lightning-rfc/blob/master/05-onchain.md#mutual-close-handling
21:06 < windsok> pr: https://github.com/ElementsProject/lightning/pull/799
21:06 < newbold> bolt2 specifically, I think https://github.com/lightningnetwork/lightning-rfc/blob/master/02-peer-protocol.md
21:07 < cryptapus> wonderful, thanks!
21:09 < newbold> cryptapus: I don't think you'll find c-lightning channel states in the bolt doc though
21:09 < newbold> pretty sure c-lightning states are unique to c-lightning
21:09 < cryptapus> that's fine, hopefully I can make out what they mean
21:10 < windsok> at least the MUTUAL_CLOSE, OUR_UNILATERAL and THEIR_UNILATERAL map directly to the closing handling in BOLT5
21:13 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection]     
21:41 -!- jb55 [~jb55@24.87.206.252] has quit [Ping timeout: 268 seconds]     
21:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds]     
22:57 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds]     
22:59 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
23:01 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #822: peer_control: Correct roundoff of remote-side msatoshi. (master...correct-rounding) https://git.io/vNDCk
23:08 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection]     
23:08 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
23:13 < bloxton> Does it matter how the funding transaction is created?  Does it need to be a manual 'raw' transaction, or could I use Jaxx?  Just wondering if multiple outputs (1. funding amount and 2. change) are why the channel stays in CHANNELD_AWAITING_LOCKIN?
23:19 < bloxton> Scratch that.  Can see from my logs that lightningd saw the block that the funding tx was in, and updated depth change from 0 -> 1.  Still trying to determine what happened (or didn't) next.
23:40 < windsok> bloxton: there is some talk about funding transactions from external wallets in this issue https://github.com/ElementsProject/lightning/issues/644