--- Log opened Tue Jan 15 00:00:21 2019
00:27 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning
00:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
00:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
00:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
00:53 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
00:53 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
01:08 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
01:08 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
01:18 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
01:18 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
01:28 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
01:28 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
01:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
01:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
01:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
01:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
01:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
01:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:04 -!- kexkey [~kexkey@172.98.82.4] has quit [Ping timeout: 268 seconds]
02:14 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:18 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
02:18 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:23 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
02:23 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
02:28 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
02:28 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
02:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
02:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
02:41 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:46 < bitonic-cjp> Is there a way to force a node to gossip its channels? I created a new isolated test network of 4 nodes; they are connected and have channels, but can't find a route.
02:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
02:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:53 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
02:53 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
02:54 < bitonic-cjp> When does a node to gossip anyway?
02:54 < bitonic-cjp> *decide to*
03:04 -!- deusexbeer [~deusexbee@093-092-181-141-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!]
03:13 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
03:13 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
03:17 -!- deusexbeer [~deusexbee@093-092-181-141-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
03:18 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
03:18 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
03:28 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
03:28 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
03:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
03:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
03:42 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:49 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:19 < blockstream_bot> [Christian Decker, Blockstream] They will send `node_announcement`, `channel_announcement` and `channel_update` once the funding transaction has 6 confirmations and is confirmed on both sides.
04:19 < blockstream_bot> [Christian Decker, Blockstream] They will also send out an update on reconnect
04:20 < blockstream_bot> [Christian Decker, Blockstream] And once every week as a keepalive
04:22 < blockstream_bot> [Christian Decker, Blockstream] Rempentant: with rendez-vous onion-routing the sender doesn't learn anything about the recipient. So, no, the recipient node does not have to identify itself to the sender once rendez-vous is implemented.
04:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
04:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
04:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
04:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
05:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
05:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
05:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
05:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
05:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
05:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
05:53 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
05:53 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
06:30 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
06:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
06:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
06:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
06:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
06:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
06:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
06:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
06:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
07:15 < blockstream_bot> [Scott Olsen, Blockstream] Hey guys... how long will CL keep a peer in this state by default?       "connected": false,
07:15 < blockstream_bot>           "state": "CHANNELD_SHUTTING_DOWN",
07:15 < blockstream_bot> [Scott Olsen, Blockstream] Trying to get a mutual close, but peer hasn't been seen for days now.
07:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
07:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
07:35 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
07:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
07:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
07:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
07:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
07:53 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
07:53 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
07:58 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
07:58 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
08:03 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
08:03 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
08:27 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving]
08:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
08:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
08:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
08:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
08:58 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
08:58 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
09:03 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
09:03 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
09:25 < blockstream_bot> [Scott Olsen, Blockstream] Anyone?
09:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
09:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
09:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
09:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
09:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
09:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
09:53 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
09:53 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
09:58 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
09:58 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
10:08 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
10:08 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
10:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
10:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
10:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
10:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
10:53 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
10:53 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
10:58 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
10:58 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:18 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
11:18 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
11:25 < rusty> ctrlbreak: It won't, you need to force close...
11:27 < ctrlbreak> ARggghhhh.
11:27 < ctrlbreak> Is this by design, or simply something that hasn't been implemented yet? Feature request?
11:28 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
11:28 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:31 < ctrlbreak> From the help "), otherwise just schedule a mutual close later and fail after timing out."
11:31 < ctrlbreak> So, essentially... they'll wait in this state indefinitely until they see the peer again :-/
11:33 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
11:33 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:35 < rusty> ctrlbreak: yes, it's kind of hard to know The Right Thing here.  If you don't say force, we timeout and give up.  If you say force, we timeout and force-close
11:36 < ctrlbreak> Understood.  Well, I've given them multiple days, so buh bye
11:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
11:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
11:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:44 < blockstream_bot> [Scott Olsen, Blockstream] w.t.f. is Rompert doing?  lol
11:44 < blockstream_bot> [Scott Olsen, Blockstream] https://1ml.com/channel/566193512752218112
11:46 < blockstream_bot> [Scott Olsen, Blockstream] I saw something like this the other day, and it looked as though they were all old inactive channels... but now I'm seeing several that are showing active.  Base Fee 102,010.101 sat !?!
11:48 < rusty> @Scott Olsen: yes, I hit one of those the other day.  I think they do it to indicate they don't actually have capacity, though I wasn't prepared to try :)
11:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
11:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
11:48 < rusty> (c-lightning refused to use a route citing large fees, and I looked and indeed, it wanted a $9 fee on $100!)
11:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning []
11:58 < ctrlbreak> Rusty; He appears to be leveraging these base fee updates for some kind of his own signaling?  Route 'steering?'
11:58 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
11:58 < ctrlbreak> "Those fees are rompert encoded signals that show to avoid sending through that edge"
11:58 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
12:07 < ctrlbreak> Soooo... basically a hack to indicate an extremely unbalanced channel.  *notbad.jpeg
12:07 < ctrlbreak> "@ctrlbreak the fees are specially coded. for instance if someone opens a channel to me i have 0 balance, so to deter ppl from routing thru it since it will not even be able to pass 1 sat, i set high fees on them. this is why i wanted a max_htlc-extension so i can just tell it in a more civilized way"
12:08 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
12:08 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
12:16 < ctrlbreak> So... here's a question that I think I think I already know the answer to; Once you've initiate a close on a channel... you can'
12:17 < ctrlbreak> *can't cancel it, can you?
12:27 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
12:38 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
12:38 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
12:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
12:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
12:57 -!- billybigpotatoes [~billybigp@2a02:c7f:c21f:8100:1c08:34e:f30b:3b06] has joined #c-lightning
12:59 < billybigpotatoes> Hello everyone. I'm trying to withdraw some sats from an old node here. I've updated to the most recent version and tried to force close the channels. I now seem to be stuck with some channels in a 'AWAITING UNILATERAL' state. Any ideas?
13:00 < ctrlbreak> BILLY.
13:08 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 244 seconds]
13:17 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
13:37 -!- booyah is now known as booyah_
13:39 -!- booyah_ is now known as booyah
13:41 < nothingmuch> ~
14:08 -!- Veggen [~vegard@engen.priv.no] has joined #c-lightning
14:09 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:10 -!- RainMan28_ [~Paintball@unaffiliated/rainman28] has joined #c-lightning
14:10 < RainMan28_> Hello all, when I do lightning-cli listpeers, I do not see any "state" showing but before I restarted lightning I was seeing that. Any idea what I'm doing wrong?
14:13 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:23 < RainMan28_> I'm following a guide that uses docker, but after doing lightning-cli stop, I am no longer able to get the lightning node to run in the same docker container as bitcoind
14:26 < RainMan28_> docker run --rm --name lightning --network container:bitcoind_mainnet -v /scratch/bitcoin/mainnet/bitcoind:/root/.bitcoin -v /scratch/bitcoin/mainnet/clightning:/root/.lightning --entrypoint /usr/bin/lightningd elementsproject/lightningd --network=bitcoin --log-level=debug
14:26 < RainMan28_> that is the command I'm using to start lightningd but it seems to end up creating its own container vs running in bitcoin_mainnet
14:27 < RainMan28_> the problem started after I did 'lightning-cli stop' and tried to start it again
14:33 < RainMan28_> @cdecker: any idea what I am doing wrong?
14:33 < billybigpotatoes> ctrlbreak, thanks for all the help the other day. Managed to upgrade to 0.6.3
14:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:43 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
14:43 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
14:48 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
14:48 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
14:48 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
15:03 < ctrlbreak> GAH :-/  You can't use RBF to LOWER a fee can you :-(  lol
15:14 < rusty> ctrlbreak: that's why we hate unilateral closes....
15:22 < ctrlbreak> yeah... I know :-/
15:26 -!- billybigpotatoes [~billybigp@2a02:c7f:c21f:8100:1c08:34e:f30b:3b06] has quit [Quit: Leaving]
15:37 < jb55> noticed gossipd was using 16GB of ram and 100% cpu... yikers
15:37 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:37 < rusty> jb55: upgrade to lastest master...
15:37 < jb55> roger
15:46 < molz> ver?
15:46 < molz> haha jk :D
16:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:54 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection]
17:00 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
18:06 < RainMan28_> Hello all, when I do lightning-cli listpeers, I do not see any "state" showing but before I restarted lightning I was seeing that. Any idea what I'm doing wrong?
18:06 < RainMan28_> I'm following a guide that uses docker, but after doing lightning-cli stop, I am no longer able to get the lightning node to run in the same docker container as bitcoind
18:06 < RainMan28_> docker run --rm --name lightning --network container:bitcoind_mainnet -v /scratch/bitcoin/mainnet/bitcoind:/root/.bitcoin -v /scratch/bitcoin/mainnet/clightning:/root/.lightning --entrypoint /usr/bin/lightningd elementsproject/lightningd --network=bitcoin --log-level=debug
18:06 < RainMan28_> that is the command I'm using to start lightningd but it seems to end up creating its own container vs running in bitcoind_mainnet
18:06 < RainMan28_> the problem started after I did 'lightning-cli stop' and tried to start it again
18:10 < rusty> RainMan28_: :(  Sorry,  awlays struggle with docker too..
18:11 < RainMan28_> yeah...I am super new to lightning and docker, but have been running a bitcoin-core node for years
18:11 < RainMan28_> been following a guide online but lost as to what to do now
18:12 < RainMan28_> one thing i'm not sure about is if c-lightning is supposed to run in the *SAME* docker container as bitcoind or in a different one
18:21 -!- grubles [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection]
18:23 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
18:23 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
18:23 < rusty>  RainMan28_: please let me know if you sort it out, so I can refer the next person who tries to you! :)
18:25 < RainMan28_> heh
18:28 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
18:28 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
18:46 -!- makey40 [~jodie@24.215.123.241] has joined #c-lightning
18:48 < makey40> does anyone know why there would be issues connecting to 104.198.32.198:9735
18:48 < makey40> is it down?
18:50 < makey40> This is happening after I upgraded to 0.6.3
18:50 < makey40> "CHANNELD_NORMAL:Attempting to reconnect"
18:51 < makey40> LOG:: lightning_connectd(26857): Failed connected out for 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432: 104.198.32.198:9735: Connection establishment: Connection timed out.
18:53 < makey40> Hmm the following just happened now ...
18:53 < makey40> lightningd(26848): lightning_channeld-02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 chan #1: peer_out WIRE_CHANNEL_REESTABLISH
18:56 -!- kexkey [~kexkey@172.98.82.10] has joined #c-lightning
18:57 -!- kexkey_ [~kexkey@172.98.82.10] has joined #c-lightning
18:57 < rusty> makey40: if that node is BLW, it may refuse to talk to us now we've disabled option_dataloss_protect.
18:58 < rusty> niftynei is debugging the issue now, we hope to reenable soon.
19:00 < makey40> BLW ?
19:01 -!- kexkey [~kexkey@172.98.82.10] has quit [Ping timeout: 268 seconds]
19:01 < rusty> makey40: someone decided to call their implementation "Bitcoin Lightning Wallet"...
19:01 < makey40> Good name .. ha!
19:03 < makey40> I actually think it is the block stream store.
19:03 < rusty> makey40: pretty sure tat doesn't accept direct connections?
19:04 < rusty> makey40: heh... no, it just doesn't advertise an address.
19:06 < makey40> I followed some step by step directions a while ago.. I think it was from the blockstream site...
19:07 < rusty> makey40: yeah, it used to at first launch, but then we removed the advertised addresses to try to make things more decentralized.
19:09 < makey40> Yea I kinda want to start again ... but I have funds in this channel.... not much
19:09 < rusty> makey40: did it finally connect?  Might want to close the channel then
19:09 < makey40> The status is now: "CHANNELD_NORMAL:Sent reestablish, waiting for theirs"
19:09 < rusty> makey40: weird... let me give it a try.
19:11 < makey40> OK cool
19:13 < rusty> Hmm, OK, connect is fine.  I wonder if it's hit the gossipd bug; I've pinged someone to upgrade it....
19:15 < makey40> rusty: I started upgrading yesterday both bitcoin and c-lightning.. compiling on a raspberry pi so it was down for about 24 hours..
19:16 < makey40> rusty: And just started the bitcoind and lightningd... So not sure if that had anything to do with it.
19:18 < rusty> makey40: I'm funding a channel with it now... I think it might be wedged a bit....
19:24 < makey40> rusty: It looks as if the number of  channels did something weird today... according to 1ml.com if I am reading that correct.
19:24 < makey40> rusty: https://1ml.com/node/02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432/history
19:46 < rusty> makey40: OK, it's upgraded.  That's weird...
19:47 < makey40> hmm
19:47 < makey40> rusty: Does it all work on your side.. with the funding?
19:48 < rusty> makey40: it hung up on me when it restarted, retrying...
20:08 < rusty> makey40: yay, finally a channel funded!
20:10 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
20:11 < makey40> rusty: Cool so it seems to work fine.
20:11 < makey40> rusty:my status showing --> CHANNELD_NORMAL:Sent reestablish, waiting for theirs
20:12 < makey40> rusty: So is this just something I should close and reopen.. or is it a problem that I can get some more info for you?
20:21 < makey40> rusty: I believe I can not send when in that state... I tried and it said "Could not find a route"
20:35 < rusty> makey40: yes, it won't try to route through that.
20:35 < rusty> makey40: try t disconnect and reconnect?
20:38 < makey40> rusty: K
20:39 < makey40> rusty: I did lightning-cli disconnect 02f6....... and got:
20:39 < makey40> rusty: { "code" : -1, "message" : "Peer is in state CHANNELD_NORMAL" }
20:40 < rusty> lightning-cli disconnect 02f6.......  true
20:40 < rusty> (i.e. force=True)
20:41 < makey40> rusty: ahhhh.. 
20:41 < makey40> rusty: Receiving tons of channel_update ...
20:42 < rusty> makey40: yeah, it will gossip 16M worth to start with :
20:43 < makey40> rusty: IT shows "CHANNELD_NORMAL:Reconnected, and reestablished.", 
20:44 < rusty> makey40: OK...  not sure why the previous one lost the plot :(
20:45 < makey40> rusty: But I did not manually reconnect... is that normal ... or will it disconnect after a bit.
20:45 < rusty> makey40: oh yeah, it will try to reconnect toany noed it has a channl w
20:45 < makey40> rusty: Thanks so much!
20:48 < RainMan28_> rusty: is it normal to not be in the gossip state when i connect to a peer?
20:49 < rusty> makey40: we should really time out connections which don't answer after some period... what goes getinfo say version is, for completeness?
20:49 < rusty> RainMan28_: it wll be in gossiping if there's no channel...
20:51 < RainMan28_> rusty: have a node i can try to connect mine to, to make sure its working?
20:51 < makey40> rusty: "version": "v0.6.3",
20:51 < RainMan28_> or could you try connecting to my node?
20:52 < rusty> makey40: https://github.com/ElementsProject/lightning/issues/2270
20:53 < rusty> RainMan28_: 024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605 128.199.202.168 2400:6180:0:d0::5cd2:a001 or 25qgmuz5bamegyj4.onion
20:54 < RainMan28_> rusty: ok just connected, but when i do lightning-cli listpeers i don't see any state of gossiping, this is what I see: https://dpaste.de/hcQO
20:55 < rusty> RainMan28_: ah, yes.  The gossiping state was a made up state, I think we got rid of it.  connected=True was what you want.  Is documentation out fo date?
20:55 < RainMan28_> oh hmm, maybe i accidentally updated somehow
20:56 < RainMan28_> earlier today before i did lightning-cli stop, when i would connect to a peer and do listpeers i'd see the state: GOSSIPING
20:56 < rusty> RainMan28_: You're on the new shiny then :)
20:56 < RainMan28_> rusty: are you able to connect to me at 0385f7cabe5185ad406ac649e59083b71fc65885a15e2c65701afe798d98840242@157.230.129.93:9735. ?
20:57 < RainMan28_> rusty: any way to determine which version I'm on? and thank you so much for all the help
20:57 < rusty> RainMan28_: lightning-cli getinfo
20:57 < RainMan28_> mine says "version": "", 
20:58 < rusty> { "code" : -1, "message" : "157.230.129.93:9735: Connection establishment: Connection refused. " }
20:58 < rusty> RainMan28_: Woah!  How did you build it?
20:58 < RainMan28_> rusty: https://medium.com/@dougvk/run-your-own-mainnet-lightning-node-2d2eab628a8b
20:58 < RainMan28_> following that guide
20:59 < rusty> RainMan28_: huh... I'd guess a weird docker image.
21:00 < RainMan28_> rusty: do you know of any newer more accurate guide? How did you set yours up?
21:00 < rusty> RainMan28_: I compiled mine from source, run it native on multiple machines...
21:01 < RainMan28_> could you try connecting to mine again rusty, i opened up port 9735 on ufw
21:01 < rusty> RainMan28_: report bug https://github.com/dougvk/lightning-node about version perhaps?
21:01 < rusty> RainMan28_: still connectionn refused :(
21:02 < RainMan28_> rusty: dang
21:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
21:37 < RainMan28_> rusty: could you try connecting to me now and see if any better?
21:37 < RainMan28_> if you don't mind :)
21:37 < rusty> RainMan28_: No :(
21:37 < RainMan28_> same connection refused?
21:37 < rusty> RainMan28_: yea,,,
21:37 < RainMan28_> ughh
21:38 < rusty> RainMan28_: definitely getting  a TCP reset frm that port
21:39 < rusty> RainMan28_: your ssh port is open though, so you're somewhere
21:40 < RainMan28_> ugh
21:46 -!- makey40 [~jodie@24.215.123.241] has quit [Ping timeout: 268 seconds]
22:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:23 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
23:23 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
23:27 -!- nothingmuch [~user@213.152.161.30] has quit [Ping timeout: 246 seconds]
23:28 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Client Quit]
23:28 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
23:42 < blockstream_bot> [Christian Decker, Blockstream] @PaintballPanda: by specifying `--network` like that you share the network cgroup of bitcoind, but you'll still spin up a new container. It really just means that you'll have the same ip as bitcoind and you can reach bitcoind over localhost
23:58 -!- farmerwampum [~farmerwam@162.219.178.10] has quit [Quit: farmerwampum]
23:58 -!- farmerwampum [~farmerwam@162.219.178.10] has joined #c-lightning
--- Log closed Wed Jan 16 00:00:22 2019