--- Log opened Tue Dec 14 00:00:00 2021
00:00 -!- rusty [~rusty@118.102.87.68] has quit [Ping timeout: 250 seconds]
01:36 -!- michaelfolkson2 [~michaelfo@138.68.143.20] has joined #c-lightning
01:38 -!- DeanWeen [~dean@nonplayercharacter.me] has joined #c-lightning
01:39 -!- Nebraskka_ [~Nebraskka@user/nebraskka] has joined #c-lightning
01:40 -!- pi1 [~pi@user/k3tan] has joined #c-lightning
01:40 -!- qubenix_ [~qubenix@66.172.11.228] has joined #c-lightning
01:41 -!- kexkey_ [~kexkey@static-198-54-132-121.cust.tzulo.com] has joined #c-lightning
01:46 -!- Netsplit *.net <-> *.split quits: kexkey, Nebraskka, michaelfolkson, k3tan, DeanGuss, qubenix
01:46 -!- qubenix_ is now known as qubenix
01:46 -!- Nebraskka_ is now known as Nebraskka
04:24 -!- bocho [~bacho@242-189-16-190.fibertel.com.ar] has joined #c-lightning
04:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:40 -!- bocho [~bacho@242-189-16-190.fibertel.com.ar] has quit [Remote host closed the connection]
05:54 -!- bocho [~bacho@242-189-16-190.fibertel.com.ar] has joined #c-lightning
06:05 < bocho> hey everyone, I am reading c-lightning code and trying to understand it, I would like to find where it starts to create a channel and see where are some default values like `to_self_delay` that we can see in this test, any clue?
06:05 < bocho> https://github.com/ElementsProject/lightning/blob/master/channeld/test/run-full_channel.c#L402
06:25 < jasan> bocho: Hello! `git grep`-ing the source is showing some other lines setting it to 144, a few tests set it to less (10, 5 - but that would be for local regtest I guess).
06:27 < jasan> common/channel_config.h contains a nice comment referring to BOLT #2
06:27 < cdecker[m]> Yeah, that's one of the complexities of the protocol right there: we set the timeout on the remote party, while they set ours (it's a security parameter expressing our confidence of being able to react and confirm a tx in response to an action they take, hence the cross-over here)
06:31 < bocho> thank for the response, but where you set to_self_delay = 144 (or anything else) in a channel creation on mainnet?
06:37 < cdecker[m]> Looking through the code I find this: https://github.com/ElementsProject/lightning/blob/335ef3fb69f923f6f30213f68881d10ee6d977ed/lightningd/opening_common.c#L155-L162
06:37 < cdecker[m]> This points towards the config in `lightningd`
06:39 < cdecker[m]> Which leads us to the default config here: https://github.com/ElementsProject/lightning/blob/335ef3fb69f923f6f30213f68881d10ee6d977ed/lightningd/options.c#L737
06:40 < cdecker[m]> A word of caution though: as explained above, if you change this value to something low, you'll actually give your peer more freedom, and not yourself (especially don't set it to 0) since then the peer can cheat for free
06:42 < bocho> @cdecker[m], I understand, thank you :)
06:48 < cdecker[m]> Anytime
07:01 -!- DeanWeen is now known as deanguss
07:01 -!- deanguss [~dean@nonplayercharacter.me] has quit [Changing host]
07:01 -!- deanguss [~dean@user/deanguss] has joined #c-lightning
07:02 -!- An0rak [An0rak@user/an0rak] has quit [Remote host closed the connection]
07:16 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
07:16 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
08:00 < vincenzopalazzo> Guys small question on the dual-funding regarding the construction of the transaction. In particular the draft said the following things
08:00 < vincenzopalazzo> ## Interactive Transaction Construction
08:00 < vincenzopalazzo> Interactive transaction construction allows two peers to collaboratively
08:00 < vincenzopalazzo> build a transaction for broadcast.  This protocol is the foundation
08:00 < vincenzopalazzo> for dual-funded channels establishment (v2).
08:00 < vincenzopalazzo> This means that the both node can path on the blockchain the same transaction?
08:06 -!- bocho [~bacho@242-189-16-190.fibertel.com.ar] has quit [Ping timeout: 260 seconds]
08:13 < darosior> Not sure i get the question. It means that both nodes can contribute UTxOs to be spent to create the channel funding UTxO.
09:13 -!- michaelfolkson2 is now known as michaelfolkson
09:35 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
09:40 -!- bocho [~bacho@242-189-16-190.fibertel.com.ar] has joined #c-lightning
10:04 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
10:04 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
10:36 -!- TracaChang [~QSDkl@gateway/tor-sasl/tracachang] has joined #c-lightning
10:37 -!- rusty [~rusty@118.102.87.68] has joined #c-lightning
10:55 -!- TracaChang [~QSDkl@gateway/tor-sasl/tracachang] has quit [Remote host closed the connection]
11:30 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
11:30 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
12:40 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
12:41 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
12:47 -!- rusty [~rusty@118.102.87.68] has quit [Ping timeout: 252 seconds]
12:49 -!- bocho [~bacho@242-189-16-190.fibertel.com.ar] has quit [Ping timeout: 256 seconds]
12:52 < andrewtoth_> What is the policy for reusing plugin option names?
12:52 < andrewtoth_> I haven't been able to find any previous discussion on this
12:52 < andrewtoth_> It doesn't fail, but the option values aren't registered properly
12:53 < andrewtoth_> For example, bitcoin-rpcuser is registered to bcli, and if I make a new plugin with it then it appears under both for --help and listconfigs
12:53 < andrewtoth_> however, setting it `bitcoin-rpcuser=user` will only show `user` for bcli, and not the new plugin
12:56 < andrewtoth_> Should there be some namespacing for plugin options and methods?
12:57 < andrewtoth_> Reusing the same plugin value, while desired for my case, could cause problems with other plugins
12:57 < andrewtoth_> but not being able to use two different plugins because the authors created conflicting names is a big problem too
13:05 < vincenzopalazzo> andrewtoth_: I think there is no policy to reuse the plugin option name, I mean if you declare the same plugin option name and disable the old one you should be have the correct behaviour
13:05 < vincenzopalazzo> but in your cause I noted that you have not
13:06 < vincenzopalazzo> I never tried but maybe we should fail in case of conflicts?
13:08 < andrewtoth_> I think we need some kind of namespacing rule
13:08 < andrewtoth_> Otherwise you can't just pick and choose plugins because the authors might have reused names
13:08 < vincenzopalazzo> to make more verbose the command line? mh, not sure about that
13:09 < vincenzopalazzo> usualy by convention, I use as prefix the name of the plugin
13:09 < vincenzopalazzo> I think we need a some point define some convention in the plugins system, to make also some install management system for plugins
13:41 -!- rojiro [~rojiro@gateway/tor-sasl/rojiro] has quit [Remote host closed the connection]
13:42 -!- rojiro [~rojiro@gateway/tor-sasl/rojiro] has joined #c-lightning
15:02 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning
15:17 -!- jespada [~jespada@87.74.33.157] has quit [Quit: Textual IRC Client: www.textualapp.com]
15:41 -!- jespada [~jespada@87.74.33.157] has joined #c-lightning
17:25 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:53 -!- An0rak [An0rak@user/an0rak] has joined #c-lightning
19:39 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 250 seconds]
19:55 -!- rojiro [~rojiro@gateway/tor-sasl/rojiro] has quit [Ping timeout: 276 seconds]
19:56 -!- rojiro [~rojiro@gateway/tor-sasl/rojiro] has joined #c-lightning
20:20 -!- rojiro_ [~rojiro@gateway/tor-sasl/rojiro] has joined #c-lightning
20:22 -!- rojiro [~rojiro@gateway/tor-sasl/rojiro] has quit [Remote host closed the connection]
20:25 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 265 seconds]
21:35 -!- rusty [~rusty@pa49-178-106-254.pa.nsw.optusnet.com.au] has joined #c-lightning
22:05 -!- rusty [~rusty@pa49-178-106-254.pa.nsw.optusnet.com.au] has quit [Ping timeout: 240 seconds]
--- Log closed Wed Dec 15 00:00:01 2021