--- Log opened Fri Jan 25 00:00:30 2019
02:03 -!- kexkey [~kexkey@199.229.249.116] has quit [Read error: Connection reset by peer]
02:12 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:32 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:33 -!- drolmer_ is now known as drolmer
05:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds]
05:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
06:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
07:03 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
07:10 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
07:48 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
10:14 < blockstream_bot> [Tim Ho, Blockstream] is it safe to upgrade clightning to the latest without closing my payment channels?
10:18 < blockstream_bot> [Tim Ho, Blockstream] i'm currently on v0.6.2rc1
10:24 < blockstream_bot> [Tim Ho, Blockstream] i'm hitting an issue where the cpu is sometimes pegged at 100% until i restart it
10:24 < blockstream_bot> [Tim Ho, Blockstream] i think it might be fixed, but i'm not sure of the upgrade process
12:01 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
14:28 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:49 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:02 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:12 < blockstream_bot> [Scott Olsen, Blockstream] Thorie,  Yes.  That particular issue has been addressed in *recent master* if I'm not mistaken.
15:29 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
16:26 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.3]
17:05 < blockstream_bot> [Tim Ho, Blockstream] Last time I tried to upgrade, I lost all my funds
17:05 < blockstream_bot> [Tim Ho, Blockstream] Should I close all my channels and transfer the bitcoin out to a new wallet?
18:00 < blockstream_bot> [Scott Olsen, Blockstream] Well, I can't speak for the devs, but if you are that worried about your funds (and you don't have many channels), then yes; I'd recommend going on-chain before upgrading to be safe (fees seem low right now).
18:02 < blockstream_bot> [Scott Olsen, Blockstream] When you are upgraded; feel free to open a channel to my node if you wish:  02a5a95669adcb170dc85a70eef8bdd3e60b459d83bb47b6aac3e17c58faffc919@skinneh.is-a-geek.com:9825
19:14 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection]
19:22 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
19:22 -!- kexkey [~kexkey@199.229.249.116] has joined #c-lightning
19:33 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
19:35 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
19:50 -!- deusexbeer [~deusexbee@080-250-075-168-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!]
19:50 -!- RainMan28_ [~Paintball@unaffiliated/rainman28] has left #c-lightning ["See ya!"]
20:07 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection]
20:48 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
21:06 -!- spinza [~spin@155.93.246.187] has quit [Read error: Connection reset by peer]
21:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
21:50 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
21:51 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
--- Log closed Sat Jan 26 00:00:31 2019