--- Log opened Sat Oct 17 00:00:49 2020 01:30 -!- jonatack [~jon@213.152.162.99] has quit [Ping timeout: 260 seconds] 01:53 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-mxlomfeqruovckob] has joined #c-lightning 01:55 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 256 seconds] 02:01 < HelloShitty> darosior: hi. After almost 2 days off of the computer, my 3 connections dropped and I'm getting the same 'peer_out WIRE_ERROR'. However I can't see any bad order gossip as before 02:02 < HelloShitty> I'm pasting the output of c-lightning to the issue in github 02:09 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning 02:17 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 02:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds] 02:22 -!- belcher_ is now known as belcher 02:38 < darosior> HelloShitty: ok, great report. Thanks! 02:39 < HelloShitty> darosior: and I'm afraid of openning channels because I'm not sure this connectivity problem can cause any problems with open channels 02:39 < HelloShitty> and my node is still not showing up on 1ml.com 02:39 < HelloShitty> Is this normal darosior ? 02:40 < darosior> For 1ml yes 02:40 < HelloShitty> why? 02:40 < darosior> If you open a channel with a C-lightning node it'll be fine 02:41 < darosior> Once you have a channel open you'll start having connections at startup 02:41 < HelloShitty> hum, so I'll only sow up there if I have open channels or if someone opens channels with me, is that it? 02:41 < HelloShitty> ahh ok 02:41 < darosior> (If they aren't dropped ..) 02:41 < HelloShitty> yeah 02:41 < darosior> Yep that's it 02:42 < HelloShitty> The connections I establish should keep alive while there are no internet problems or any other issues with the software or with other node, right? 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:11 < HelloShitty> darosior: when we ask a 'newaddr' to c-lightning node, do we have access to the PK? 03:12 < darosior> Well if PK is the private key corresponding to the pubkey used to generate this address, it is derived from your `hsm_secret` 03:12 < darosior> BIP32 way 03:15 < HelloShitty> So, we don't have access? 03:16 < HelloShitty> I mean, I generated the address with newaddr command but the output is only the bech32 address 03:16 < darosior> Yeah, fortunately ^^ 03:17 < darosior> You do have access! However there is no `dumpprivkey`-lke footgun rpc 03:17 < darosior> However we have the hsmtool ! 03:17 < darosior> https://lightning.readthedocs.io/lightning-hsmtool.8.html 03:18 < darosior> I'm going to extend it soon (TM) to support outputting xpubs and output descriptors from the onchain wallet 03:18 < darosior> Maybe xprivs as well 03:23 < HelloShitty> ohh ok, that's great 03:26 < HelloShitty> I was reading the link you sent me 03:27 < HelloShitty> but the only methods available are to encrypt and decrypt the hsm_secret file 03:27 < HelloShitty> but that file content is nothing readable 03:27 < darosior> Hmm outputting output descriptors with xpriv would be great: just import in the about-to-be-released bitcoind descriptor wallet the descriptor and you are good to go. This would solve this UX issue that people have been asking a lot on IRC to have a dumpprivkey. 03:28 < darosior> Yeah, we are planning to extend it 03:28 < darosior> That file is your wallet seed, you can't read it with text tools as it's in a binary formay 03:28 < darosior> format* 03:29 < HelloShitty> darosior: I'm not following your expertise. I'm sorry. I didn't understand what you mean here -> just import in the about-to-be-released bitcoind descriptor wallet the descriptor and you are good to go 03:29 < darosior> I was just thinking out loud about https://github.com/ElementsProject/lightning/issues/4110, nevermind 03:30 < HelloShitty> So, can you please tell me in very basic words, how we get access to the priv key of the address I just generated? 03:31 < HelloShitty> Or, if preferable, how can I use the address with funds I alreay have imported into my bitcoin node, so that I can use its funds to open channels in c-lightning 03:31 < HelloShitty> you said this is also possible, but more complex 03:31 < darosior> Don't use external funds, that's a footgun 03:32 < darosior> Just send the coins to the address, why not ? 03:33 < HelloShitty> Well, I have already sent the funds to that address because I thought that was the way to go. So, now I have to send the funds again into yet another address 03:33 < darosior> .. 03:33 < HelloShitty> nevermind, I'll do it 03:33 < darosior> Did you send them to the C-lightning wallet ? 03:33 < HelloShitty> no 03:34 < HelloShitty> I had an address free in my offline BTC node 03:34 < HelloShitty> so I imported that address into my online node using the PK 03:34 < HelloShitty> and sent to that address some funds 03:34 < HelloShitty> and I thought now I could use that address I imported to my online BTC node in my c-lightning node to fund channels 03:35 < darosior> Yeah you can't, the bitcoind wallet isn't related to the lightningd 03:35 < HelloShitty> ok 03:35 < darosior> Oh i see you are trying to do the less onchain transactions possible ? :p 03:35 < HelloShitty> ohh no... Not that. I just thought I could use an address I already had 03:35 < HelloShitty> that's all 03:36 < HelloShitty> but nevermind. I'll just send the funds to the address I just created with c-lightning 03:36 < HelloShitty> I just wanted to know how can I have access to the PK of that c-lightning generated address 03:36 < HelloShitty> in case, for some reason I want to remove the funds from there 03:40 < darosior> The withdraw command 03:41 < darosior> https://lightning.readthedocs.io/lightning-withdraw.7.html 03:41 < HelloShitty> And what about the PK of the address? 03:42 < HelloShitty> I was trying to use the decrypt method on hsmtool 03:42 < HelloShitty> but it asks me for a password 03:42 < HelloShitty> I haven't a password. never set one 03:45 * m-schmoock is recently having troubles getting payments bigger than > 0.002 BTC (20$) done via LN. everything timouts and WIRE_TEMPORARY_CHANNEL_FAILURE everywhere. Should I fix that by opeining more channels to LN_BIG and other centralizers? 03:48 < m-schmoock> funny thing, when I use my eclair through my own clnd it can pay easily bigger amounts though my own node that fails if I do it via cli directly 03:48 < m-schmoock> maybe my gossip is damaged? 03:50 < darosior> HelloShitty: please don't use hsm_secret encryption if you are not sure what you are doing 03:50 < darosior> m-schmoock: i think it's from pay 03:50 < darosior> Got some surprises too after the recent refactors 03:50 < darosior> But i think there's been some fixes on master right ? 03:51 < HelloShitty> darosior: I thought you told me to use hsmtool to get access to the PK or seed of the address I just generated 03:52 < HelloShitty> Anyways, can we see the address we generated? Is there a command to show the addresses generated by the c-lightning node? 03:56 < HelloShitty> Is this the appropriate command to check the addresses in our c-lightning node: 'dev-listaddrs' ? 03:58 < m-schmoock> darosior: currently I use 0.9.1 release 03:58 < m-schmoock> thinking about deleting gossip and retry after a while. if that doesnt help but a more recent commit I can try that 04:00 < m-schmoock> lulz ... is a string contains uptick quotation ('..') and we add it tho json_add_string it gets escaped in a non-working way: 'message': \"Forcibly closed by 'close' command timeout\" SyntaxError: unexpected character after line continuation character 04:01 < m-schmoock> and yes fiatjaf this is for you :D 04:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 04:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 04:35 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning 04:40 < fiatjaf> m-schmoock: /) 04:44 < m-schmoock> I have added state change cause/reason and also the varchar message to the notification. Now I need to add it to RPC and DB 04:45 < m-schmoock> seems like a working concept after as you can see in the testcase 04:45 < m-schmoock> https://github.com/ElementsProject/lightning/pull/4126/files#diff-b62266dbe51dfb9358f9f7174a4dd8f165eb650d71cf59c42f3a933078e4a95b 04:45 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 272 seconds] 05:32 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 05:48 < m-schmoock> is there a good way to use pyenv to trick your buildsuite that theres no python available on a system? I want to test the NO_PYTHON=1 stuff locally without relying on endless travis iteration :D 05:48 < m-schmoock> or any other good way to temporarily disable python to run this test? 06:05 <@cdecker> How about running it in docker? 06:05 <@cdecker> That's my usual goto for these kinds of things 06:05 <@cdecker> I had a small dockerfile that tries to emulate travis, because I got bored of waiting as well 06:05 < m-schmoock> I though of a more easy way (like NO_PYTHON=1 make ) 06:06 <@cdecker> Maybe that can work too :-) 06:06 < m-schmoock> I need to execute (and patch) that on each C code changing commit that affects the generated files so the commit chain is bisectablke 06:07 < m-schmoock> NO_PYTHON is only recognized by the travis installer script 06:07 <@cdecker> Anyway, this is the dockerfie I came up with https://gist.github.com/cdecker/ff967ac0ce4693ed2ac1454fc867041a (no guarantee that it really is close, but it helped me look into some things 06:07 < m-schmoock> I really would like to have a git macro that does that for me on each commint in the current branch 06:08 < m-schmoock> cdecker: thx, will try that. Just thought theres a easier way to temporarily disable python 06:09 <@cdecker> Hm, maybe tinkering with the config.vars file could do that as well 06:10 <@cdecker> I think if you set HAVE_PYTHON#_MAKO=0 it should pretty much ignore the generation or better throw an error 06:10 < m-schmoock> hm... worth a shot 06:10 <@cdecker> Trying with a dummy change now 06:11 < m-schmoock> something is calling configure when I do make, which resets this modification 06:13 < m-schmoock> maybe we can modify ./configure to enable overriding that by environment or even watching for NO_PYTHON (so we can copy/pasta the run configs from travis) 06:15 < m-schmoock> somthin along the line: 06:15 < m-schmoock> +if [ "$NO_PYTHON" = 1 ]; then 06:15 < m-schmoock> + HAVE_PYTHON3_MAKO=0 06:15 < m-schmoock> +fi 06:29 -!- ark [~juan@89.32.80.84] has joined #c-lightning 06:33 < m-schmoock> aaahhhh now I know how this is supposed to work :D I think the most effective way would be to modify the SHA256TSTAMP_CHANGED macro to raise an error if NO_PYTHON=1 is set 06:59 < HelloShitty> darosior: when you connected to my node, did you used port 9735 or 9537 ? 06:59 < HelloShitty> cdecker: Hello 06:59 < HelloShitty> have you checked most recent github issue in c-lightning repo? 07:06 <@cdecker> m-schmoock: adding the check to wiregen and sqlgen seems more appropriate, not all sha256stamp_changed occurences have a python-based generator 07:06 <@cdecker> HelloShitty, which issue are you looking at? 07:07 < HelloShitty> https://github.com/ElementsProject/lightning/issues/4130 07:09 < HelloShitty> however, this is not happening all the time 07:10 < HelloShitty> because I had the issue I describe there when trying to connect to that node 07:10 < HelloShitty> but after a few tries I tried to connect to a different node and it succeeded 07:10 < HelloShitty> and after that connection I tried to connect back to the first node and it also succeeded and connections are still up as we speak 07:10 <@cdecker> Can you run with `--log-level=io` so we can see what the error message is we are sending to the peer? 07:11 < HelloShitty> it's in the issue, wait, I'll copy it to here 07:11 < HelloShitty> 1st this: 07:11 < HelloShitty> 2020-10-14T18:35:55.140Z DEBUG 02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2-gossipd: Bad gossip order: WIRE_CHANNEL_UPDATE before announcement 652486x469x0/1 07:11 < HelloShitty> then: 07:12 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 07:12 < HelloShitty> 2020-10-14T18:36:05.599Z DEBUG 02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2-openingd-chan#3: peer_out WIRE_ERROR 07:12 < HelloShitty> 2020-10-14T18:36:05.599Z INFO 02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2-openingd-chan#3: Peer connection lost 07:12 < HelloShitty> 2020-10-14T18:36:05.599Z DEBUG 02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2-openingd-chan#3: Status closed, but not exited. Killing 07:12 < HelloShitty> that was with the master version 07:12 < HelloShitty> then I downgraded to 0.9.1 07:12 <@cdecker> No, that's the debug log, not the io log. io would print the hex of the messages being sent back and forth 07:12 < HelloShitty> ahh ok 07:13 < HelloShitty> Do I have to stop the node? 07:13 < HelloShitty> and restart it again? 07:14 <@cdecker> Yep 07:14 <@cdecker> And then wait for the peer to lose its connection 07:14 < HelloShitty> ok can try but I'm not sure the situation will repeat 07:14 <@cdecker> Best to pipe the output into a file, since it'll cause loads of output 07:14 < HelloShitty> because looks like the connection drops only after a long time 07:14 <@cdecker> I'll look into it from the info in the issue in the meantime 07:14 < HelloShitty> ok 07:15 < HelloShitty> I might not to report the output today 07:15 < HelloShitty> I'll wait for the connections to drop 07:15 < HelloShitty> and then I will try to reconnect to my firend's node to see if the situation persists 07:17 <@cdecker> No problem, let me know once you have a reproduction and we can go from there 07:18 <@cdecker> I'll also try to reproduce it on my side 07:18 < HelloShitty> ok 07:18 < HelloShitty> I think darosior already tried to reproduce and he couldn't 07:18 < HelloShitty> but I'll let you know when I get the issue reproduced 07:24 < ark> hello 07:24 < ark> I have a node in an rpi3 and there are many forwardings in local-fail due to the timeout of adding the htlc 07:25 < ark> the log: https://0bin.net/paste/GUGJ95BH#m05BVyghNkSPB7FLGoWmYJnxWy-u/SQZnyP16789f1X 07:32 <@cdecker> ark: seems your peer is being slow. I've only seen this on a very overloaded machine before, or if the node is running under a heavy debugger like valgrind 07:36 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has quit [Ping timeout: 264 seconds] 07:40 < ark> But this happens to me a lot and with different nodes 07:40 < ark> *peers 07:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds] 07:41 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 07:44 < ark> If I look at my node, I find local forward failures with CoinGate, rompert.com, CoinPayments, ln.bitstamp.net, etc. 07:53 < m-schmoock> cdecker: my proposal on the Makefile NO_PYTHON check: https://github.com/ElementsProject/lightning/pull/4138 07:54 <@cdecker> ark in that case could it be that your raspberry is under heavy load? 08:00 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has joined #c-lightning 08:03 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 08:04 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 08:08 < ark> Right now it only has the bitcoin node, c-lightning, lightning_rest, rtl and tor 08:11 < HelloShitty> cdecker: I restarted my node in the meantime because I was away for a while and left my laptop only on it's battery and I think the wireless connection deactivated so I lost connection to peers 08:11 < HelloShitty> and took the oppotunity to start the node with level-debug=io in the config file and send the output into a file 08:12 < HelloShitty> but that file in like 10 or 15 mins is already over 100Mb 08:12 < HelloShitty> and the peer I try to connect didn't lost connection 08:12 < HelloShitty> so far 08:13 <@cdecker> ark is the bitcoin node syncing? 08:14 <@cdecker> HelloShitty, that's to be expected, it logs all communication 08:14 < HelloShitty> ok, but as of now, the peers are sitll up and connected 08:14 < HelloShitty> need to wait to see if the peers lose connection over time 08:15 < ark> https://pasteboard.co/Jw4UPFG.png 08:16 < HelloShitty> ok, connections are lost cdecker 08:16 < HelloShitty> gonna stop the node 08:16 < HelloShitty> to avoid the file going huge 08:17 < ark> cdecker: yes 08:19 < HelloShitty> What can I do to let you see the file of the log output? Do you want me to create a file only with the small parts were there are messages related to peer connection lost, cdecker ? 08:25 < HelloShitty> I'm now using this command to shrink the output and only log messages related to the peer ID 08:25 < HelloShitty> lightningd | grep -i "02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2" > ~/.lightning/io.log 08:29 < HelloShitty> brb 09:11 <@cdecker> Yep, last 100 lines of log for the node in question should suffice 09:11 <@cdecker> cat logfile.log | grep 02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2 | tail -n 100 > cdecker.log :-) 09:13 <@cdecker> ark, looks like the node is synced and running fine. Dunno what the issue with the errors is in that case 09:22 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 09:24 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds] 09:54 < HelloShitty> cdecker: you around? 09:54 < HelloShitty> connection to peers is lost 09:54 < HelloShitty> I stopped the node 09:54 < HelloShitty> the log file is 1.2M. Not very big 09:55 < HelloShitty> Do you want me to send it to you somehow? 09:56 < ark> cdecker: Could it be due to using tor? because I don't know how well tor supports keeping connections open for a long time 10:01 < HelloShitty> ark: are you talking about my issue? 10:05 < az0re> I use tor and have no problem keeping connections up. Well, they die every now and then, but they always come back 10:07 < HelloShitty> az0re: how do they come back up? Automatically? 10:07 < az0re> Yeah 10:08 < HelloShitty> But did you add the peers to your config file or something like that or do they come back just because there are logs or gossip in the network that allows your node to recover the connection? 10:10 < HelloShitty> I keep getting the error 10:11 < HelloShitty> now even with another node 10:11 < HelloShitty> 2020-10-17T17:06:50.909Z DEBUG 034d2dfd138b4dff2e8f29fef8b70b91ae87b384eb8b8294a54ed2e58f11f2109d-gossipd: reply_channel_range 613715+23853 (of 504500+148689) 8000 scids 10:11 < HelloShitty> 2020-10-17T17:06:51.167Z DEBUG 034d2dfd138b4dff2e8f29fef8b70b91ae87b384eb8b8294a54ed2e58f11f2109d-openingd-chan#1: peer_out WIRE_ERROR 10:11 < HelloShitty> 2020-10-17T17:06:51.167Z INFO 034d2dfd138b4dff2e8f29fef8b70b91ae87b384eb8b8294a54ed2e58f11f2109d-openingd-chan#1: Peer connection lost 10:11 < HelloShitty> 2020-10-17T17:06:51.167Z DEBUG 034d2dfd138b4dff2e8f29fef8b70b91ae87b384eb8b8294a54ed2e58f11f2109d-openingd-chan#1: Status closed, but not exited. Killing 10:24 < ark> HelloShitty: no 10:24 < HelloShitty> ok, sorry 10:29 < az0re> HelloShitty: Errr, no, no special config 10:29 < az0re> It just reconnects 10:29 < HelloShitty> ok 10:29 < az0re> I don't get any `pper_out WIRE_ERROR` either 10:30 < az0re> Just `Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (62208)` 10:30 < az0re> s/pper/peer/ 10:33 < HelloShitty> For some reason, when I connect to peers, often, the node loses connection shortly after 10:33 < HelloShitty> and they don't come back up 10:35 < HelloShitty> az0re: you tried to connect to the same peer as me? 10:36 < HelloShitty> I also get this message: 10:36 < HelloShitty> 02ab6d60e2e46e1af91c671234c914f99a3826c1c7e3a358cc46a0bcf37663adb2-openingd-chan#3: peer_out WIRE_GOSSIP_TIMESTAMP_FILTER 10:37 < HelloShitty> and shortly after, the other one comes 10:48 < az0re> No, not the same peer 10:51 < HelloShitty> ah ok 11:03 <@niftynei> darosior: "Maybe the mkcommit tool if you know the commit number ?" needs to be integration test accessible 11:23 -!- ark [~juan@89.32.80.84] has quit [Quit: Konversation terminated!] 12:31 < HelloShitty> darosior: what will happen if I open a channel with someone, fund it and sooner or later, the connection to that noded/peer drops? Do I lose funds in that channel? 12:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 12:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 14:36 < HelloShitty> darosior: az0re: any of you aorund? 14:37 < HelloShitty> If I open a channel using fundchannel command and use partial amount to fund the channel, the remianing of the source address will go to miners? 14:38 < HelloShitty> I mean, I had 200k sats in an address, opened a channel with 20k sats but never mentioned a change address, so the remaining 180k sats are gone for a fee? 15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 16:06 < az0re> HelloShitty: No it should just make a new address and give you change 16:06 < HelloShitty> yeah, it did 16:06 < az0re> lightning-cli listfunds | less 16:06 < az0re> OK cool 16:07 < HelloShitty> I just thought the address I saw in blockchair explorer was some miners address where the remianing btc would have been sent 16:07 < HelloShitty> but after all, that address is in my lightning node 16:07 < HelloShitty> all good 16:10 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 260 seconds] 16:40 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:01 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has joined #c-lightning 17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 17:23 < HelloShitty> az0re: you around? 17:24 < HelloShitty> If I use the command "fundchannel" to open and fund a channel but don't use the entire utxo value, does the remaining value goes to miners or where do I specify the change address? 17:24 < HelloShitty> I'm building the command like this: 17:26 < HelloShitty> lightning-cli fundchannel "peer_id" 200000 normal true 1 "[{\"txid\":\"asjnaksndaksnsjandkasnajdn\",\"vout\":0}]" 17:26 < HelloShitty> but the source address has more than the 200k sats 17:26 < HelloShitty> and I'm not specifying any change address, so where goes the remaining value of this utxo that is not being used to fund the channel? 17:59 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has quit [Read error: Connection reset by peer] 18:02 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has joined #c-lightning 18:43 < az0re> HelloShitty: Nah it will make a new address and send the change there. The fee is set by the "normal" value there; it could also be something like "1000perkb". 18:45 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 18:46 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 18:47 < az0re> Also I believe the utxo set there should be rendered like: `'["asjnaksndaksnsjandkasnajdn:0"]'` 18:48 < az0re> i.e. an array of strings, not an array of objects with fields "txid" and "vout" 19:10 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 260 seconds] 19:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 19:35 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 21:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 22:15 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 22:16 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 23:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 23:20 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 264 seconds] --- Log closed Sun Oct 18 00:00:50 2020