--- Log opened Thu Oct 01 00:00:34 2020 00:18 -!- skme9_ [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has joined #c-lightning 00:20 -!- skme9 [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has quit [Ping timeout: 240 seconds] 00:46 -!- jonatack [~jon@37.164.132.126] has joined #c-lightning 00:48 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 01:07 -!- felixweis [sid154231@gateway/web/irccloud.com/x-krefugjevbfmhthz] has joined #c-lightning 01:07 -!- fjahr [sid374480@gateway/web/irccloud.com/x-rbbwbtbigjvdlmkh] has joined #c-lightning 01:52 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis 02:10 -!- Netsplit over, joins: felixweis, fjahr 02:38 < m-schmoock> cdecker: https://github.com/ElementsProject/lightning/issues/4027#issuecomment-702016444 02:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 02:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 03:04 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds] 03:05 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:15 -!- jonatack [~jon@37.164.132.126] has quit [Ping timeout: 260 seconds] 03:17 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 04:17 < darosior> az0re: LSAN_OPTIONS=suppressions=contrib/sanitizer_suppressions/lsan (your error is related to LeakSanitizer) 04:17 < darosior> Arf this asan file you used should not be comitted .. 05:21 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 06:00 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 06:04 -!- jasan [~jasan@tunnel509499-pt.tunnel.tserv27.prg1.ipv6.he.net] has quit [Quit: Bye!] 07:01 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 07:01 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 07:36 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 07:42 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 07:54 -!- yang [~yang@freenode/sponsor/fsf.member.yang] has joined #c-lightning 08:02 < az0re> Hmmm, nope, that doesn't seem to work; I still get spammed with "DEADLY SIGNAL" messages 08:31 -!- kexkey [~kexkey@89.36.78.198] has joined #c-lightning 08:42 < liberliver> Hey. Can't you guys give a suggestion from where comes this error "Wrong network! Our Bitcoin backend is running on 'main', but we expect 'test'". I'm using custom plugin which replaces bcli. 08:49 -!- skme9 [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has joined #c-lightning 08:50 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 08:53 -!- skme9_ [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has quit [Ping timeout: 260 seconds] 08:55 < darosior> liberliver: which plugin are you using ? 08:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 08:56 < darosior> Doesn't it expose a --testnet-like argument ? 08:58 < liberliver> darosior: I'm adding testnet option for fiatjaf's trustedcoin 09:04 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 09:06 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 09:08 < liberliver> darosior: what does mean --testnet-like argument? 09:15 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 09:23 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 09:40 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 09:49 -!- skme9_ [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has joined #c-lightning 09:53 -!- skme9 [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has quit [Ping timeout: 260 seconds] 10:38 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 10:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 10:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 11:01 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis 11:12 -!- skme9_ [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has quit [Remote host closed the connection] 11:12 -!- skme9_ [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has joined #c-lightning 11:47 -!- Netsplit over, joins: felixweis, fjahr 11:49 -!- skme9_ [~skme9@2402:3a80:6b5:7b87:1cda:e858:531:5bf1] has quit [Ping timeout: 260 seconds] 11:50 < liberliver> If you meant whether I launch lightningd with --testnet or not, I say yes, I do launch with --testnet or --network=testnet or network in config.. 11:57 < liberliver> Am I right esplora uses uses proxy for Tor? https://github.com/lvaccaro/esplora_clnd_plugin/tree/v0.1 11:57 < liberliver> Or might use Tor only with proxy 11:58 < az0re> liberliver: So you're running bitcoind on mainnet and lightningd on testnet. Do you see the problem? 11:59 < az0re> If the problem is with the plugin mis-reporting, well, unfortunately can't help there... 12:00 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 12:00 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #c-lightning 12:01 < az0re> Although, perusing https://github.com/lvaccaro/esplora_clnd_plugin/blob/v0.1/esplora.c briefly, it sure looks like there's no way to misreport 12:01 < az0re> (Or maybe this is a different plugin you're talking about) 12:05 < az0re> And it looks like you need to have proxy_enabled == true here in order to use Tor/proxy: https://github.com/lvaccaro/esplora_clnd_plugin/blob/v0.1/esplora.c#L154 12:07 < az0re> And that seems to be set only when "always-use-proxy" is enabled: https://github.com/lvaccaro/esplora_clnd_plugin/blob/v0.1/esplora.c#L687 12:37 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 240 seconds] 12:39 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 13:38 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 14:16 < darosior> Sorry, was not available. liberliver: as pointed out by the error message "Wrong network! Our Bitcoin backend is running on 'main', but we expect 'test"", well, you are running your Bitcoin backend on the wrong network. You can either run your backend with a --testnet option, or run lightningd on mainnet. 14:32 < az0re> `lightning-cli help multifundchannel` includes language like the following: "amount is the amount in satoshis taken from the internal wallet to fund the channel. The string all can be 14:32 < az0re> used to specify all available funds (or 16,777,215 satoshi if more is available and large channels were not 14:32 < az0re> negotiated with the peer)." 14:32 < az0re> How exactly does one negotiate large channels with a peer? 14:35 < az0re> And although I think the spec for `destinations` is fine, it would be nice to include a template 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 15:15 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 15:32 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 16:27 < az0re> Also, why is keysend pegging my CPU? (I'm not sending anything, definitely do not expect keysend to be running or doing anything) 16:55 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis 17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 17:05 -!- Netsplit over, joins: felixweis, fjahr 17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 17:19 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 17:40 -!- skme9 [~skme9@2402:3a80:6b1:49a5:8d17:c5ec:1a13:9518] has joined #c-lightning 18:51 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 18:52 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 19:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 19:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 19:16 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 19:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 19:24 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 19:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 20:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:21 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis 20:21 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Write error: Connection reset by peer] 20:21 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #c-lightning 20:49 -!- Netsplit over, joins: felixweis, fjahr 20:50 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 21:28 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 21:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 21:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 22:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds] 22:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 23:39 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning 23:42 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Ping timeout: 256 seconds] 23:58 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has joined #c-lightning --- Log closed Fri Oct 02 00:00:35 2020