--- Log opened Mon May 10 00:00:50 2021 01:12 -!- belcher_ is now known as belcher 01:14 -!- shafire66 [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has joined #c-lightning 01:14 -!- shafire66 [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has left #c-lightning [] 01:14 -!- shafire66 [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has joined #c-lightning 01:14 < shafire66> hello 01:16 < shafire66> Yesterday, I created a channel with the following command: "lightning-cli fundchannel 2000000sat feerate=slow close_to=". However, feerate and close_to have been ignored. 01:17 < shafire66> What's wrong with my fundchannel command? 01:21 < shafire66> Can I adjust the feerate of a already created channel? 01:33 -!- fiatjaf [~fiatjaf@2804:7f2:298d:1e20:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 250 seconds] 01:35 <@cdecker> shafire66: you're mixing positional with key=value syntax, either add the `id=`, `amount=` in front of the first two arguments as well or leave them out on the feerate and close_to as well 01:35 -!- fiatjaf [~fiatjaf@2804:7f2:2a8f:67a2:ea40:f2ff:fe85:d2dc] has joined #c-lightning 01:41 < shafire66> Leaving them out is a bit complicated, as the optional arguments is long, at least for fundchannel 01:41 < shafire66> the list of* 02:12 < vincenzopalazzo> Hello cdecker, I can ask what is your trick to make the bitcoin rpc up and running with bought of the bitcoin version (pre default wallet and post default wallet)? 02:14 < vincenzopalazzo> I reproduced the problem of bitcoin rpc exception in the local machine and the problem is the lnprototest, but when I try to update the version of lnprototest with the latest version of master I don't receive the exception like that https://github.com/ElementsProject/lightning/pull/4517/checks?check_run_id=2536481745#step:5:2431 02:14 -!- gleb [~gleb@178.150.137.228] has joined #c-lightning 02:14 < vincenzopalazzo> P.S: Maybe it is not the time to update lnprotetest? 02:22 <@cdecker> shafire66: yep,, generally using the `key=value` syntax is better, less confusing and future-proof, but it comes with the downside of having to know what the key-name is for the desired argument. As soon as you start having to skip positional arguments it gets really unwieldy 02:23 <@cdecker> vincenzopalazzo: I thought I had filed a PR on lnprototest to work with 0.21 as well. let me check 02:23 <@cdecker> Yep, here it is: https://github.com/rustyrussell/lnprototest/pull/10/files 02:24 < vincenzopalazzo> cdecker: Yep it is on lnprototest master 02:24 < vincenzopalazzo> :) I upadate te submodule in clightning 02:25 < vincenzopalazzo> and it work on my machine but not on the github actions, and I'm not able to catch the missing part 02:25 < vincenzopalazzo> but any way, I need to search more in deep what is wrong with the github actions 02:25 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-tcmhyidyotayoduh] has left #c-lightning [] 02:25 <@cdecker> It's a quick fix tbh, the better way to do it would be to use getnetworkinfo to detect which version we're running against, and then performing only the necessary steps to create a testing wallet 02:25 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-tcmhyidyotayoduh] has joined #c-lightning 02:26 <@cdecker> Can you share the GH Actions instance that is failing? Maybe I can spot the issue 02:26 < vincenzopalazzo> This is the line https://github.com/ElementsProject/lightning/pull/4517/checks?check_run_id=2536481745#step:5:2431 02:27 < vincenzopalazzo> and this is all the task trace https://github.com/ElementsProject/lightning/pull/4517/checks?check_run_id=2536481745 02:29 <@cdecker> Ouch, yeah that one I failed to address as well 02:30 <@cdecker> Seems we need to switch the URI part of the RPC to make it work again, well that's a bummer 02:31 <@cdecker> So we have a pre-wallet-creation RPC URL that is something like `http://rpcuser:rpcpass@127.0.0.1:8332/` and a post-wallet-creation URL of `http://rpcuser:rpcpass@127.0.0.1:8332/wallet/lnprototest`, though there may be an easier solution 02:31 < vincenzopalazzo> Ah 02:32 < vincenzopalazzo> ok, it is a bad idea if inside the lnprototest we check the version as you mensioned before and it the version it is >=0.21 we create a main wallet, otherwise nothings? 02:32 < vincenzopalazzo> this solution can solve this problem? 02:32 <@cdecker> We might be lucky and `default` is still mapped to the URL without the `/wallet/walletname` suffix 02:33 < vincenzopalazzo> I'm not a lucky person :) 02:33 < vincenzopalazzo> but, I can make some test, I can take this task :) 02:37 <@cdecker> Hehe, ok, so we likely need to have both fixes: 1) check version and create a wallet if none is present, and 2) change the RPC URL if we detect we're working with a wallet (likely in this class https://github.com/ElementsProject/lightning/blob/master/contrib/pyln-testing/pyln/testing/utils.py#L312) 02:39 < vincenzopalazzo> I got it thanks :) I think I have a PR open on ln-prototest where integrate this change 02:39 < vincenzopalazzo> Cool! 02:48 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 02:48 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 03:41 < shafire66> Could someone try to connect to my ipv6-only node for testing purposes? 03:43 < vincenzopalazzo> Testnet or mainet? 03:43 < shafire66> mainnet 03:47 < vincenzopalazzo> Yep I can try a connection with you 04:03 -!- darosior [~darosior@194.36.189.246] has quit [Ping timeout: 260 seconds] 04:23 -!- darosior [~darosior@194.36.189.246] has joined #c-lightning 04:45 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 265 seconds] 04:50 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #c-lightning 05:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 07:45 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-daqmgpiqolbibgyl] has joined #c-lightning 08:18 -!- jarthur [~jarthur@2603-8080-1540-002d-4833-2069-9a58-8526.res6.spectrum.com] has joined #c-lightning 08:31 -!- shafire66 [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has quit [Quit: Connection closed] 09:28 -!- shafire [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has joined #c-lightning 09:29 < shafire> Hi, how do I set the 'Time Lock Delta' and 'Min HTLC' for a channel? 09:47 < darosior> shafire: they are startup configuration options, see https://lightning.readthedocs.io/lightningd-config.5.html 10:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-tcmhyidyotayoduh] has left #c-lightning [] 10:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-tcmhyidyotayoduh] has joined #c-lightning 11:01 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 11:02 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 11:19 -!- shafire [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has quit [Ping timeout: 240 seconds] 12:08 -!- shafire [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has joined #c-lightning 12:09 < shafire> I'm afraid that I still cannot find the settings for "delay" and "htlc_minimum_msat" of a channel... 12:41 < shafire> Can someone please tell me what these channel info means? 12:41 < shafire>          "delay": 34, 12:41 < shafire>          "htlc_minimum_msat": "1msat", 12:42 < fiatjaf> shafire: these seems to be the info you need 12:47 < shafire> can I adjust "delay" with the watchtime-blocks=BLOCKS config? 12:50 < shafire> I just checked the config in lnd and could spot the settings "; bitcoin.defaultremotedelay=" and "; bitcoin.minhtlc=". In c-lightning, I'm a bit lost. 13:01 < shafire> ok, delay is config "cltv-delta=BLOCKS" 13:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:16 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 240 seconds] 14:12 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning 14:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 15:02 -!- vincenzopalazzo [~vincenzop@host-79-23-113-134.retail.telecomitalia.it] has quit [Quit: Leaving] 15:08 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 16:26 -!- shafire [4e2ad60e@HSI-KBW-078-042-214-014.hsi3.kabel-badenwuerttemberg.de] has quit [Quit: Connection closed] 16:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:03 -!- jarthur_ [~jarthur@2603-8080-1540-002d-a172-fa76-51c1-034c.res6.spectrum.com] has joined #c-lightning 17:06 -!- jarthur [~jarthur@2603-8080-1540-002d-4833-2069-9a58-8526.res6.spectrum.com] has quit [Ping timeout: 250 seconds] 17:08 -!- jarthur_ is now known as jarthur 17:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-tcmhyidyotayoduh] has left #c-lightning [] 18:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-tcmhyidyotayoduh] has joined #c-lightning 18:58 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...] 18:59 -!- jarthur [~jarthur@2603-8080-1540-002d-a172-fa76-51c1-034c.res6.spectrum.com] has quit [Ping timeout: 250 seconds] 19:02 -!- spinza [~spin@102.132.245.16] has joined #c-lightning 19:06 < warren> Has someone made a tool that helps you analyze which of your channels have been more productive than others? (volume routed over capital ratio or something) 20:38 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 20:41 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds] 21:26 < rusty> warren: probably, but not that I know of. What I really want is a path map, showing all the channels in a circle, then drawing all the fwd from one to another. That would give you density at a glance (assuming diff colors for success v fail, and wider paths meaning more sats). 22:25 -!- gleb [~gleb@178.150.137.228] has quit [Ping timeout: 252 seconds] 22:27 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 252 seconds] 22:29 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 22:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds] 23:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning --- Log closed Tue May 11 00:00:51 2021