--- Day changed Wed Feb 14 2018 00:19 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 00:19 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 00:41 -!- graphite [~androirc@84-75-249-170.dclient.hispeed.ch] has joined #c-lightning 01:12 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning 01:29 -!- graphite [~androirc@84-75-249-170.dclient.hispeed.ch] has quit [Remote host closed the connection] 01:38 -!- graphite [~androirc@178.197.226.39] has joined #c-lightning 01:38 -!- graphite [~androirc@178.197.226.39] has quit [Read error: Connection reset by peer] 01:39 -!- graphite [~androirc@84-75-249-170.dclient.hispeed.ch] has joined #c-lightning 01:41 -!- vicenteH [~user@195.235.96.150] has joined #c-lightning 01:47 -!- nithalak [~androirc@178.197.226.39] has joined #c-lightning 01:48 -!- nithalak [~androirc@178.197.226.39] has quit [Remote host closed the connection] 01:48 -!- nithalak [~androirc@178.197.226.39] has joined #c-lightning 01:51 -!- graphite [~androirc@84-75-249-170.dclient.hispeed.ch] has quit [Ping timeout: 248 seconds] 02:10 -!- nithalak [~androirc@178.197.226.39] has quit [Read error: Connection reset by peer] 02:10 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #996: Opening cleanups (master...opening-cleanups) https://git.io/vAsiJ 02:11 -!- nithalak [androirc@nat/google/x-oflmmkgvocihqxza] has joined #c-lightning 02:32 -7IZAACM8T:#c-lightning- [lightning] cdecker pushed 21 new commits to master: https://git.io/vAs14 02:32 -7IZAACM8T:#c-lightning- lightning/master 26617d1 Rusty Russell: gossipd/test: update mocks.... 02:32 -7IZAACM8T:#c-lightning- lightning/master 7eea02e Rusty Russell: db: don't allow newer db versions.... 02:32 -7IZAACM8T:#c-lightning- lightning/master fcffbd0 Rusty Russell: channeld: rename new_channel to new_full_channel.... 02:32 -3NAAAEU17:#c-lightning- [lightning] cdecker closed pull request #975: Peer channel split, so we can sanely allow a peer to reopen a channel while others are closed (master...peer-channel-split) https://git.io/vAtHs 02:55 -!- jochemin [~jochemin3@213.99.53.154] has joined #c-lightning 02:57 -githubby:#c-lightning- [lightning] cdecker closed pull request #995: onchain: handle case where multiple HTLCs exist for same payment_hash. (master...fix-394) https://git.io/vAsW0 03:00 -!- nithalak [androirc@nat/google/x-oflmmkgvocihqxza] has quit [Read error: Connection reset by peer] 03:00 -!- nithalak [androirc@nat/google/x-ajyzkfrdojoedqnr] has joined #c-lightning 03:01 -githubby:#c-lightning- [lightning] lvaccaro opened pull request #998: Fix on litecoin mainnet & testnet chainparams (master...litecoin-fix) https://git.io/vAsSC 03:15 < bitonic-cjp> Is there a way for RPC applications to be notified of changes, or do they need to poll? 03:31 -!- llou [~textual@cm-83-97-182-195.telecable.es] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:08 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:08 -!- nithalak [androirc@nat/google/x-ajyzkfrdojoedqnr] has quit [Read error: Connection reset by peer] 04:08 -!- nithalak [androirc@nat/google/x-stwimegluhazjxts] has joined #c-lightning 04:18 -!- llou [~textual@149.12.223.173] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:19 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:23 -!- llou [~textual@149.12.223.173] has quit [Client Quit] 04:23 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:24 -!- llou [~textual@149.12.223.173] has quit [Client Quit] 04:25 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:27 -!- llou [~textual@149.12.223.173] has quit [Client Quit] 04:29 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:36 -!- llou [~textual@149.12.223.173] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:39 -!- nithalak [androirc@nat/google/x-stwimegluhazjxts] has quit [Read error: Connection reset by peer] 04:40 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:41 < provoostenator> ZMQ might be useful 04:42 < provoostenator> bitonic-cjp: https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md 04:42 < provoostenator> Or do you mean notifications by the c-lightning app? 04:42 -!- llou [~textual@149.12.223.173] has quit [Client Quit] 04:44 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 04:49 -!- llou [~textual@149.12.223.173] has joined #c-lightning 04:54 < bitonic-cjp> I mean notifications by c-lightning to an app that uses c-lightning. 04:55 -!- llou [~textual@149.12.223.173] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:57 < lxer> agree. but reading the logfile also works (somewhat) 05:00 < bitonic-cjp> LOL, reading the log file; nice approach. "Hey, something has been written at in ; let's poll the status again!". 05:01 < lxer> no, I use it only for detecting a succesful payment 05:03 < bitonic-cjp> I'm writing a GUI; I also want to know when other peoples' txes are being routed through my node (that changes channel balances). 05:06 < provoostenator> Maybe add ZMQ or something similar to c-lightning? 05:07 < bitonic-cjp> Potential issue: whenever I perform RPC commands, the log gets updated too, which could lead to an infinite loop. I definitely need to filter those log changes out. 05:08 < bitonic-cjp> Yes, adding ZMQ or similar to C-Lightning sounds nice. If other people aren't doing it, I might as well do it myself. 05:10 < lxer> I think getting the routing and payment to work is first prio. 05:11 < bitonic-cjp> I'm first going to develop my GUI a bit further to find out what I need in terms of notifications. For now, I'll just use periodic polling. 05:36 -!- nithalak [androirc@nat/google/x-afmzwmchphwuirbo] has joined #c-lightning 06:12 -!- bryan_w [~is@2600:2108:9:8a90:72a3:5780:f492:1888] has joined #c-lightning 06:26 -githubby:#c-lightning- [lightning] cdecker closed pull request #998: Fix on litecoin mainnet & testnet chainparams (master...litecoin-fix) https://git.io/vAsSC 06:41 -!- llou [~textual@cm-83-97-182-195.telecable.es] has joined #c-lightning 06:41 -!- nithalak [androirc@nat/google/x-afmzwmchphwuirbo] has quit [Ping timeout: 265 seconds] 06:45 -!- dougsland [douglas@nat/redhat/x-gjxjwsnziwgrgqbw] has joined #c-lightning 06:50 -!- Poodle [d48bcf55@gateway/web/freenode/ip.212.139.207.85] has joined #c-lightning 06:51 < Poodle> just curious what was main reason for c-lightning ? not fans of golang ? 06:52 < mlz> lol 06:53 < mlz> it's really easy to compile c-lightning and run it but then it just has other problems that im not fond of 06:53 < mlz> but hopefully the devs are sorting them out 06:56 -!- graphite [~androirc@178.197.226.39] has joined #c-lightning 06:57 -!- graphite [~androirc@178.197.226.39] has quit [Quit: Out] 06:58 -!- graphite [~androirc@178.197.226.39] has joined #c-lightning 06:58 < Poodle> i've just recently (few days) tried the golang lightning and zap and lightning-app. 07:00 < mlz> i'm reinstalling c-lightning on WSL Ubuntu the 3rd time :D 07:00 < Poodle> which ones' easier to debug c or the golang :) 07:01 < mlz> c-lightning has an easier entry but after that you're in some complicated issues, lnd has a harder entry but after that it's faily easy to know what's going on 07:01 < mlz> fairly* 07:02 < mlz> so i learned lnd first the hard way, now i'm trying to understand c-lightning 07:03 < Poodle> usually when i learn new code base i look for lots of printf sprinkled throughout the code, then have fancy trace logs to see the flow. might have to manually add some :( 07:05 -!- graphite [~androirc@178.197.226.39] has quit [Remote host closed the connection] 07:11 < bitonic-cjp> Why isn't every channel-related amount in the RPC listed in milliSatoshi? 07:12 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-odcczcjvsbaxzrkx] has quit [Quit: Connection closed for inactivity] 07:13 < mlz> afaik, msat is only used for fees 07:15 < bitonic-cjp> Fees end up in channel balances, don't they? So shouldn't every part of the channel balance be expressed in msat? 07:17 < bitonic-cjp> Example of where else msat is used: in the invoice rpc command. 07:18 < bitonic-cjp> Only for on-chain amounts (channel funding, setting on-chain fees, listing non-channel funds) I'd expect amounts to be rounded to satoshi. Even then, it might be clean to use msat as unit in the RPC. 07:19 < mlz> ah c-lightning uses msat in balances.. 07:19 < mlz> i wish that would be changed 07:20 < bitonic-cjp> No, I'd like to have everything changed to msat; right now it's inconsistent. 07:21 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 276 seconds] 07:21 < mlz> no i'd rather get rid of msat altogether but if the devs want to use it, only use it for fees 07:22 -githubby:#c-lightning- [lightning] cdecker opened pull request #999: pylightning: Implement dict based API client (update from #884) (master...json-dict) https://git.io/vAGGi 07:22 < bitonic-cjp> If you express everything in Satoshi, you lose resolution. On a user interface that might be acceptable, but on the RPC level, the full resolution should always be made available. 07:23 < provoostenator> What does this mean? "Unacceptable channel constraints: minimum HTLC value is too large: 0" (when opening a channel to mainnet Yalls) 07:23 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 07:23 < mlz> maybe in 10 yrs if 1BTC == 1mil USD then i would say use msat but for now, i think it's too extreme 07:24 < bitonic-cjp> That is thinking from the POV of the end user. Think instead from the POV of a programmer. The RPC is not primarily an end user interface. 07:26 < bitonic-cjp> The RPC is the only official point of entry for monitoring / controlling c-lightning. If the RPC doesn't allow you to see sub-Satoshi amounts, nothing will. 07:26 < mlz> bitonic-cjp, sure, from the POV of programmer you might be right but make it not too complicated for the average joes 07:27 < bitonic-cjp> Whoever is manually hacking with the RPC isn't an average joe. 07:28 < bitonic-cjp> BTW I am really interested in making Lightning available to the average joe. I'm actually making a GUI right now. 07:29 < provoostenator> Also, I think I made it crash by connecting to a peer that I may have had a channel with in the past: wallet_channel_save: UNIQUE constraint failed: peers.node_id 07:29 < bitonic-cjp> In the GUI, the impact of sub-Satoshi amounts is just that a number of extra decimals is added. 07:29 < provoostenator> Happens when trying to fund a channel. 07:31 < bitonic-cjp> When closing a channel, the GUI may need to explain to the average joe that amounts will be rounded. However, that rounding is probably negligible to the on-chain fee anyway. 07:33 -githubby:#c-lightning- [lightning] lvaccaro closed pull request #940: Add dev-listaddrs command (master...listaddr) https://git.io/vAfVP 07:52 -!- jochemin [~jochemin3@213.99.53.154] has quit [Remote host closed the connection] 07:52 -!- jochemin [~jochemin3@213.99.53.154] has joined #c-lightning 07:58 -!- JSorel [~JSorel@modemcable086.144-178-173.mc.videotron.ca] has joined #c-lightning 08:01 -githubby:#c-lightning- [lightning] lvaccaro opened pull request #1001: Add dev-listaddrs option (master...dev-listaddrs) https://git.io/vAG83 08:11 -!- ougha [~quassel@b2b-130-180-107-194.unitymedia.biz] has joined #c-lightning 08:11 -!- ougha [~quassel@b2b-130-180-107-194.unitymedia.biz] has quit [Changing host] 08:11 -!- ougha [~quassel@unaffiliated/ougha] has joined #c-lightning 08:21 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 08:28 -!- bryan_w [~is@2600:2108:9:8a90:72a3:5780:f492:1888] has quit [Ping timeout: 255 seconds] 08:44 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 09:06 -!- tmus [~tmus@194.177.231.78] has joined #c-lightning 09:07 < tmus> Is there a good way to perform a backup of c-lightning state/data while it's running? Or is the only good way to stop the daemon first, do the backup and then restart? 09:13 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving] 09:19 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 255 seconds] 09:23 -!- graphite [~androirc@84-75-249-170.dclient.hispeed.ch] has joined #c-lightning 09:27 -!- graphite [~androirc@84-75-249-170.dclient.hispeed.ch] has quit [Client Quit] 09:29 -!- graphite [~graphite@37.139.21.22] has joined #c-lightning 10:14 -!- llou [~textual@cm-83-97-182-195.telecable.es] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 10:29 -!- JSorel [~JSorel@modemcable086.144-178-173.mc.videotron.ca] has quit [Ping timeout: 264 seconds] 10:32 -!- tmus [~tmus@194.177.231.78] has quit [Quit: Leaving] 10:38 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 276 seconds] 10:40 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 10:48 -!- dougsland [douglas@nat/redhat/x-gjxjwsnziwgrgqbw] has quit [Ping timeout: 256 seconds] 11:46 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 240 seconds] 11:51 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 11:54 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 12:13 < mlz> provoostenator, i'm having the same issue when trying to open a channel 12:13 < mlz> { "code" : -1, "message" : "Error packet: channel 1fc5810a3a42699e97573c6f28e6b01712b985092a349f9d3a4d159a7f65e708: Unacceptable channel constraints: minimum HTLC value is too large: 0" } 12:14 < provoostenator> mlz see https://github.com/ElementsProject/lightning/issues/997 12:14 < mlz> provoostenator, thanks, glad i'm not the only one 12:38 -!- llou [~textual@cm-83-97-182-195.telecable.es] has joined #c-lightning 13:15 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 260 seconds] 13:21 -!- jojeyh [~delphi@2602:306:b8b6:b970:b4ab:2df2:581f:7ebf] has quit [Ping timeout: 276 seconds] 13:35 -!- booyah is now known as blkshp 13:36 -!- blkshp is now known as Guest24100 13:36 -!- Guest24100 [~bb@193.25.1.157] has quit [Killed (hitchcock.freenode.net (Nickname regained by services))] 13:36 -!- Guest24100 [~bb@193.25.1.157] has joined #c-lightning 13:36 -!- Guest24100 is now known as booyah 13:36 -!- booyah [~bb@193.25.1.157] has quit [Client Quit] 13:36 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 13:41 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #c-lightning 14:06 -!- tan90 [605261e9@gateway/web/freenode/ip.96.82.97.233] has joined #c-lightning 14:09 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has joined #c-lightning 14:12 -!- hba [2ec45204@gateway/web/freenode/ip.46.196.82.4] has joined #c-lightning 14:14 -githubby:#c-lightning- [lightning] graphite opened pull request #1003: Pylightning (master...pylightning) https://git.io/vAZLo 14:19 < hba> hi 14:19 < hba> Can I access the private key of the newly created lnd address 14:21 < hba> I actually created more than one btc address, which is valid 14:28 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has quit [Ping timeout: 268 seconds] 14:49 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 14:53 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 248 seconds] 15:13 < tan90> people said we can earn fees from hosting lightning node, do I have to setup some command to make my node collect fee? like "lightning-cli set-fee"? 15:21 -!- Poodle [d48bcf55@gateway/web/freenode/ip.212.139.207.85] has quit [Quit: Page closed] 15:25 < mlz> no 15:52 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-aqqlkbjngmrfcfto] has joined #c-lightning 15:54 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 15:54 -!- aproc [~aproc@2605:6000:e503:8300:2828:d4f9:cb3f:f5fd] has quit [Ping timeout: 265 seconds] 15:58 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 248 seconds] 16:01 -!- lxer [~lx@ip5f5bd676.dynamic.kabel-deutschland.de] has quit [Ping timeout: 260 seconds] 16:07 -!- aproc [~aproc@2605:6000:e503:8300:297a:74e9:9194:98d] has joined #c-lightning 16:20 -!- jojeyh [~delphi@2602:306:b8b6:b970:b4ab:2df2:581f:7ebf] has joined #c-lightning 16:20 -!- tan90 [605261e9@gateway/web/freenode/ip.96.82.97.233] has quit [Ping timeout: 260 seconds] 16:22 -!- hba [2ec45204@gateway/web/freenode/ip.46.196.82.4] has quit [Ping timeout: 260 seconds] 16:48 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 16:49 -!- shesek [~shesek@bzq-84-110-55-65.cablep.bezeqint.net] has joined #c-lightning 16:49 -!- shesek [~shesek@bzq-84-110-55-65.cablep.bezeqint.net] has quit [Changing host] 16:49 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 16:52 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 256 seconds] 17:00 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 17:05 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 256 seconds] 17:58 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 18:03 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 260 seconds] 18:16 -!- bryan_w [~is@2600:2108:9:8a90:72a3:5780:f492:1888] has joined #c-lightning 18:49 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 18:53 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 240 seconds] 19:17 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 276 seconds] 19:28 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 19:51 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 19:55 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 19:55 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 240 seconds] 20:26 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #1004: travis: Correctly process $SOURCE_CHECK_ONLY. (master...travis-source-check-only) https://git.io/vAZgM 20:55 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 21:00 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 248 seconds] 21:59 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 22:16 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 240 seconds] 22:50 -!- hba [55617ae8@gateway/web/freenode/ip.85.97.122.232] has joined #c-lightning 22:54 -!- hba [55617ae8@gateway/web/freenode/ip.85.97.122.232] has quit [Client Quit]