--- Log opened Fri Feb 22 00:00:57 2019
01:18 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
01:25 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
02:04 -!- kexkey [~kexkey@176.113.74.230] has quit [Ping timeout: 245 seconds]
02:16 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:19 < fiatjaf> using pylightning in a test environment, I'm able to instantiate 3 nodes, A, B, and C. and channels A->B, B->C and C->A.
02:20 < fiatjaf> I can send payments from A->B, B->C etc. but I can't send a payment B->A. why?
02:20 < fiatjaf> it doesn't find a route. but there is a route B->C->A, right?
02:20 < fiatjaf> do I have to wait until the routing table is built before I attempt to send the payment or something like that?
02:27 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
02:44 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
03:13 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
04:42 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
05:15 < m-schmoock> fiatjaf: yes, you have instruct the python test to wait until channel c->a is announced at b
05:16 < m-schmoock> i.e.  wait_for(lambda: len(lb.rpc.listchannels()['channels']) == 3)
05:18 < m-schmoock> (lb being your ln node B)
06:12 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:28 < fiatjaf> thank you!
06:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
07:24 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
07:34 -!- gettokid [~gettokid@2a07-a880-3101-1022-cb06-f0ec-eb72-c3e3.pool6.ovpn.com] has joined #c-lightning
07:40 < gettokid> Hi, I can´t get lightning started
07:41 < gettokid> ./lightningd -> Could not connect to bitcoind using bitcoin-cli. Is bitcoind running?
07:41 < gettokid> sudo systemctl status bitcoind -n2 --no-pager
07:41 < gettokid> [sudo] password for linux: 
07:41 < gettokid> ● bitcoind.service - Bitcoin daemon
07:41 < gettokid>    Loaded: loaded (/lib/systemd/system/bitcoind.service; disabled; vendor preset: enabled)
07:41 < gettokid>    Active: inactive (dead)
07:41 < gettokid> is this normal ?
07:43 < t0mix> gettokid: "Active: inactive (dead)" .. your bitcoind is not running
07:43 < m-schmoock> you bitcoind is not running ;)
07:43 < m-schmoock> ... damn you were faster
07:43 < t0mix> ^^
07:45 < gettokid> bitcoin-qt is running 
07:46 < gettokid> 100%
07:46 < gettokid> I also tried to run bitcoind only without the bitcoin-qt gui
07:46 < gettokid> still the same problem
07:53 < gettokid> but bitcoind itself is working fine ?
07:54 <@cdecker> m-schmoock: I'll review your PR tomorrow, still have a few things on my list for 0.7rc1
07:55 <@cdecker> gettokid: you need to configure `bitcoind` with `server=1`, `rpcuser=...` and `rpcpassword=...` and then you need to tell `lightningd` about the password and user (unless it can grab them from the bitcoin.conf file)
08:03 < gettokid> so adding the lines into the bitcoin.conf file ? what do I put for rpcuser and rpcpassword, anything random ?
08:07 < m-schmoock> cdecker: thats fine, alternatively you can first just give me input on the open issues so i can make the thing really done before final review
08:20 < rafalcpp> gettokid: are you sure bitcoin is running as mainnet not testnet, and has rpc ports opened etc
08:37 < gettokid> rafalcpp yes I am sure bitcoin is running as mainnet. I added server=1 rpcuser and rpcpassword into the bitcoin.conf file as cdecker stated, but I am still searching for the config file for lightningd 
08:48 < gettokid> where can i configure the rpc stuff on lightningd ?
08:48 < gettokid> to tell ´lightningd´ about the password and user
08:57 < gettokid> removed, cloned lightningd, configured and make and still the same error
08:58 < gettokid> bitcoin-cli echo 'hello world'
08:58 < gettokid> [
08:58 < gettokid>   "hello world"
08:58 < gettokid> ]
08:59 < gettokid> even echo working
08:59 < gettokid> but lightningd wont work
09:01 < m-schmoock> gettokid: still "Could not connect to bitcoind using bitcoin-cli. Is bitcoind running" ?   If so, is lightningd executed as the same user?
09:01 < m-schmoock> sounds like a permission issue on your machine
09:04 < gettokid> yes sure why should i execute is as another user
09:04 < rafalcpp> gettokid: I would try running bitcoin-cli first. and runnig it from same user as the user of lightningd
09:05 < rafalcpp> though connection is on IP localhost right, so not sure why user should matter that much
09:06 -!- kexkey [~kexkey@176.113.74.230] has joined #c-lightning
09:22 < gettokid> ok so after setting up a config file into the ./lightning directory and putting all the parameter for the port, localip, rpcuser, rpcpassword i am getting following error msg
09:22 < gettokid> Refusing to migrate down from version 90 to 89
09:28 < gettokid> ARGH
09:29 < gettokid> I think i need tu study computer science to be able to get these started
09:41 < gettokid> i just downloaded the latest version with git, how its possible that he is saying that i am migrating down ?
09:56 < gettokid> yo fuck IT Its working now
09:56 < gettokid> removed it and downloaded another version from github
09:58 < gettokid> the version migrate problem took me 30 minutes, while the otherone where I had to configure bitcoind and lightningd proberly about 8 hours maybe. I hope it will be easier in the future for other people
10:32 -!- gettokid [~gettokid@2a07-a880-3101-1022-cb06-f0ec-eb72-c3e3.pool6.ovpn.com] has quit [Ping timeout: 258 seconds]
12:08 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 245 seconds]
12:42 < fiatjaf> easy comes, easy goes
14:01 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
14:02 -!- booyah [~bb@193.25.1.157] has joined #c-lightning
14:19 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
14:58 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:05 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:39 < fiatjaf> m-schmoock, channels never get announced
15:40 < fiatjaf> I'm waiting for more than 60 seconds
15:40 < fiatjaf> each node still only has access to its 2 channels
16:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:36 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
16:43 < shesek> I recently added a "deposit" page to spark, which creates a new address via "newaddr" and displays it to the user (https://twitter.com/shesek/status/1097046906759495681). right now, whenever the user opens the page or clicks on the "switch to [bech32/p2sh]" button, a new address is generated.
16:44 < shesek> it would be useful if there was a way to create a new address and get both its sbech32 and p2sh representations, so I could toggle between them without creating new ones. it seems like getting the other representation is only possible right now using dev-listaddrs, which I obviously shouldn't rely upon (though, it appears like it is accidentally available even without DEVELOPER=1). does that seem like a reasonable thing to add?
16:47 < shesek> it would also perhaps make sense display the last generated address if it is still unused and have a button for explicitly creating new ones. this would require "dev-listaddrs" to indicate whether the address is used or not, and to make it a non-DEVELOPER only API. or maybe I could add an "getunusedaddr" rpc command as a plugin?
16:49 < shesek> though, this could lead to accidental address reuse, especially because c-lightning won't consider it used until the tx is confirmed. I guess generating a new address whenever the user opens the "deposit" page might be reasonable, and just make the "switch to [...]" retain the same one
17:10 < rusty> shesek: easy to add..'
17:14 < shesek> cool. I'll open a feature request.
17:17 < shesek> https://github.com/ElementsProject/lightning/issues/2390
17:24 < rusty> shesek: OK, as a result I've deprecated the 'address' output field in favor of explicit 'p2sh-segwit' and 'bech32' fields.  If you ask for 'all' you'll get both.
17:25 < rusty> shesek: deprecated simply means they're going away in 0.8, so no hurry.
18:20 < shesek> sounds great, thank you :)
18:21 -!- kexkey [~kexkey@176.113.74.230] has quit [Ping timeout: 255 seconds]
19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
20:48 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
20:48 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:59 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
21:04 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
21:06 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
23:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
23:29 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning
23:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:40 -!- booyah [~bb@193.25.1.157] has quit [Excess Flood]
23:40 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Excess Flood]
23:40 -!- fiatjaf [~fiatjaf@162.243.220.95] has quit [Excess Flood]
23:42 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning
23:42 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 249 seconds]
23:46 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning
--- Log closed Sat Feb 23 00:00:58 2019