--- Day changed Tue Feb 20 2018 00:03 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 00:29 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 00:29 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 00:41 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 00:53 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has joined #c-lightning 01:07 -!- bitonic-cjp [~bitonic-c@92.111.70.106] has joined #c-lightning 01:14 -!- jojeyh [~delphi@2602:306:b8b6:b970:f504:8f4:31bf:2836] has quit [Ping timeout: 276 seconds] 01:20 -!- jojeyh [~delphi@2602:306:b8b6:b970:f504:8f4:31bf:2836] has joined #c-lightning 01:21 -!- jojeyh [~delphi@2602:306:b8b6:b970:f504:8f4:31bf:2836] has quit [Remote host closed the connection] 01:54 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1048: lightningd: expose internal error information. (master...expose-internal-error) https://git.io/vABhr 01:54 -!- FORATEMER-node [b253a4da@gateway/web/freenode/ip.178.83.164.218] has joined #c-lightning 01:55 -!- straumat [5d5f3c17@gateway/web/freenode/ip.93.95.60.23] has joined #c-lightning 01:58 < straumat> Hi. I'm a Java developer and I wrote applications like https://github.com/straumat/blockchain2graph and I also own a company named Scub with 45 Java developers. I would like to know if you have an idea of a project (open source) I could create to help your project and ln ? A java API ? A telegram Bot ? A independant neo4J database of ln nodes/channels ? Any idea or feature you would like ? 02:00 < bitonic-cjp> Java? Can you make things for Android? 02:00 < straumat> Nope ... i'm more backend sorry :( 02:08 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1050: log: fix ltmp crash. (master...pr-943) https://git.io/vABjd 02:17 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has quit [Ping timeout: 260 seconds] 02:27 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1051: lightningd: fix crash when htlc failed and source is onchain. (master...pr-821) https://git.io/vARfA 03:04 < p3tr> it seems to me that unilateral channel close has some problems - this is the third time i had to manually do dev-sign-last-tx to finally be able to close a channel that was in state CHANNELD_SHUTTING_DOWN for several days 03:04 < p3tr> is this a known issue? 03:06 < p3tr> it seems that the closing tx simply never hits the blockchain unless i do it manually (sendrawtransaction with the tx i get from c-lightning dev-sign-last-tx) 03:06 -!- FORATEMER-node [b253a4da@gateway/web/freenode/ip.178.83.164.218] has quit [Ping timeout: 260 seconds] 03:51 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1053: Make sure msatoshi and sender are not uninitialized when calling channel_add_htlc(...) (master...msatoshi) https://git.io/vAROm 03:56 <@cdecker> p3tr, what version are you running? We had a bug a few weeks ago that was blocking our bitcoind calls, which is also used to send TXs to the blockchain 03:57 <@cdecker> It has since been fixed 03:58 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vAROj 03:58 -githubby:#c-lightning- lightning/master 4aeebe8 Rusty Russell: log: fix ltmp crash.... 04:06 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vARsI 04:06 -githubby:#c-lightning- lightning/master 6bacab5 practicalswift: Fix typos 04:15 < p3tr> cdecker: um, not sure exactly i think the last update i did was about a week ago 04:15 < p3tr> ok i just updated to latest rev, will check whether the issue still exists once i get to it in the evening 04:50 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:38 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-mizqdwmwjvhcpahc] has quit [Quit: Connection closed for inactivity] 05:48 -!- dougsland [douglas@nat/redhat/x-gsqyrkmawcleqizp] has joined #c-lightning 05:57 -!- dougsland [douglas@nat/redhat/x-gsqyrkmawcleqizp] has quit [Changing host] 05:57 -!- dougsland [douglas@tchelinux/moderator/dougsland] has joined #c-lightning 06:12 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 06:36 -!- shesek [~shesek@bzq-84-110-53-17.red.bezeqint.net] has joined #c-lightning 06:36 -!- shesek [~shesek@bzq-84-110-53-17.red.bezeqint.net] has quit [Changing host] 06:36 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 06:44 -!- alanc44 [uid281453@gateway/web/irccloud.com/x-oalwilwrjqqaljav] has quit [Quit: Connection closed for inactivity] 06:46 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 06:49 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 07:23 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning 07:25 -!- straumat [5d5f3c17@gateway/web/freenode/ip.93.95.60.23] has quit [Quit: Page closed] 07:32 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 07:37 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 256 seconds] 07:40 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Quit: Leaving.] 07:41 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning 07:42 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 07:44 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 265 seconds] 07:44 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 08:11 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 08:28 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 08:32 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Quit: Leaving.] 08:32 -!- jb554 [~jb55@216-71-192-56.dyn.novuscom.net] has joined #c-lightning 08:35 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 08:35 -!- vogelito [~Adium@187.162.108.173] has joined #c-lightning 08:45 -!- vogelito [~Adium@187.162.108.173] has quit [Quit: Leaving.] 09:00 -!- vogelito [~Adium@187.162.108.173] has joined #c-lightning 09:06 < mlz> how can we close channels that keep having "state" : "CHANNELD_AWAITING_LOCKIN", ? 09:10 -!- bitonic-cjp [~bitonic-c@92.111.70.106] has quit [Quit: Leaving] 09:10 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 09:14 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 276 seconds] 09:25 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds] 09:37 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 09:37 < provoostenator> mlz any luck with dev-fail? 09:37 < mlz> provoostenator, i'm reading up on github issues ... but how do you use dev-fail? 09:38 < provoostenator> lightning-cli dev-fail [node_id] 09:38 < provoostenator> You may or may not lose your money. 09:44 < grubles> maybe dev-rescan-outputs 09:44 < grubles> your c-lightning might be behind bitcoind 09:44 < grubles> so maybe shut down then restart 09:46 < mlz> provoostenator, it seems working.. but weird that i did it on the receiving node (the node that had channels opened to by other nodes) and now it still says "state" : "CHANNELD_AWAITING_LOCKIN" but the other nodes say "state" : "ONCHAIND_OUR_UNILATERAL", 09:46 < mlz> provoostenator, thank you :) 09:47 < mlz> i also restarted that node, now restarting again 09:49 < mlz> still saying "state" : "ONCHAIND_OUR_UNILATERAL", 09:49 < mlz> i'm wondering if it's because this is on WSL Ubuntu and the port isn't opened? 09:49 < mlz> my other two nodes are on VPS servers and don't have this problem 09:50 < grubles> how do you network your lightning instances on your VPS 09:50 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 265 seconds] 09:50 < grubles> specifically, do you run bitcoind on them? 09:56 < mlz> yup 09:56 < mlz> for both c-lightning and lnd on testnet 09:56 < mlz> i guess i can do the same for mainnet but i'm not sure about c-lightning yet 09:57 < mlz> i have to change the port because they all use port 9735 09:57 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 10:00 < grubles> ah ok so storage isn't that expensive then 10:00 < grubles> since testnet is much smaller 10:03 < provoostenator> mlz: ONCHAIND_OUR_UNILATERAL takes 144 blocks to complete; your node broadcast that transaction and then the other node has 144 blocks to claim all the funds if you cheated. Only then does your node sweep its funds. 10:04 < provoostenator> Although even in that case I've seen ONCHAIND_OUR_UNILATERAL stick around longer, but at least you shoudl be able to open a new channel. 10:13 < mlz> oh.. i see 10:20 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 256 seconds] 10:29 -!- vogelito [~Adium@187.162.108.173] has quit [Quit: Leaving.] 10:35 -!- vogelito [~Adium@187.162.108.173] has joined #c-lightning 10:52 < cluelessperson> so in clightning 10:52 < cluelessperson> --bitcoin-datadir -datadir arg for bitcoin-cli 10:52 < cluelessperson> what does this mean? 10:52 < cluelessperson> datadir for bitcoin-cli ? 10:52 < cluelessperson> bitcoind's datadir is where blocks are stored. 10:53 < cluelessperson> bitcoin-cli is a binary 10:53 < cluelessperson> that's nonsensical terminology 10:54 < cluelessperson> --- 10:54 < cluelessperson> Also, does lightningd need a different datadirecotry for mainnet versus testnet? 10:54 < cluelessperson> or does it place a new testnet datadir inside the mainnet datadir, like bitcoind? 10:55 -!- fafaynk [556487f0@gateway/web/freenode/ip.85.100.135.240] has joined #c-lightning 10:56 < vogelito> how long does it take for lightningd to see the funding transaction? 10:56 < grubles> lightningd needs bitcoin-cli to communicate with bitcoind 10:57 < cluelessperson> grubles: so, what does bitcoin-datadir mean? 10:57 < cluelessperson> why not just ask for "bitcoin-cli-binary" path 10:57 < grubles> yeah i suppose it could be worded more clearly 10:58 < cluelessperson> --rpc-file Set JSON-RPC socket (or /dev/tty) (default: "lightning-rpc") 10:58 < cluelessperson> ??? 10:58 < cluelessperson> grubles: I don't mean to be a dick. I'm just very upfront and I like things clear :P 10:58 < cluelessperson> I'm good at knowing what users need to see 10:58 < cluelessperson> (usually) 10:58 < vogelito> root@c-lightning:/home/ubuntu# runuser -l bitcoin -c '/home/ubuntu/builds/lightning/cli/lightning-cli newaddr' 10:58 < vogelito> { "address" : "37dAhm4cizrtKRChg5GbtRvRsGYFsZ1vha" } 10:58 < vogelito> https://blockchain.info/address/37dAhm4cizrtKRChg5GbtRvRsGYFsZ1vha 10:59 < vogelito> root@c-lightning:/home/ubuntu# runuser -l bitcoin -c '/home/ubuntu/builds/lightning/cli/lightning-cli listfunds' 10:59 < vogelito> { "outputs" : 10:59 < vogelito> [ ], "channels" : 10:59 < vogelito> [ ] } 10:59 < cluelessperson> vogelito: Use a pastebin 10:59 < grubles> cluelessperson, haha no i don't think you're being a dick 10:59 < vogelito> will do @cluelessperson 11:00 < fafaynk> hi all, i have a problem with my lightningd, log is here http://pasted.co/e6cfdd6e 11:00 < fafaynk> please help 11:01 < cluelessperson> fafaynk: what problem 11:01 < fafaynk> process kills itself 11:01 < fafaynk> last log message is lightningd: lightning_gossipd failed (signal 14), exiting. 11:04 < fafaynk> anybody can help? 11:04 < fafaynk> lightning_channeld(30): STATUS_FAIL_GOSSIP_IO: Can't read command: Success lightningd(1): peer 03dbd26bedb44490bfbf19c876f41c4561e3c650517a6c6ba77cb5e581b0b886b8: Peer transient failure in CHANNELD_NORMAL: Owning subdaemon lightning_channeld died (33280) 11:13 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 11:14 < cluelessperson> --bitcoin-datadir -datadir arg for bitcoin-cli 11:14 < cluelessperson> --rpc-file Set JSON-RPC socket (or /dev/tty) (default: "lightning-rpc") 11:14 < cluelessperson> can anyone tell me what these are? 11:25 -!- vogelito [~Adium@187.162.108.173] has quit [Quit: Leaving.] 11:28 < cluelessperson> ... 11:28 < cluelessperson> Why is clightning communicating with bitcoind using bitcoin-cli and NOT through the RPC interface? 11:40 < cluelessperson> lightningd(1805): bitcoin-cli exec failed: No such file or directory 11:49 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning 11:50 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Client Quit] 11:59 < mlz> cluelessperson, what are you trying to do? 12:00 -!- fafaynk [556487f0@gateway/web/freenode/ip.85.100.135.240] has quit [Ping timeout: 260 seconds] 12:03 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning 12:05 < cluelessperson> mlz: setup clightning on mainnet with bitcoind 12:06 < cluelessperson> mlz: but, I *properly* setup bitcoind to use a conf from /etc/bitcoin/bitcoin-mainnet.conf, datadir /var/bitcoin/bitcoind/data/ 12:06 < cluelessperson> mlz: and bitcoin-cli is located at. /var/bitcoin/bitcoind/source/bitcoin/src/bitcoin-cli 12:06 < cluelessperson> clightning can't seem to find the bitcoin-cli exe 12:06 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Client Quit] 12:07 < cluelessperson> which, is confusing, because bitcoind uses a RPC interface to communicate 12:07 < mlz> why would c-lighting have to find bitcoin-cli? 12:07 < mlz> you have bitcoin fullnode to run, and then you set up lightningd to run 12:08 < cluelessperson> from clightning's logs 12:08 < cluelessperson> bitcoin-cli exec failed: No such file or directory 12:08 < mlz> and you use c-lightning rpc calls to create channels 12:08 < cluelessperson> /var/bitcoin/lightningd/source/daemon# ./lightningd --lightning-dir /var/bitcoin/lightningd/mainnet_datadir/ 12:08 < cluelessperson> --bitcoin-datadir -datadir arg for bitcoin-cli 12:08 < cluelessperson> --rpc-file Set JSON-RPC socket (or /dev/tty) (default: "lightning-rpc") 12:08 < cluelessperson> from the help. :/ 12:09 < mlz> i put my .bitcoin in /home/mlz/.bitcoin 12:09 < mlz> try that 12:09 < mlz> and i put my .lightning in /home/mlz/.lightning 12:09 < mlz> try that 12:09 < mlz> make your life simple and stop throwing your temper around here 12:10 < cluelessperson> mlz: I'm not reconfiguring my server incorrectly 12:11 < cluelessperson> I adhere to conventions to keep my configurations organized and reliable. 12:12 < mlz> well you're such a geek, figure it out then 12:25 < cluelessperson> mlz: if it's not designed to use proper conventions, I may not be able to 12:28 < mlz> cluelessperson, it's fine, maybe LN isn't for you 12:28 < cluelessperson> mlz: no, it's not fine. Conventions exist for a reason. 12:29 < mlz> no clue, and i don't care 12:29 < cluelessperson> mlz: My server has multiple drives used for storage. Storage is a finite resource, and so must be managed. Certain directories are used for storing data, others are used for configuration. 12:30 < cluelessperson> Some random program deciding to store its stuff in a random place is frustrating 12:31 < cluelessperson> mlz: I also run 3 or more instances of bitcoind. mainnet on an NVME for fast disk IO, mainnet on SSD for general use, testnet, electrumxmainnet, electrumx on testnet 12:31 < cluelessperson> which one will lightningd connect to? 12:33 < cluelessperson> --- 12:33 < cluelessperson> mlz: and believe me, I want to help, I'm just not ina position where I can 12:34 < mlz> nobody is asking you to help with anger 12:34 < cluelessperson> mlz: I'm not angry at you 12:34 < mlz> i put both bitcoind and lightind in home and they talk to each other 12:34 < mlz> so if you have some personal setup, you should know how to get them to talk to each other, how am i supposed to know? 12:35 < mlz> i'm not a linux user, and i can get the nodes run on linux, you should be better than me 12:35 < cluelessperson> mlz: I don't have some personal setup. Bitcoind has an RPC, the convention is username:password:IP:port 12:36 < cluelessperson> this is how pretty much everything works 12:40 < mlz> never heard of that "convention for bitcoind" 12:40 < mlz> you created it? 12:41 < cluelessperson> mlz: so databases and various services depending on each other has existed for a long time. In databasing you typically create a database, a user/password, and configure the permissions to that database that user has. 12:41 < cluelessperson> mlz: Then, for like a website, like wordpress, you'd configure it to connect to the database at ip:port and use the username:password 12:42 < mlz> well do you know you don't need a user and pw you still can do rpc call for bitcoin 12:42 < mlz> calls* 12:42 < cluelessperson> mlz: https://en.bitcoin.it/wiki/API_reference_(JSON-RPC) 12:42 < mlz> but this is offtopic for this channel 12:43 < cluelessperson> mlz: Ah, so then it'd probably be best to interface directly with bitcoin peers, and allow you to define which peers to connect to 12:43 -17WAAR9DF:#c-lightning- [lightning] cdecker closed pull request #1046: subd: handle stdin being closed (eg. --daemon). (master...pr-1016) https://git.io/vABMX 12:43 -7GHAB5LAD:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vA0lz 12:43 -7GHAB5LAD:#c-lightning- lightning/master eca55ce Rusty Russell: subd: handle stdin being closed (eg. --daemon).... 12:45 < cluelessperson> mlz: here's code I made in python to connect to electrumx and bitcoin nodes: https://hastebin.com/raw/amaquguraf 12:46 < mlz> cluelessperson, we're going offtopic, i'm not going to discuss this here 12:50 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 12:50 < rotarydialer> Where can I find more info on a payment that I sent, that now is stated as 'pending' when I do > lightning-cli listpayments ? 12:51 < rotarydialer> also, when I try and do getroute I get: { "code" : -1, "message" : "Could not find a route" } 12:54 -!- jb554 [~jb55@216-71-192-56.dyn.novuscom.net] has quit [Ping timeout: 240 seconds] 13:14 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vA0Bh 13:14 -githubby:#c-lightning- lightning/master d2265cd practicalswift: Make sure msatoshi and sender are not uninitialized when calling channel_add_htlc(...) 13:28 -!- jb554 [~jb55@S010618b16923ebb1.vc.shawcable.net] has joined #c-lightning 13:35 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 13:35 -!- dougsland [douglas@tchelinux/moderator/dougsland] has quit [Ping timeout: 248 seconds] 13:36 -githubby:#c-lightning- [lightning] cdecker pushed 8 new commits to master: https://git.io/vA0EX 13:36 -githubby:#c-lightning- lightning/master 4cf274b Rusty Russell: lightningd/opening_control: routines to control openingd (move from peer_control.c)... 13:36 -githubby:#c-lightning- lightning/master a83ff83 Rusty Russell: lightningd/connect_control: routines to control connecting (move from peer_control.c)... 13:36 -githubby:#c-lightning- lightning/master 9176ee6 Rusty Russell: lightningd/closing_control: routines to control closingd (move from peer_control.c)... 13:38 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 13:42 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 256 seconds] 13:57 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning 13:59 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vA0gW 13:59 -githubby:#c-lightning- lightning/master 1192f16 Rusty Russell: lightningd: fix crash when htlc failed and source is onchain.... 13:59 -githubby:#c-lightning- [lightning] cdecker opened pull request #1055: Add --no-listen option to disable listening for incoming connections (master...issue-1025) https://git.io/vA0g0 14:00 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Client Quit] 14:11 -!- cryptapus_ is now known as cryptapus 14:12 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Quit: conversation terminated!] 14:14 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #c-lightning 14:19 -!- vogelito [~Adium@187.162.108.173] has joined #c-lightning 14:23 < vogelito> what happens if I already have a channel open but I change my config file to rename my node, change my color, and restart lightningd? 14:28 < mlz> your channel will still be there 14:29 < vogelito> thanks @mlz - with the new name? 14:34 < grubles> can domains be specified instead of IP addresses 14:34 < grubles> in a URI 14:40 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 14:48 -!- jb554 [~jb55@S010618b16923ebb1.vc.shawcable.net] has quit [Ping timeout: 260 seconds] 15:16 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 248 seconds] 15:25 -!- booyah is now known as b00yah 15:25 -!- b00yah is now known as xb00744 15:26 -!- xb00744 is now known as x800744725 15:28 -!- x800744725 is now known as booyah 15:42 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 15:59 -!- vogelito [~Adium@187.162.108.173] has quit [Quit: Leaving.] 16:11 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 16:18 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 256 seconds] 16:25 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 16:29 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 16:31 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ptkymzprmpoctyba] has joined #c-lightning 16:34 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 256 seconds] 16:38 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 16:43 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 256 seconds] 16:47 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 16:52 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 256 seconds] 16:53 -!- jb554 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning 16:57 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 16:58 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning 17:01 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 256 seconds] 17:05 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 17:10 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 240 seconds] 17:14 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 17:19 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 248 seconds] 17:24 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 17:28 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 248 seconds] 17:40 -!- farmerwampum [~farmerwam@209.95.51.102] has quit [Read error: Connection reset by peer] 17:49 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 17:54 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 268 seconds] 17:58 -!- grafcaps [~haroldbr@38.109.179.34] has joined #c-lightning 17:59 -!- lightninmax [495ad11f@gateway/web/freenode/ip.73.90.209.31] has joined #c-lightning 17:59 < lightninmax> heyoooo 18:01 < lightninmax> got a node running. having a problem. have made a bunch of payments now it doesnt work and i got this: { "code" : -1, "message" : "failed: INVALID 0 (WIRE_TEMPORARY_CHANNEL_FAILURE: Capacity exceeded)" } 18:01 < lightninmax> any ideas how to approach this problem? 18:02 -!- grafcaps [~haroldbr@38.109.179.34] has quit [Ping timeout: 248 seconds] 18:24 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 18:28 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 18:40 < dougsland> lightninmax, looks like: https://www.trendsmap.com/twitter/tweet/956136818352648192 18:54 -!- CubicEarths [~cubiceart@73.93.141.14] has joined #c-lightning 20:01 -!- jb554 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 256 seconds] 20:29 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has quit [Read error: Connection reset by peer] 20:54 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 265 seconds] 20:58 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:59 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Quit: Leaving.] 21:06 -!- bryan_w [~is@2600:2108:9:8a90:f3b8:cb41:7595:463f] has joined #c-lightning 21:27 -!- vogelito [~Adium@187.151.195.87] has joined #c-lightning 22:12 -!- aj [aj@cerulean.erisian.com.au] has joined #c-lightning 22:12 -!- CubicEarths [~cubiceart@73.93.141.14] has quit [Remote host closed the connection] 22:13 -!- CubicEarths [~cubiceart@73.93.141.14] has joined #c-lightning 22:16 < aj> test/test_state_coverage.c and hence "make protocol-diagrams" seems to be broken? 22:18 -!- CubicEarths [~cubiceart@73.93.141.14] has quit [Ping timeout: 260 seconds] 22:52 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 276 seconds] 23:01 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 23:26 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 23:27 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 23:31 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 240 seconds] 23:44 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 23:57 -!- renlord [~ry@unaffiliated/renlord] has quit [Ping timeout: 374 seconds] 23:57 -!- windsok [~windsok@unaffiliated/windsok] has quit [Remote host closed the connection] 23:58 -!- renlord [~ry@unaffiliated/renlord] has joined #c-lightning 23:59 -!- windsok [~windsok@rarepepe.cash] has joined #c-lightning 23:59 -!- windsok [~windsok@rarepepe.cash] has quit [Changing host] 23:59 -!- windsok [~windsok@unaffiliated/windsok] has joined #c-lightning