--- Day changed Wed Jun 27 2018 00:14 -!- mn3monic [~guido@unaffiliated/mn3monic] has joined #c-lightning 00:19 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 256 seconds] 00:20 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-taelvzozbnphflex] has joined #c-lightning 00:25 -githubby:#c-lightning- [lightning] arowser opened pull request #1633: add alias and color to getinfo (master...get_info) https://git.io/f45OS 01:02 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:48 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 01:56 -!- daouzo235 [~daouzo23@178.165.129.248.wireless.dyn.drei.com] has joined #c-lightning 02:00 -!- daouzo23 [~daouzo23@178.165.128.152.wireless.dyn.drei.com] has quit [Ping timeout: 268 seconds] 02:15 -!- tiagotrs [~user@p5DDB5EB2.dip0.t-ipconnect.de] has joined #c-lightning 02:15 -!- tiagotrs [~user@p5DDB5EB2.dip0.t-ipconnect.de] has quit [Changing host] 02:15 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 02:30 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-taelvzozbnphflex] has quit [Quit: Connection closed for inactivity] 02:45 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 02:55 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-txnbihlwcjebttfb] has joined #c-lightning 03:26 < bitonic-cjp> "Bad gossip order from error": WHY????? 03:55 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 250 seconds] 03:56 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 04:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 265 seconds] 04:40 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/f45X9 04:40 -githubby:#c-lightning- lightning/master aeafe4d nicolas.dorier: [Docker] Fix: Bind socat to the right port 05:03 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:04 -!- daouzo235 [~daouzo23@178.165.129.248.wireless.dyn.drei.com] has quit [Remote host closed the connection] 06:05 -!- daouzo235 [~daouzo23@178.165.129.248.wireless.dyn.drei.com] has joined #c-lightning 06:41 -!- face [~face@80.72.82.160.coresnet.bg] has joined #c-lightning 06:45 -!- broompole [b99cae1b@gateway/web/freenode/ip.185.156.174.27] has joined #c-lightning 06:52 < broompole> can anyone help getting c-lightning running? 06:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qlccotiggftxpaqt] has left #c-lightning [] 06:54 < broompole> question: should there be nodes connected if I do "lightning-cli listnodes"? 06:54 < broompole> (currently haven't funded the wallet) 06:58 -!- dougsland [douglas@nat/redhat/x-tufomrnwqgkdxhup] has joined #c-lightning 07:01 < windsok> broompole: not sure if DNS seeds for finding initial node to connect to are working yet 07:01 < windsok> you might need to manually connect to a node 07:01 < windsok> or node(s) 07:01 < windsok> in the past I've just picked a few from here https://rompert.com/recksplorer/ 07:07 < broompole> windsok: thanks, that's what it needed 07:08 < windsok> that's mainnet btw 07:08 < broompole> anything else I need to initialise things manually? 07:09 < windsok> create a new on-chain address, fund it, then open some channels :) 07:09 < windsok> if you want to be connectable you need to set the --addr setting 07:10 < windsok> I saw some auto-config settings for that.. but not sure how well it works yet, i've had to set my external ip address in --addr 07:10 < windsok> and make sure port 9735 is open 07:14 < broompole> windsok: thanks again 07:15 < broompole> windsok: lightningd is behind my Tor proxy 07:15 < windsok> ahh i see, i've not setup with Tor before 07:15 < windsok> others here might have 07:17 < broompole> opening 9735 might prove fun, forwarding 8333 has never resulted in e.g. connecting to incoming peers on bitcoind! 07:17 < broompole> windsok: big thanks for the rompert.com tip :) 07:17 < windsok> Well i think you can advertise your node to the network with a .onion address... somehow 07:18 < broompole> and 9735 will be forwarded without any config? 07:20 < molz> it's in your firewall setup 07:21 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:21 < windsok> they are asking about doing it with tor 07:21 < windsok> can't find any info in the readme 07:22 < windsok> though I see this interesting setting on lightningd 07:22 < windsok> --tor-service-password Set a Tor hidden service password 07:22 < windsok> and 07:22 < windsok> --announce-addr Set an IP address (v4 or v6) or .onion v2/v3 to announce, but not listen on 07:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 07:22 < windsok> I assume .onion also works for 07:22 < windsok> --addr Set an IP address (v4 or v6) to listen on and announce to the network for incoming connections 07:23 < windsok> but maybe noe.. 07:23 < molz> but to forward port 9735, it has to be in his firewall setup? 07:23 < molz> i use ufw to do this 07:24 < broompole> so incoming connections is a must (and so 9735 must be forwarded correctly) 07:25 < broompole> hence the necessity of the --addr parameter? 07:25 < molz> if you don't open port 9735 you still can connect and open channels to other nodes that have their ports opened 07:25 < windsok> not a must 07:26 < windsok> you only need it if you want others to be able to discover your node and open channels to you 07:27 < windsok> you can run a totally private node, with private not-announced channels if you want 07:27 < windsok> sounds like that's probably what you want :) 07:28 < broompole> right, that all makes sense 07:28 -!- Lightblock [uid302821@gateway/web/irccloud.com/x-pekosrnpmehlzzeh] has joined #c-lightning 07:29 < Lightblock> @azi yes, publickey 07:29 -!- douglas_ [douglas@nat/redhat/x-jrfegalcefwhdclx] has joined #c-lightning 07:32 -!- dougsland [douglas@nat/redhat/x-tufomrnwqgkdxhup] has quit [Ping timeout: 264 seconds] 07:42 -!- broompole [b99cae1b@gateway/web/freenode/ip.185.156.174.27] has quit [Ping timeout: 260 seconds] 07:51 < Lightblock> can anyone suggest a quick way to get the bitcoin on-chain TXid when you have the short channel id (blockheight txindex and outputindex) 07:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qlccotiggftxpaqt] has joined #c-lightning 07:56 -!- douglas__ [douglas@nat/redhat/x-fwmahoactgduqroe] has joined #c-lightning 07:57 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 07:57 < molz> Lightblock, why do you want that info? 07:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qlccotiggftxpaqt] has left #c-lightning [] 07:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qlccotiggftxpaqt] has joined #c-lightning 07:58 < Lightblock> because I want to see the normal representation of the the fudning txID 07:58 < Lightblock> for the channel funding transaction ID 07:59 -!- douglas_ [douglas@nat/redhat/x-jrfegalcefwhdclx] has quit [Ping timeout: 264 seconds] 08:02 < windsok> is it your own channel? 08:05 < Lightblock> nope, I mean some other node 08:05 < Lightblock> for my own I can lookup via listpeers command 08:05 < Lightblock> it gives the funding TXid 08:05 < molz> so, why do you want this info? you've been at this for two weeks now 08:06 < Lightblock> no, before I was asking about the format of channel ID 08:06 < Lightblock> now I am asking about the channel funding TX id 08:06 < Lightblock> I am just monitoring some channels 08:06 < Lightblock> and I want to know the funding TX id just I have it for own channel 08:06 < molz> which channels are you monitoring? 08:07 < Lightblock> for example 529463:165:1 08:07 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qlccotiggftxpaqt] has left #c-lightning [] 08:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qlccotiggftxpaqt] has joined #c-lightning 08:10 < Lightblock> so any ideas? ) 08:17 < Lightblock> I know that c-lightning does not give this info out of the box 08:18 < Lightblock> this question is how to do it via normal bitcoin-cli 08:18 < Lightblock> I've googled that, at no avail 08:21 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 08:27 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 08:31 -!- douglas__ [douglas@nat/redhat/x-fwmahoactgduqroe] has quit [Ping timeout: 256 seconds] 08:44 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer] 08:48 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 08:58 -!- fusion45 [~fusion44@31.6.42.114] has joined #c-lightning 09:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:16 < blockstream_bot> [Chang Li, Blockstream] using bitcoin-cli to see channel tx? 09:22 < mn3monic> @Lightblock, sed\awk\jq combo, or a simply python script. 09:23 < mn3monic> given a short channel id, is quite easy. blockheight:txheight:voutheight 09:35 -!- mn3monic [~guido@unaffiliated/mn3monic] has quit [Remote host closed the connection] 09:36 -!- daouzo235 [~daouzo23@178.165.129.248.wireless.dyn.drei.com] has quit [Read error: Connection reset by peer] 09:41 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 09:56 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 10:08 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 10:12 -!- daouzo23 [~daouzo23@178.165.129.248.wireless.dyn.drei.com] has joined #c-lightning 10:21 -!- blyat [~blyat@cpe-172-72-228-93.carolina.res.rr.com] has joined #c-lightning 10:26 -githubby:#c-lightning- [lightning] wythe opened pull request #1636: Typesafe callback system for parsing json (master...typesafe-params) https://git.io/f4dZS 10:50 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:51 -!- Lightblock [uid302821@gateway/web/irccloud.com/x-pekosrnpmehlzzeh] has quit [Quit: Connection closed for inactivity] 10:51 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 276 seconds] 10:55 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 10:56 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 10:58 -!- belcher [~belcher@unaffiliated/belcher] has quit [Max SendQ exceeded] 10:59 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 11:10 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer] 11:16 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 11:30 -!- tiagotrs [~user@p5DDB5EB2.dip0.t-ipconnect.de] has joined #c-lightning 11:30 -!- tiagotrs [~user@p5DDB5EB2.dip0.t-ipconnect.de] has quit [Changing host] 11:30 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 11:36 < CubicEarths> One of my channels has been stuck "Shutting Down" for weeks now. 11:36 < CubicEarths> Ideas as to the cause? 11:36 < CubicEarths> And what can I do to close it out? 11:40 -!- Lightblock [uid302821@gateway/web/irccloud.com/x-sflsrojexdranerv] has joined #c-lightning 11:41 < Lightblock> @blockstream_bot yes, using bitcoin-cli to get channel txid 11:41 < Lightblock> @mn3monic but how to do it via bitcoin-cli? 11:41 < Lightblock> without additional scripts 11:48 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 12:08 -!- blyat [~blyat@cpe-172-72-228-93.carolina.res.rr.com] has quit [Quit: Leaving] 12:14 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 12:55 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 12:56 -!- fusion45 [~fusion44@31.6.42.114] has quit [Quit: Leaving.] 13:04 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 14:54 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 15:10 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 15:11 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 15:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.0] 15:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:56 < CubicEarths> I had lost my connection for a few minutes... not sure if I missed an answer re: my stuck channel closing question 16:36 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 16:51 -!- Lightblock [uid302821@gateway/web/irccloud.com/x-sflsrojexdranerv] has quit [Quit: Connection closed for inactivity] 17:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:29 < molz> CubicEarths, there was no answer to your question, you might want to open an issue on github 17:32 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 276 seconds] 17:37 < aj> CubicEarths: "lightning-cli close $PEER true" ? 17:38 < aj> CubicEarths: (forces a unilateral close, rather than trying to negotiate one) 18:15 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 18:16 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 18:27 < CubicEarths> aj: thanks. I tried it (as I maybe I tried once before?), and it did confirm it will be attempting a unilateral close. I'll see if it is still open later 18:37 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1639: Improve the output of decodemsg. (master...printwire-better) https://git.io/f4dhJ 19:06 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1640: Bolt update (master...bolt-update) https://git.io/f4djY 19:13 -!- face [~face@80.72.82.160.coresnet.bg] has quit [Ping timeout: 255 seconds] 19:33 < CubicEarths> It's closing, as expected :) 22:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 22:17 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ousphcxwzteoczwe] has joined #c-lightning 22:26 -!- shesek [~shesek@bzq-84-110-233-180.red.bezeqint.net] has joined #c-lightning 22:26 -!- shesek [~shesek@bzq-84-110-233-180.red.bezeqint.net] has quit [Changing host] 22:26 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 22:40 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 264 seconds] 23:32 -!- Lightblock [uid302821@gateway/web/irccloud.com/x-sfdnbubhasbwjqpn] has joined #c-lightning 23:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning