--- Log opened Mon Mar 22 00:00:03 2021
01:50 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Ping timeout: 240 seconds]
02:08 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
02:13 < carboncarlo> In the docs it says that if you used BIP39 words to generate the hsm_secret, you can also use these BIP39 words to regenerate the hsm_secret. However, it does not specify how you would do that. Here's my guess from what I understand: you write down the seed phrase into a text file and then point to that text file with lightning-hsmtool
02:13 < carboncarlo> dumponchaindescriptors path_to_txt. is that about right?
02:24 -!- jonatack_ [~jon@37.166.124.247] has joined #c-lightning
02:27 -!- jonatack [~jon@37.166.26.72] has quit [Ping timeout: 240 seconds]
02:41 < darosior> carboncarlo: no, you'd use the 'generatehsm' command from hsmtool
02:42 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Ping timeout: 240 seconds]
02:45 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
02:47 < carboncarlo> oh ok, so I can test that by deleting the hsm_secret and then use generate again with the same words and password?
02:51 < carboncarlo> I just tested it this way and it works (y)
03:11 < darosior> carboncarlo: just as a disclaimer keep in mind these words are not enough for a backup lightning.readthedocs.io/BACKUP.html (saying as people are familiar to 'store your mnemonics')
03:13 < carboncarlo> thanks for the reminder, I'm reading the docs and choosing how I want to back up. I think for now I will just go with the backup plugin
03:19 < carboncarlo> I see that to use the backup plugin, I need to change the config file. Is the config file just a text file I need to put into /.lightning myself? I don't seem to have one yet.
03:32 < carboncarlo> I found the instructions to config in the docs.
03:35 -!- jonatack_ [~jon@37.166.124.247] has quit [Ping timeout: 276 seconds]
03:40 -!- jonatack [~jon@37.166.124.247] has joined #c-lightning
04:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
04:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
04:04 <@cdecker> carboncarlo: yes, it's just a plaintext file called `~/.lightning/config`. You can put any command line argument in there (without the leading `--` and it'll get picked up on start. This way you can avoid specifying them all each time you want to run.
04:05 <@cdecker> However you can also just add them all to the command line, if that's easier. The prescription for the backup plugin is just there so you don't accidentally forget it, which would mean the backup gets out of sync
04:08 < carboncarlo> cdecker thanks a lot, that's great. I figured this out after I found the corresponding instructions in the docs. right now, I am figuring out how to actually use the plugin with an USB, finding the URL to my USB.
04:13 <@cdecker> It should be `file:///` + absolute path to the location, so probably something like `file:////media/myUSB/` (could be off by a `/` but it'll complain if it doesn't work with `./backup-cli init`
04:25 < carboncarlo> thanks for your help. please let me know if I ask too much. I got this error: ModuleNotFoundError: No module named 'tqdm'
04:26 <@cdecker> Yep, you need the dependecies. You can install them using `pip install -r requirements.txt` in the plugin directory. Depending on OS and python installation it might require a `sudo` in front of it
04:30 <@cdecker> I need to port some of the plugins to rust so we don't have all these dependencies at some point :-)
04:31 < carboncarlo> awesome, it worked. thanks a lot. I had already installed requirements for an other plugin and I thought that would be it =)
04:32 < carboncarlo> Successfully written initial snapshot
04:32 <@cdecker> Nice ^^
04:44 -!- jonatack [~jon@37.166.124.247] has quit [Ping timeout: 265 seconds]
04:56 -!- jonatack [~jon@37.166.124.247] has joined #c-lightning
05:11 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
05:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
05:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
05:19 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
05:21 < carboncarlo> great, I think I'm all set up and can send some funds to my node.
06:09 -!- jonatack [~jon@37.166.124.247] has quit [Read error: Connection reset by peer]
06:26 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning []
06:26 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning
10:08 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning
10:09 < jasan> Fair enough, the topic is better without the info about meeting. But meeting tonight at 20:00 UTC?
10:11 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
10:25 -!- jonatack [~jon@37.166.77.159] has joined #c-lightning
10:36 <@cdecker> My calendar still says 21:00, and I'm not aware of it having been moved
10:46 < jasan> 20:00 UTC is 21:00 EU. Yes.
10:47 < jasan> cdecker: now is Mon Mar 22 17:46:59 UTC 2021
10:47 < jasan> See you then!
11:04 <@cdecker> Ah righto, damn timezones... ;-)
11:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 268 seconds]
11:17 -!- ksedgwic [~ksedgwic@192-184-130-48.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal]
11:27 < vincenzopalazzo> cdecker: If I'm not wrong we have the same timezone? So I would like to join if I'm at home in time
11:31 < jasan> vincenzopalazzo: Yes, please join! It will be in an hour and half.
11:32 < vincenzopalazzo> jasan: "It will be in an hour and half" it is much better of the strange combination of letter like "UTC". See you later :)
11:35 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
11:49 -!- ksedgwic [~ksedgwic@192-184-130-48.fiber.dynamic.sonic.net] has joined #c-lightning
12:28 < openoms> I just have one question regarding funding with the wrong txid. Now 2016 blocks have passed and the peer couldn't update. The state change is a bit strange complaining about multiple channels:
12:28 < openoms> "state_changes": [
12:28 < openoms>                      "timestamp": "2021-03-22T01:04:32.385Z",
12:28 < openoms>                      "old_state": "CHANNELD_AWAITING_LOCKIN",
12:28 < openoms>                      "new_state": "AWAITING_UNILATERAL",
12:28 < openoms>                      "cause": "protocol",
12:28 < openoms>                      "message": "channeld: received ERROR error channel a33eb36b226641bbf23b2664b99f5eee47bba35f9830ea668222e2e89abf8a40: Multiple channels unsupported"
12:28 < openoms>                "status": [
12:28 < openoms>                   "AWAITING_UNILATERAL:Attempting to reconnect"
12:28 < openoms> Question: can there be any possibility in the future to recover the funds?
12:37 < carboncarlo> is anyone interested in opening some channels mutually? I have 6 active channels already, one is pending.
12:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
12:46 < jasan> carboncarlo: What do you mean by mutually? C-Lightning allows only one channel to one node.
12:48 < vincenzopalazzo> openoms: Maybe this can help? https://github.com/lightningnetwork/lightning-rfc/pull/854 or I misunderstanding the question or I misunderstanding the PR :-D
12:48 < vincenzopalazzo> jasan: Can help me to search the link of meeting? :)
12:52 < jasan> vincenzopalazzo: Rusty will send it in a few moments.
12:52  * jasan will login then as well
12:54 < jasan> carboncarlo: join us for the meeting when Rusty sends the link here
12:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:59 < rusty> Hi all!  Open meeting for next 30 minutes or so; https://meet.jit.si/CLightning-Open-Meeting
13:00 < jasan> vincenzopalazzo: ^^
13:02 < vincenzopalazzo> Cool :)
13:05 < openoms> @vincenzopalazzo yes #854 should help preventing this problem if I understand it correctly, but I don't think it can be applied retrospectively.
13:06 -!- carboncarlo27 [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
13:06 < michaelfolkson> Put this SE question up on lnprototest, saw Lisa's draft PR potentially adding it to the c-lightning CI https://bitcoin.stackexchange.com/questions/103767/what-is-lnprototest-exactly-can-it-be-used-to-test-an-individual-lightning-impl
13:17 < jasan> m-schmoock: where are you?
13:34 < jasan> cdecker: https://github.com/ElementsProject/lightning/issues/2637#issuecomment-801459495 - is this related to what you are talking about now?
13:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
13:49 < jasan> There was no live music this time. Waiting for m-schmoock :) In order to prepare, please have a look at the lyrics Eternal Flame (gnu.org fun section). All the best!
13:58 < carboncarlo> hey, thanks for the meeting. open some channels with me if you want =)  I'm currently known as ODDPENGUIN aka 02dde1de894345d7167db18ff92266fa7302ae018fbea3b12948b3a50cf253f6db
14:00 -!- jonatack [~jon@37.166.77.159] has quit [Remote host closed the connection]
14:00 -!- jonatack [~jon@37.166.77.159] has joined #c-lightning
14:07 < jasan> carboncarlo: noted, will do as soon as I recover funds from https://github.com/ElementsProject/lightning/issues/2637#issuecomment-801459495
14:07 -!- jasan [~j@n.bublina.eu.org] has quit [Quit: Bye!]
14:08 < vincenzopalazzo> carboncarlo: I will join when my java architecture is able to run on testnet :-P
14:21 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
14:21 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Quit: %bye%]
14:21 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 268 seconds]
14:23 -!- jonatack_ [~jon@37.166.59.253] has joined #c-lightning
14:27 -!- jonatack [~jon@37.166.77.159] has quit [Ping timeout: 260 seconds]
14:32 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:48 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning []
14:48 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning
15:31 -!- bdykesfr [~pi@84-83-104-27.fixed.kpn.net] has joined #c-lightning
16:20 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 268 seconds]
16:33 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
17:05 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
17:05 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
17:08 -!- gleb [~gleb@178.150.137.228] has quit [Quit: Ping timeout (120 seconds)]
17:09 -!- gleb [~gleb@178.150.137.228] has joined #c-lightning
17:20 -!- jonatack_ [~jon@37.166.59.253] has quit [Ping timeout: 240 seconds]
17:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds]
17:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:46 < warren> Is there a way to whitelist what node id's are allowed to make incoming channels to you?
17:46 < warren> Or set the minimum channel size?
18:08 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
18:17 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
19:20 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Quit: Bye]
19:22 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
20:14 < rusty> warren: not without writing a simple plugin to do so, no.
20:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]
20:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:04 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
21:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Quit: %bye%]
21:21 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
21:24 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
22:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
22:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 268 seconds]
23:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning []
23:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning
--- Log closed Tue Mar 23 00:00:04 2021