--- Day changed Mon Jun 18 2018 00:15 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 00:15 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 00:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 00:51 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 01:52 < sturles> I get a different error than I should when running make check. Connect to 032cf15d1ad9c4a08d26eab1918f732d8ef8fdc6abb9640bf3db174372c491304e is supposed to time out, but I get "No address known" instead. I get the same message on a live node. Is there something wrong about the test? 01:52 < sturles> https://0bin.net/paste/MVglt9QSn+WrWhhA#ZiLDTbpsLBJReNfAl2kQ2wRmAAAF7zR3hVDX1YcL1ut 02:03 -!- tiagotrs [~user@p3EE2DC65.dip0.t-ipconnect.de] has joined #c-lightning 02:03 -!- tiagotrs [~user@p3EE2DC65.dip0.t-ipconnect.de] has quit [Changing host] 02:03 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 02:44 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vjQoZ 02:44 -githubby:#c-lightning- lightning/master f66cf87 Christian Decker: gossip: Avoid integer count overflow in gossip_store... 03:09 -githubby:#c-lightning- [lightning] cdecker force-pushed master from f66cf87 to 71ec819: https://git.io/vWE2d 03:09 -githubby:#c-lightning- lightning/master 71ec819 Christian Decker: gossip: Avoid integer count overflow in gossip_store... 03:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:30 -githubby:#c-lightning- [lightning] cdecker closed pull request #1584: Release notes for 0.6 "I Accidentally The Smart Contract" (master...relnotes) https://git.io/vhPM8 03:31 < rusty> cdecker: w00t! 03:31 -githubby:#c-lightning- [lightning] cdecker closed pull request #1595: Bolt updates (no code changes) (master...bolt-updates) https://git.io/vhMl5 03:31 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vjbuk 03:31 -githubby:#c-lightning- lightning/master 2d95ed7 Christian Decker: pay: Use `locktime_max` as maximum cumulative CLTV delta... 03:33 -githubby:#c-lightning- [lightning] cdecker closed pull request #1590: Added wallet related error codes (master...fund-error-codes) https://git.io/vhXHV 03:37 < sturles> When I try to give parameters to pay, to adjust maxfeepercent and maxdelay, it always fails with "msatoshi parameter unnecessary". Any way to get past this? 03:40 < sturles> I can't specify maxfeepercent without specifying mmsatoshi as well. 03:45 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vjxII 03:45 -githubby:#c-lightning- lightning/master 654fa9d Christian Decker: doc: Fixed typo in the release notes... 03:50 < rusty> sturles: yes, either empty parameter ('') or use named parameters... 03:56 < sturles> Empty parameter or named parameter (maxfeeprcent=1) doesn't work. Using lightning-cli. 03:58 < sturles> { "code" : -32602, "message" : "msatoshi parameter unnecessary" } 03:59 < sturles> Using only empty parameters after the bolt11 code works, but doesnt't achieve anything.. 04:02 -githubby:#c-lightning- [lightning] cdecker tagged v0.6rc1 at fcc8205: https://git.io/vjjrW 04:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 04:07 -githubby:#c-lightning- [lightning] cdecker created issue-1587 (+1 new commit): https://git.io/feezs 04:07 -githubby:#c-lightning- lightning/issue-1587 2f67386 Christian Decker: gossip: Add an assert that we don't queue empty messages... 04:56 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 04:57 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 04:58 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:16 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 265 seconds] 06:01 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 06:09 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 06:12 -!- j9m [~j9m@47.157.125.55] has joined #c-lightning 06:24 -!- berndj [~berndj@197.242.93.82] has quit [Quit: ZNC - http://znc.in] 06:28 -!- berndj [~berndj@azna.co.za] has joined #c-lightning 06:33 -!- _mr_e [63e63289@gateway/web/freenode/ip.99.230.50.137] has quit [Ping timeout: 260 seconds] 07:27 -!- grafcaps [~haroldbr@107.147.175.194] has joined #c-lightning 07:32 -!- grafcaps [~haroldbr@107.147.175.194] has quit [Ping timeout: 264 seconds] 07:51 -!- deusexbeer [~deusexbee@095-129-169-151-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 240 seconds] 07:52 -!- deusexbeer [~deusexbee@095-129-175-233-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 08:02 -githubby:#c-lightning- [lightning] wythe closed pull request #1569: Improved JSON-RPC Parameter Processing (master...parse-params) https://git.io/vhrxU 08:04 -!- _mr_e [18723113@gateway/web/freenode/ip.24.114.49.19] has joined #c-lightning 08:04 < _mr_e> Hi rusty... so I see your tx confirmed, I tried to send this morning. Still no path found:( 08:05 < _mr_e> I am also curious, I tried satohis place and they work by simply having you send a payment to the generate invoice, without having to open a channel with them. Do you have any insights on how they are pulling this off? How they can manage to keep enough incoming channels for everyon's deposits? 08:06 < _mr_e> I will require this to work for a new service I am building so I'm glad to see it is indeed doable, but it will be hard to find people to keep opening enough channels with me to stay funded. 08:07 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Read error: Connection reset by peer] 08:08 -!- ctrlbreak [~ctrlbreak@142.162.42.47] has quit [Read error: Connection reset by peer] 08:08 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #c-lightning 08:08 -!- ctrlbreak [~ctrlbreak@142.162.42.47] has joined #c-lightning 08:13 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 08:20 < _mr_e> even starblocks seems to be well funded enough to consistently process payments. How are they doing it? 08:54 -!- fusion45 [~fusion44@31.6.30.190] has joined #c-lightning 08:57 < molz> _mr_e, you don't have to have a direct channel to SP or any node to pay them, this is how LND works 08:58 < molz> er s/LND/LN 09:00 < molz> if you have channels with node A, B, C, D, and one or all of them have channels with E and enough liquidity on the other side of their channel, you can send payment to E, because either A, or B, or C, or D will forward your payment 09:01 < molz> i've never had a direct channel with satoshis.place, but i've been able to send payments to it 09:02 < molz> you need to set up nodes on testnet and figure this out 09:03 -!- tiagotrs [~user@p5DDB4F52.dip0.t-ipconnect.de] has joined #c-lightning 09:03 -!- tiagotrs [~user@p5DDB4F52.dip0.t-ipconnect.de] has quit [Changing host] 09:03 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 09:04 < _mr_e> yes, I would like to be a node that received payments, without the user having to open a channel with me 09:04 < _mr_e> similiar to satohis place or starblocks 09:05 < _mr_e> they just generate an invoice and I can pay them no problem. but yesterday rusty was telling me I cannot receive payments unless i have enough people who have opened channels with me. So I am wondering how to provide a similiar user experience as those services, without having to chase a bunch of people down to lock up their funds with my service? 09:06 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:06 < _mr_e> i have opened channels with many nodes, yet I cannot get a route to pay my node 09:37 < molz> _mr_e, can you pay to those nodes that you opened channels ? 09:40 < molz> ah.. i can see the problem 09:45 < _mr_e> yes, i can pay satoshis place 09:45 < _mr_e> i can pay starblocks 09:45 < _mr_e> from my node and my android eclair wallet 09:45 < _mr_e> but from my android eclair wallet, i cannot pay my node 09:45 < _mr_e> so I am trying to figure out what those services are doing that allow me to pay them without opening a channel to them directly 09:46 < _mr_e> because I need to do a similiar user experience for my app 09:46 < molz> did you set up a few c-lightning nodes and they have direct channels to each other but you can't get the funder node to pay the other node or something? 09:47 < _mr_e> I have 1 clightning node 09:47 < _mr_e> with 4 channels opened to other nodes 09:47 < _mr_e> including the same node run by starblocks or asinq 09:48 < molz> on testnet right? 09:48 < _mr_e> i then downloaded the eclair android wallet 09:48 < _mr_e> yes testnet 09:48 < _mr_e> I opened a channel to the asinq node on eclair 09:48 < _mr_e> using that I can successfuly pay satoshi's place or starblocks 09:48 < _mr_e> but I cannot pay my clightning node 09:50 < molz> yes i'm familiar with this issue, it's here: https://github.com/ACINQ/eclair/issues/591 09:51 < molz> i think c-lightning needs to fix something 09:52 < molz> _mr_e, pay more to starblocks 09:52 < molz> when it's over the 1% reserve amount, your eclair will be able to pay to your c-lightning node 10:48 -!- Xian001 [~xian001@47.184.129.94] has joined #c-lightning 10:49 -!- Xian001 is now known as ThrobbingSausage 11:26 -!- _mr_e [18723113@gateway/web/freenode/ip.24.114.49.19] has quit [Ping timeout: 260 seconds] 12:58 -!- fusion45 [~fusion44@31.6.30.190] has quit [Quit: Leaving.] 13:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 13:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:28 -!- _mr_e [187231d8@gateway/web/freenode/ip.24.114.49.216] has joined #c-lightning 14:28 < _mr_e> Yes, so that does look like my issue, but somehow it appears satoshis place has solved the problem... Does nobody know how they've done it? 14:29 < molz> what do you mean? 14:36 -!- jojeyh [~delphi@2602:306:b8b6:b970:30d8:d7c2:d20:7f35] has quit [Ping timeout: 245 seconds] 14:39 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 14:42 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 14:42 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 14:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds] 14:47 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 276 seconds] 15:02 < _mr_e> i mean why can everyone have no problem paying satoshis place without opening a channel to them 15:02 < _mr_e> you can just simply pay the invoice 15:02 < _mr_e> which is the same user experience I'd like my app to support 15:17 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Quit: Lost terminal] 15:20 -!- ThrobbingSausage [~xian001@47.184.129.94] has quit [] 15:27 -!- _mr_e [187231d8@gateway/web/freenode/ip.24.114.49.216] has quit [Ping timeout: 260 seconds] 15:48 -!- CubicEarths [~cubiceart@2600:100f:b010:c303:84c3:bc56:b3fe:128b] has joined #c-lightning 15:49 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-yzpbnfsoljhuwxqs] has joined #c-lightning 16:10 -!- CubicEarths [~cubiceart@2600:100f:b010:c303:84c3:bc56:b3fe:128b] has quit [Remote host closed the connection] 17:54 -!- _mr_e [63e63289@gateway/web/freenode/ip.99.230.50.137] has joined #c-lightning 17:54 < _mr_e> has anyone replied to me yet, I lost connection and all messages again:( 18:09 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-yzpbnfsoljhuwxqs] has quit [Quit: Connection closed for inactivity] 18:28 < _mr_e> So apparantly I can't receive funds more then the channel I opened... ? 18:28 < _mr_e> So you can receive payments unless you spend 18:28 < _mr_e> yet I have nothing I want to buy 18:28 < _mr_e> especially on mainnet 18:29 < _mr_e> again, how does something like satoshi's place handle this 18:29 < _mr_e> are you supposed to set up a second node and send money to yourself? 19:19 < molz> oh hey _mr_e i was going to reply but you were gone 19:20 < molz> _mr_e, satoshis.place has something to sell, so people send their payments to sp node 19:20 < molz> sp also has direct channels with some people 19:21 < molz> so i made some txs to sp today and they went thru 7 hops, it's like a chain of channels, a has channel with b, b has channel with c, and so on and the last node has a channel with SP 19:27 < _mr_e> right, so how do you think they went about getting enough channels open to them to be able to fund all the payments they've been receiving? 19:28 < _mr_e> Is their any kind of best practice or documentation on how to properly set yourself up to run such a service? 19:39 < molz> they have an interesting product to sell which is satoshis.place, so people open direct channels to them, and when they buy the pixels, they pay, im not sure how else i can explain this? 19:43 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 19:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 19:58 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 256 seconds] 20:20 < _mr_e> but the point is, you can pay them without opening a channel 20:21 < _mr_e> so you are saying they first had to gain a mass of people who opened channels, then once they did they were able to start offer channelless deposits? 20:22 < _mr_e> i would expect people would be drained of their channels quicker then people opening them 20:22 < _mr_e> I would expect lots of failed routes 20:28 -!- Test [63e63289@gateway/web/freenode/ip.99.230.50.137] has joined #c-lightning 20:29 -!- Test is now known as Guest57432 20:39 -!- Guest57432 [63e63289@gateway/web/freenode/ip.99.230.50.137] has quit [Ping timeout: 260 seconds] 20:44 < molz> "channelless deposits"? there's not "channel deposits" so im not sure what you mean 20:45 < molz> if there's not a route to pay SP then i would try to open a direct channel to SP but at this rate, it's so popular, many people have been making payments to it so i don't see this issue yet 20:46 < molz> <_mr_e> but the point is, you can pay them without opening a channel <-- false, because I opened a channel to other nodes, you can't pay anyone if you don't open a single channel 20:47 < molz> and your chances of paying SP increase without having a direct channel to SP when you have many channels with other people 20:48 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:54 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 20:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit] 21:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:07 < windsok> experimenting with setting up a lite node with spruned and c-lightning 23:23 < windsok> weird bug with spruned. When c-lightning starts up, it queries "getblockcount" which is currently returning 528171, but even so c-lightning tries to get the blockhash for the next non-existent block 528172. When 528172 is mined it will start trying to pull 528173 23:24 < windsok> so just errors over and over with 2018-06-19T06:21:52.550Z lightningd(32665): bitcoin-cli getblockhash 528172 exited with status 5 23:24 < windsok> weird since bitcoin-cli is returning the correct block height. Can't figure out why c-lightning would do that 23:26 -!- tiagotrs [~user@p3EE2DE01.dip0.t-ipconnect.de] has joined #c-lightning 23:26 -!- tiagotrs [~user@p3EE2DE01.dip0.t-ipconnect.de] has quit [Changing host] 23:26 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 23:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 23:47 < windsok> or is that normal behaviour after startup.. it just keeps polling for the next block until it exists? 23:54 < windsok> hmm in any case, after connecting to a lightning peer it seems to have stopped doing that