--- Log opened Sat Mar 27 00:00:08 2021
00:33 -!- klaiko [d5bdb9c6@host-213-189-185-198.dynamic.voo.be] has quit [Quit: Connection closed]
01:07 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
01:34 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has joined #c-lightning
01:41 < vincenzopalazzo> Hello Guys, yesterday I walk around the web to search if it is possible dump the private key, or at list export the private key from the clightning node and use the same private key in different wallets
01:42 < vincenzopalazzo> I found a old post (2018-2019), that now I'm not able to find the link anymore :-), but I want ask if there is there is some external tools update to do this operation with c-lightning?
01:43 < vincenzopalazzo> or at list, a way to get the private key and use the it in another wallet
01:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
01:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
02:16 -!- bdykesfr [~pi@84-83-104-27.fixed.kpn.net] has joined #c-lightning
04:12 <@cdecker> vincenzopalazzo: depends on where you are in the process, if you want to generate a new hsm_secret from a BIP39 the you can use the hsmtool to do that (https://lightning.readthedocs.io/lightning-hsmtool.8.html)
04:13 <@cdecker> If you want to move an existing secret, then just copy hsm_secret (you should also back that file up just in case of HW failure)
04:14 <@cdecker> But please don't run two nodes concurrently with the same node_id, that'd cause a variety of issues (channels not being able to re-establish because the peer is contacting the wrong node, announcements being contradictory, ...)
04:15 <@cdecker> The hsmtool can also be used to dump the onchain descriptors to track funds in other wallets, to import the private keys we could look into allowing generation of those as well
04:18 < vincenzopalazzo> cdecker: Thanks for the link, I will play with these tools. But, yest I haven't intention to run two node with the same private key
04:20 < vincenzopalazzo> I haven't not read yet careful the documentation but, from you last message if I'm not wrong, it is possible make the dump of private key, but it is not available the feature to import a private key
04:21 < vincenzopalazzo> For example, if I have my wallet on-chain, and to avoid moving the fund with a transaction in my lightning node, I can't import the private key of my on-chain wallet to my lightning node?
04:21 < vincenzopalazzo> I'm understand correctly?
04:25 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
04:44 <@cdecker> That'd be possible, if we're using the same derivation paths, which is discouraged by the HD wallet BIP IIRC. If the derivation paths differ then we'd be generating different addresses from the same seed, and therefore lightningd would not be seeing the funds the other wallet sees, despite having the same seed. The opposite is likely possble
04:44 <@cdecker> (export from lightningd, and import into wallet) because general purpose wallets often allow you to specify the derivation path.
05:13 < vincenzopalazzo> Thanks for the information :)
05:41 -!- belcher_ is now known as belcher
05:47 -!- rny [~rny@gateway/tor-sasl/renlord] has quit [Remote host closed the connection]
05:48 -!- rny [~rny@gateway/tor-sasl/renlord] has joined #c-lightning
07:48 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
07:57 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
08:10 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
08:49 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
09:54 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
09:54 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
10:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
10:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
11:35 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
11:38 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
11:39 < carboncarlo> Good evening =)  people have had troubles to connect to my TOR node, even if they are in TOR as well. When I connect to them first, it works quite fine. Is there something I should enable?
11:42 < darosior> carboncarlo: smells like a port forwarding issue
11:43 < carboncarlo> darosior when I try to see if my port 9735 is open, it usually is.
11:44 < carboncarlo> I just checked with https://www.yougetsignal.com/tools/open-ports/ but yes, I see, that is only for clearnet IP
12:48 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
12:49 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
13:58 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
14:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
14:37 < warren> If you run non-mainnet LN nodes there is no canonical different TCP port number? it's still 9735?
14:39 < warren> like signet
15:09 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Read error: Connection reset by peer]
15:10 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
15:47 < grubles> mine defaulted to 9735 fwiw
15:47 < grubles> (running on signet)
15:51 < vincenzopalazzo> warren: No there is any difference, the config file work different from the bitcoind, but you can define different config file for different network as the doc suggest https://lightning.readthedocs.io/lightningd-config.5.html?highlight=config#lightningd-config-lightning-daemon-configuration-file
15:52 < warren> I'm testing stuff on signet. Anyone want to peer?
16:04 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
16:08 < carboncarlo> mhhh, so I reread a lot of the guide for using c-lightning with tor. I'm case #4 where I don't have a public IP but want others to connect over my onion address. It says for the config file --bind-addr=yourInternalIPAddress:port --announce-addr=your.onionAddress:port or --addr=your.onionAddress:port if you are NOT on an internal network.
16:08 < carboncarlo> I'm afraid I have to ask what is meant by internal network.
16:24 < vincenzopalazzo> warren: I have a node on testnet
16:27 < vincenzopalazzo> carboncarlo: I'm supposing that the internal network is your "home network", the command "--addr" try to make the binding operation for you, without specify the --bind-addr and --announce-addr
16:29 < vincenzopalazzo> In my understanding, the doc tell you if you don't know your internal IP address, there is a method to be lucky and give to lightnind the possibility to understand what it is
16:30 < vincenzopalazzo> but I'm a disaster with the network stuff and maybe I'm wrong
16:31 < carboncarlo> vincenzopalazzo ok thanks for suggestions. I think it's not really clear what I should do here, but I think I will do something that kinda feels right: bind-addr=127.0.0.1:9735
16:31 < carboncarlo> announce-addr=h3vvv5nm44ls47lbbxrblnfn3jgzfbhid4hc2ry4klqs7yppvn4bq2qd.onion:9735
16:32 < vincenzopalazzo> 127.0.0.1 work in any case :-P (maybe)
16:33 < carboncarlo> If I have a static IP, should I put it there instead?
16:33 < vincenzopalazzo> you are on testnet?
16:33 < carboncarlo> nooooo
16:33 < carboncarlo> I'm totally live and figuring this out now
16:34 < vincenzopalazzo> if you have a static public ip and you want to be visible to the network, you static ip need to be put on the --announce-addr
16:34 < carboncarlo> no, I mean internally, I have made the IP of the machine lightningd runs on static
16:35 < carboncarlo> I don't want my external IP announced
16:35 < warren> carboncarlo: bind=127.0.0.1:9735 and announce-addr=torv3onionaddress.onion:9735
16:35 < vincenzopalazzo> but sometimes you ahve also a static internal ip, for example on google clouse of somethings like that, and in this case your internal static ip need to be put on the --bind-addr
16:36 < warren> The docs are not easy to understand in that section.
16:37 < carboncarlo> warren ok thanks. I'll try like this. all other things concerning tor I think are correct now.
16:37 < warren> carboncarlo: always-use-proxy=true (for outgoing connections) and proxy=127.0.0.1:9050 
16:37 < vincenzopalazzo> if you using always-use-proxy=true you are able to connect only to other node over tor
16:37 < warren> this is how I used to use it. I found tor added random network delay that would occasinally cause problems so I instead VPN through a IPv4 visible host 
16:38 < warren> vincenzopalazzo: nope, it also connects to IPv4 over tor exit nodes (which is maybe not a good thing when it comes to reliability)
16:39 < carboncarlo> warren ok thanks a lot
16:41 < carboncarlo> I will sleep now, but maybe tomorrow someone running tor could try if they can connect to me!
16:42 < carboncarlo> cu
16:42 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Quit: Connection closed]
17:04 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
17:46 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
18:31 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
18:31 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
20:19 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
20:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
20:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:46 -!- mode/#c-lightning [+o rusty] by ChanServ
20:47 -!- rusty changed the topic of #c-lightning to: Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning  Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.10.0rc2 Logs at http://gnusha.org/c-lightning/ Dev Roadmap: https://github.com/ElementsProject/lightning/wiki
23:29 < warren> I'm cleaning up Blockstream Store's LN channels and opening new channels over the next week. Anyone able to open big channels toward us? Please contact me (not via unencrypted IRC) if you're interested in peering. warren -at- blockstream -dot- com.
--- Log closed Sun Mar 28 00:00:09 2021