--- Log opened Sat Mar 20 00:00:01 2021 00:47 < vincenzopalazzo> grubles: Cool 02:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 04:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning [] 04:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning 05:50 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection] 05:51 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 06:22 -!- belcher_ is now known as belcher 06:56 < grubles> warren: looks like there's support in c-lightning at least https://github.com/ElementsProject/lightning/pull/4078 06:57 < grubles> might have to try signet instead because bitcoind keeps crashing when syncing testnet 07:05 < grubles> z5cvpykfsefa4dojroscq73c6dcqks7uzimi5rvtlrudynuvsuvffbid.onion:9735 if anyone wants to connect to my signet node 07:52 < warren> In general I think all wallets should support signet. It's a great noob teaching tool. Noobs need to build up confidence. Seeing transactions in a safe environment helps. 08:09 < warren> With multifundchannel is it currently possible to specify the change address so perhaps that could go elsewhere? 08:10 -!- Zanth [5ceae07f@cpc101546-mort7-2-0-cust126.19-2.cable.virginm.net] has joined #c-lightning 08:19 < warren> Ugh ... Error broadcasting transaction: error code: -26\\\\nerror message:\\\\nmempool min fee not met, 1613 < 1686. Unsent tx discarded 08:19 < warren> withdraw command with "slow" rejected its own transaction, and now all my UTXO's are reserved. 08:21 < warren> Fee smoothing along with "slow" during a period when fee rates are falling is when I triggered this bug. 12:12 -!- jonatack_ [~jon@37.165.162.147] has joined #c-lightning 12:17 -!- openoms [~quassel@cpc115064-stok20-2-0-cust91.1-4.cable.virginm.net] has joined #c-lightning 12:21 -!- jonatack_ [~jon@37.165.162.147] has quit [Read error: Connection reset by peer] 12:22 -!- jonatack_ [~jon@37.165.162.147] has joined #c-lightning 12:29 -!- jonatack_ [~jon@37.165.162.147] has quit [Quit: jonatack_] 12:29 -!- jonatack [~jon@37.165.162.147] has joined #c-lightning 12:40 -!- jonatack [~jon@37.165.162.147] has quit [Ping timeout: 264 seconds] 12:42 -!- jonatack [~jon@37.165.162.147] has joined #c-lightning 12:44 -!- jonatack [~jon@37.165.162.147] has quit [Read error: Connection reset by peer] 12:44 -!- jonatack_ [~jon@37.165.162.147] has joined #c-lightning 12:48 -!- jonatack_ [~jon@37.165.162.147] has quit [Read error: Connection reset by peer] 12:49 -!- jonatack_ [~jon@37.165.162.147] has joined #c-lightning 12:55 -!- jonatack_ [~jon@37.165.162.147] has quit [Read error: Connection reset by peer] 12:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 12:55 -!- jonatack_ [~jon@37.165.162.147] has joined #c-lightning 12:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning [] 12:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning 13:19 -!- HelloShi1ty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 13:28 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 13:31 -!- jonatack_ [~jon@37.165.162.147] has quit [Quit: jonatack_] 13:38 -!- jonatack [~jon@37.165.162.147] has joined #c-lightning 14:02 < HelloShitty> Hello 14:02 -!- gwillen [~gwillen@unaffiliated/gwillen] has quit [Remote host closed the connection] 14:03 < HelloShitty> Anyone around here? I rebooted my laptop and now, when I try to start lightningd, I get this error: 14:03 < HelloShitty> $ lightningd 14:03 < HelloShitty> lightning_connectd: Connecting stream socket to Tor service: Connection refused 14:03 < HelloShitty> lightningd: connectd failed (exit status 1), exiting. 14:04 < rny> systemctl status tor? 14:07 < HelloShitty> $ systemctl status tor 14:07 < HelloShitty> ● tor.service - Anonymizing overlay network for TCP (multi-instance-master) 14:07 < HelloShitty> Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled) 14:07 < HelloShitty> Active: active (exited) since Sat 2021-03-20 20:53:12 WET; 13min ago 14:07 < HelloShitty> Process: 2761 ExecStart=/bin/true (code=exited, status=0/SUCCESS) 14:07 < HelloShitty> Main PID: 2761 (code=exited, status=0/SUCCESS) 14:07 < HelloShitty> debian-+ 2767 0.1 0.1 45928 29884 ? Ss 20:53 0:01 /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 14:09 < rny> check if the control port or socks port is listening (with netstat or ss), depending on your setup 14:10 < HelloShitty> rny: `netstat -ntl | grep 9051` ? 14:11 < rny> yea 14:12 < HelloShitty> I'm always conffused with 9050 and 9051 14:12 < HelloShitty> I can't see anything with 9051, but I can see with 9050 14:12 < rny> 9051 is the tor control port 14:14 < HelloShitty> I can't see anything listening in 9051 14:15 < rny> your torrc configuration needs to enable ControlPort 14:15 < HelloShitty> I think that port is set in another tor-defaults-something file 14:16 < HelloShitty> I can't remember where is there file located 14:18 < rny> but your systemctl status shows -f /etc/tor/torrc :/ 14:19 < HelloShitty> yes, but there is another config file that I think is also read 14:20 < HelloShitty> but I'll put the ControlPort 9051 in /etc/tor/torrc 14:20 < HelloShitty> to try it 14:21 < HelloShitty> Just did it but lightnind is still refusing to connect to tor 14:22 < rny> did you check with netstat again? 14:24 < HelloShitty> going to check now, but I think Tor is not running now 14:28 < HelloShitty> yep, tor is not running 14:28 < HelloShitty> it fails loading the config file 14:59 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #c-lightning 15:38 < HelloShitty> ok, I ended up uninstalling tor and reinstalling it 15:38 < HelloShitty> but it still not running lightnind 15:38 < HelloShitty> The error message is the same 15:41 < HelloShitty> ok, I think it started now 15:43 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Ping timeout: 246 seconds] 15:51 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #c-lightning 16:10 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 16:11 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Read error: Connection reset by peer] 16:11 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 16:11 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #c-lightning 16:20 -!- thorie [~thorie@76-226-84-35.lightspeed.sntcca.sbcglobal.net] has joined #c-lightning 16:47 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Remote host closed the connection] 16:49 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #c-lightning 16:56 -!- jonatack [~jon@37.165.162.147] has quit [Ping timeout: 240 seconds] 17:00 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:51 < warren> v0.10.0rc1 ... is it #reckless to upgrade my mainnet v0.9.3 node? 18:08 -!- openoms [~quassel@cpc115064-stok20-2-0-cust91.1-4.cable.virginm.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.] 18:09 -!- openoms [~quassel@196.196.192.20] has joined #c-lightning 18:09 -!- openoms [~quassel@196.196.192.20] has quit [Remote host closed the connection] 18:12 -!- openoms [~quassel@196.196.192.12] has joined #c-lightning 18:13 -!- openoms [~quassel@196.196.192.12] has quit [Remote host closed the connection] 18:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds] 18:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 18:40 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Remote host closed the connection] 18:46 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 19:00 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...] 19:07 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #c-lightning 19:11 -!- openoms [~quassel@cpc115064-stok20-2-0-cust91.1-4.cable.virginm.net] has joined #c-lightning 19:11 -!- openoms [~quassel@cpc115064-stok20-2-0-cust91.1-4.cable.virginm.net] has quit [Client Quit] 19:12 -!- openoms [~quassel@cpc115064-stok20-2-0-cust91.1-4.cable.virginm.net] has joined #c-lightning 19:14 -!- openoms [~quassel@cpc115064-stok20-2-0-cust91.1-4.cable.virginm.net] has quit [Client Quit] 19:17 -!- spinza [~spin@102.132.245.16] has joined #c-lightning 19:22 -!- openoms [~quassel@109.202.99.36] has joined #c-lightning 19:23 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Remote host closed the connection] 19:23 -!- openoms [~quassel@109.202.99.36] has quit [Remote host closed the connection] 19:23 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #c-lightning 19:24 -!- openoms [~quassel@109.202.99.41] has joined #c-lightning 19:25 -!- openoms [~quassel@109.202.99.41] has quit [Remote host closed the connection] 19:25 < warren> https://0bin.net/paste/Hj1xh3lh#eUKj9O7EMG0CTNMmMfrF6hwFXMczGrcRlXNDGinLVNx 19:26 < warren> mutual close spent ~4x as much as the "mutual_close_satoshis" estimate. Is this expected behavior? 19:26 -!- openoms [~quassel@213.152.176.252] has joined #c-lightning 19:27 -!- openoms [~quassel@213.152.176.252] has quit [Remote host closed the connection] 19:28 -!- openoms [~quassel@109.202.99.46] has joined #c-lightning 19:29 -!- openoms [~quassel@109.202.99.46] has quit [Remote host closed the connection] 19:32 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Quit: Leaving] 19:33 -!- Zanth [5ceae07f@cpc101546-mort7-2-0-cust126.19-2.cable.virginm.net] has quit [Quit: Connection closed] 19:58 -!- openoms [~quassel@109.202.99.41] has joined #c-lightning 19:59 -!- openoms [~quassel@109.202.99.41] has quit [Remote host closed the connection] 20:02 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #c-lightning 20:27 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Ping timeout: 268 seconds] 20:32 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #c-lightning 20:34 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Remote host closed the connection] 20:55 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #c-lightning 21:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 21:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning [] 21:13 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 21:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning 21:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 21:23 -!- rubikputer [~rubikpute@unaffiliated/rubikputer] has joined #c-lightning 22:28 < warren> Hmm mutual close of a channel between two c-lightning nodes had a nicely low fee rate. 22:46 -!- opsec_x122 is now known as opsec_x12 --- Log closed Sun Mar 21 00:00:02 2021