--- Day changed Sat Jul 28 2018 00:41 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 00:45 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 240 seconds] 00:57 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 00:58 -!- booyah_ is now known as booyah 01:02 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 248 seconds] 01:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:18 -!- tiagotrs [~user@i5E863AB5.versanet.de] has joined #c-lightning 01:18 -!- tiagotrs [~user@i5E863AB5.versanet.de] has quit [Changing host] 01:18 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 01:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 01:56 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 02:00 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 240 seconds] 02:06 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #c-lightning 02:06 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 02:06 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #c-lightning 02:07 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Remote host closed the connection] 02:45 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 02:50 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 268 seconds] 03:53 -!- deusexbeer [~deusexbee@093-092-181-127-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 04:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 04:50 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:01 -!- ken2812221 [~User@1.200.198.248] has joined #c-lightning 05:45 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 06:01 -!- qubenix [~qubenix@23.226.131.131] has joined #c-lightning 06:08 -!- j9m [~j9m@47.157.125.55] has joined #c-lightning 06:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds] 06:22 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 06:27 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 268 seconds] 06:54 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 08:03 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 08:10 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 08:14 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 240 seconds] 08:52 -!- mdrollette [~mdrollett@feynman.drollette.com] has quit [Quit: ZNC 1.7.0 - https://znc.in] 08:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:13 -!- mdrollette [~mdrollett@feynman.drollette.com] has joined #c-lightning 09:39 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 09:50 -!- j9m [~j9m@47.157.125.55] has quit [Ping timeout: 256 seconds] 10:58 -!- jav_v [2e1aee10@gateway/web/freenode/ip.46.26.238.16] has joined #c-lightning 10:59 -!- jav_v [2e1aee10@gateway/web/freenode/ip.46.26.238.16] has quit [Client Quit] 12:15 -!- deusexbeer [~deusexbee@093-092-181-127-dynamic-pool-adsl.wbt.ru] has quit [Read error: Connection reset by peer] 12:16 -!- deusexbeer [~deusexbee@079-170-139-044-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 12:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:35 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 12:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:45 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 256 seconds] 12:48 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 13:48 -githubby:#c-lightning- [lightning] wythe opened pull request #1770: Remove sigaction from run-param test (master...remove-sigaction) https://git.io/fNgwl 13:49 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 248 seconds] 14:43 -!- User__ [~User@1.200.198.248] has joined #c-lightning 14:43 -!- ken2812221 [~User@1.200.198.248] has quit [Read error: Connection reset by peer] 14:47 -!- pcre [~quassel@anon-34-234.vpn.ipredator.se] has joined #c-lightning 14:47 -!- ken2812221 [~User@180.217.140.78] has joined #c-lightning 14:47 -!- User__ [~User@1.200.198.248] has quit [Ping timeout: 260 seconds] 15:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 15:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 15:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:11 -!- pcre [~quassel@anon-34-234.vpn.ipredator.se] has quit [Remote host closed the connection] 16:42 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1771: Fix channel reserve enforcement (master...guilt/test-channel-reserve) https://git.io/fNgPk 17:04 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 17:08 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds] 18:39 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 18:43 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 240 seconds] 19:14 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1772: Add and populate a CHANGELOG.md: following wisdom from keepachangelog.com (master...keepachangelog.com) https://git.io/fNgMu 19:50 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 19:55 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 240 seconds] 20:41 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 21:39 < molz> could someone give me an example for getroute 21:39 < molz> i've tried different numbers for this formula but it doesnt work: getroute id msatoshi riskfactor [cltv] [fuzzpercent] [seed] 21:40 < rusty> molz: testsuite uses it... 21:40 < molz> oh hi rusty, how do you use testsuite? 21:40 < rusty> molz: getroute 100000 1 should work. 21:41 < molz> ah cool 21:42 < rusty> molz: what problem were you having? 21:43 < molz> rusty, i thought i had to fill in data for each of those fields except the last one 21:43 < molz> $ lightning-cli getroute 024a2e265cd66066b78a788ae615acdc84b5b0dec9efac36d7ac87513015eaf6ed 50000000 0 9 0.0 21:43 < molz> { "code" : -32602, "message" : "'fromid' of '0.0' is invalid'", "data" : 21:43 < molz> { 21:43 < molz> "fromid": "0.0" 21:43 < molz> } } 21:44 < rusty> molz: hmm, manpage is out of date. 21:44 < molz> rusty, so '1' is 1% for riskfactor? 21:45 < rusty> molz: to quote manpage: 21:45 < rusty> There are two considerations for how good a route is: how low the fees are, and how long your payment will get stuck if a node goes down 21:45 < rusty> during the process. The 'riskfactor' floating-point field controls this tradeoff; it is the annual cost of your funds being stuck (as a percentage), multiplied by the percentage chance of each node failing. 21:45 < rusty> For example, if you thought there was a 1% chance that a node would fail, and it would cost you 20% per annum if that happened, 'riskfactor' would be 20. 21:45 < rusty> If you didn't care about risk, 'riskfactor' would be zero. 21:47 < molz> rusty, thank you, got it :) 21:48 < rusty> molz: and optional fields can either be all spelled out in order, or 'null' to leave defaults, or use -k and then 'id=...' 'msatoshi=...' 'riskfactor=..' etc. in any order. 21:54 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 240 seconds] 22:01 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 22:03 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 22:23 < molz> rusty, i see.. thank you 22:23 < molz> rusty, one more question if you don't mind: do we have "fundchannel all" like "withdraw all" ? 22:24 < molz> i don't see in the help list so i guess we don't have it 22:24 < rusty> molz: hmm, no. I guess it would fund what we ahve, or max possible? 22:24 < molz> yes 22:24 < molz> but not over the allowed max amount 22:26 < rusty> molz: actually, it seems like it *does* support 'all' (shared parsing and all that!) but it won't cap it... 22:26 < molz> suppose i have 0.01 btc in so many utxo sets... and i want to use them all to open a channel, and i can't figure out how i can use them all after paying a fee 22:26 < molz> hm 22:27 < rusty> molz: let me see if I can fix it... 22:39 < rusty> molz: seems to work. Adding test now. You can add an issue if you want, then it's easy to credit you? 22:45 < molz> omg, thanks, rusty, you're fast :D 22:46 < rusty> molz: just a bit embarrassed ;) Seems like 'any' was an undocumented feature, since we actually test it in the testsuite! We don't test the "more funds than we're allowed' case though! 22:47 < molz> ah i see... still great :) 22:49 < molz> ok im writting up an issue :D 22:49 < rusty> molz: actually, it *is* documented in the manpage, even. Things I learn :) 22:49 < molz> oooo 22:50 < rusty> lightning-cli help fundchannel ? 22:50 < molz> yes i see it 22:51 < molz> satoshi is the amount in satoshis taken from the internal wallet to fund the channel. The 22:51 < molz> string all can be used to specify all available funds. This value cannot be less than the 22:51 < molz> dust limit, currently set to 546. And it must be less than 1<<24 (approximately 0.16778 22:51 < molz> BTC). 22:54 < rusty> molz: give me issue # when you've got it, and I'll add it to commit msg :) 22:54 < molz> hm i thought you said we already have this? 22:55 < molz> im trying to withdraw some coins from my test node so i can test this lol 22:56 < rusty> molz: we ahve it, we just don't cap it at max possible: if you hve too many funds it will fail with "max satoshi exceeded" 22:56 < molz> it didn't allow me to fund more than the max amount 22:56 < molz> ah 22:56 < rusty> molz: yeah, I changed it so "any" just becomes "16777215" if you're too rich :) 22:57 < molz> ah i see.. so in case if we have too much, you're going to make the channel to automatically open with the max amount 22:58 < rusty> molz: ack: 22:58 < molz> rusty, thanks but that's ok, i don't need to submit an issue :) 22:58 < rusty> New text: 22:58 < rusty> The string 'all' can be used to specify all available funds (or 16777215 satoshi if more is available). 22:58 < rusty> The value cannot be less than the dust limit, currently set to 546, nor more 22:58 < rusty> than 16777215 satoshi. 22:58 < molz> great :thumbsup: 23:00 < molz> because of htlcs, lightning gives me many small utxo sets 23:01 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1773: fundchannel: cap 'any' at 2^24-1 satoshi. (master...fundchannel-all) https://git.io/fNgSx 23:01 < rusty> molz: heh, you're not supposed to unilaterally close very often, so hope that will get better! 23:02 < molz> rusty, well my c-lightning node still does it to some lnd nodes :) 23:02 < molz> it actually closed my lnd channel a few weeks ago lol 23:04 < molz> yesterday it closed one channel, i'm sure from an lnd node, and here's what was on the screen: 23:04 < molz> "status": [ 23:04 < molz> "CHANNELD_NORMAL:update_fee 250 outside range 253-12470", 23:04 < molz> "ONCHAIN:Tracking our own unilateral close", 23:06 < rusty> molz: yeah, they need to stop doing that :) 23:07 < molz> rusty, i just tested "fundchannel all", it works :) 23:08 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Remote host closed the connection] 23:08 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 23:11 -!- froyer_ [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 23:13 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 240 seconds] 23:13 -!- froyer_ [~froyer@126.121.233.220.static.exetel.com.au] has quit [Read error: Connection reset by peer] 23:13 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 23:14 -!- froyer_ [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 23:16 < molz> rusty, thank you, ttyl :) 23:17 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 256 seconds] 23:18 -!- froyer_ [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 240 seconds] 23:48 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 23:53 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds]