--- Log opened Wed Mar 31 00:00:11 2021
01:37 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds]
01:38 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
02:19 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 276 seconds]
02:23 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning
02:30 -!- csknk [~csknk@unaffiliated/csknk] has joined #c-lightning
02:40 -!- snyke is now known as cdecker
02:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:55 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has joined #c-lightning
04:17 -!- csknk [~csknk@unaffiliated/csknk] has quit [Ping timeout: 260 seconds]
04:20 -!- michaelfolkson2 is now known as michaelfolkson
04:37 < k3tan> i setup a channel about a year ago. i've just force closed it now. the peer was offline at the time of closure. his funds went into a single sig wallet (which he has access to), my side went into a multisig address and not in my possession. is there some kind of time lock before it gets released into my wallet? how long could that take?
04:38 < k3tan> 144 blocks have passed since i force closed
04:40 < darosior> k3tan: depends on your channel, you can see the timelock duration in listpeers
04:41 < darosior> And do a quick computation (with the confirmation height) to know at which point your output is going to be sweeped
04:43 < k3tan> "their_to_self_delay": 144,
04:43 < k3tan>                "our_to_self_delay": 1033,
04:43 < k3tan> is that what i'm looking for?
04:49 < darosior> Yes :)
04:49 < darosior> From https://lightning.readthedocs.io/lightning-listpeers.7.html
04:49 < darosior> > our_to_self_delay: The number of blocks that you must wait to claim your funds, if you close unilaterally.
04:56 < k3tan> thanks darosior
05:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
05:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
05:33 -!- belcher_ is now known as belcher
05:58 -!- csknk [~csknk@unaffiliated/csknk] has joined #c-lightning
07:38 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
07:39 < carboncarlo> Question regarding the channel creation plugin for Boltz. When I try $lightning-cli addchannelcreation 5000000000 90 I get the following error:
07:40 < carboncarlo> {
07:40 < carboncarlo>    "code": -32600,
07:40 < carboncarlo>    "message": "Error while processing addchannelcreation: 'id'"
07:40 < carboncarlo> }
07:40 < carboncarlo> I tried connecting to Boltz Node first, but that didn't change anything. What could be wrong here?
07:42 < carboncarlo> I'll ask in a Boltz chat, but maybe someone here already encountered this error.
07:49 < carboncarlo> and a quick other question: while a channel close tx is awaiting a conf, will the node still forward payments in other channels? because I didn't get any new entries in listforwards since I started a channel close.
07:51 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
07:52 < vincenzopalazzo> carboncarlo: Sure during the confirmation of channel X you can send payment using other channel different form X. Of course, a route must exist
08:26 -!- csknk [~csknk@unaffiliated/csknk] has quit [Ping timeout: 240 seconds]
08:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
09:18 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
09:20 < carboncarlo> vincenzopalazzo ok thanks, yes I see now other forwarded payments, that was just a coincidence.
09:20 < carboncarlo> I asked in the Boltz debug chat and they are looking into it about the channel creation swap plugin error.
09:22 < vincenzopalazzo> carboncarlo I'm sorry I don't know nothings about boltz :)
09:23 < carboncarlo> vincenzopalazzo sure thing, they wrote the plugin, I just wanted to update about the error that I encountered =)
09:25 < vincenzopalazzo> Yes sure :)
09:31 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
10:04 -!- csknk [~csknk@unaffiliated/csknk] has joined #c-lightning
10:15 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning
11:01 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has quit [Ping timeout: 240 seconds]
11:38 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving]
12:02 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
12:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
12:11 -!- vincenzopalazzo [~vincenzop@host-87-17-34-148.retail.telecomitalia.it] has joined #c-lightning
12:52 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
12:53 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Client Quit]
13:15 -!- mode/#c-lightning [+o rusty] by ChanServ
13:16 -!- rusty changed the topic of #c-lightning to: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning  Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.10.0 Logs at http://gnusha.org/c-lightning/ Dev Roadmap: https://github.com/ElementsProject/lightning/wiki
13:16 -!- mode/#c-lightning [-o rusty] by rusty
13:42 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
13:42 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
16:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 258 seconds]
16:25 -!- vincenzopalazzo [~vincenzop@host-87-17-34-148.retail.telecomitalia.it] has quit [Quit: Leaving]
19:22 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
19:41 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
20:20 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
20:24 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 268 seconds]
20:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
21:10 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving]
21:17 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
21:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
21:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
21:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
21:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:44 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
22:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
22:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
--- Log closed Thu Apr 01 00:00:12 2021