--- Day changed Wed Jan 24 2018
00:39 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has joined #c-lightning     
01:39 -!- vicenteH [~user@195.235.96.150] has joined #c-lightning     
02:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
02:50 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 248 seconds]     
03:00 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning     
03:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 255 seconds]     
03:01 < mn3monic> hello
03:02 < mn3monic> what status is 'ONCHAIND_OUR_UNILATERAL' ?
03:06 -!- shesek [~shesek@bzq-84-110-60-135.red.bezeqint.net] has joined #c-lightning     
03:06 -!- shesek [~shesek@bzq-84-110-60-135.red.bezeqint.net] has quit [Changing host]     
03:06 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
03:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
03:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds]     
04:34 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Quit: Leaving.]     
05:17 -!- xocite [local@gateway/vpn/privateinternetaccess/xocite] has joined #c-lightning     
05:59 -!- c-tester [ac618a6a@gateway/web/freenode/ip.172.97.138.106] has joined #c-lightning     
06:37 -!- Sam____ [40ecd01a@gateway/web/freenode/ip.64.236.208.26] has joined #c-lightning     
06:37 < Sam____> Good morning! I’m running a mainnet node, id `02e40b82365cd2a3908a481b712ba09858a5dee4cac997351db6cbaa175129907b`. First issue: I can’t find my node on https://lnmainnet.gaben.win/. Second: I’m getting “first peer not ready: WIRE_TEMPORARY_CHANNEL_FAILURE” when attempting to buy something from the Lightning Store. They both say connected: false, even though the first channel was funded yesterday. The second channel is 
06:38 < Sam____> lightning-cli listpeers { "peers" : 	[ 		{ "id" : "022d065a059294ff8796cf0b9df467ba76420c62eda92771a4063d15e7170020e0", "connected" : false, "channels" : 			[ 				{ "state" : "ONCHAIND_THEIR_UNILATERAL", "owner" : "lightning_onchaind", "short_channel_id" : "505730:2010:0", "funding_txid" : "326d8c97c7ccd707328d0634cec19f983179f74b33f3eb6ee83f9950e7afdbc3", "msatoshi_to_us" : 300000000, "msatoshi_total" : 300000000, "dust_limit_s
06:38 < Sam____> However, it seems to be able to find a route: lightning-cli getroute 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 3000000 0 { "route" : 	[ 		{ "id" : "0371190acfb2e92bd1faa6ce4d12ff248798515a92ac903ac14d31b5172d9b2917", "channel" : "505883:564:0", "msatoshi" : 3002033, "delay" : 167 }, 		{ "id" : "03095de5cd2e615ab6f445d7b956044b77bdd8d37a6e1a8ac67e76e4f0637a19ba", "channel" : "505800:1723:0", "msatoshi" : 
06:41 < Sam____> 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "channel" : "505523:729:0", "msatoshi" : 3500000, "delay" : 9 } ] }
06:46 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection]     
06:46 < c-tester> hey Sam,  can you recap how you funded the channel?
06:47 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
06:49 <@cdecker> Sam____, the TCP connection to your peer was lost, hence connected=false, however the channel is still alive, in case you can reconnect to the peer
06:57 < Sam____> I funded the first channel yesterday with `lightning-cli fundchannel`, with 300k satoshi. The second channel just got its 6 confirms, also 300k satoshi
06:57 < c-tester> For those struggling with 'WIRE_TEMPORARY_CHANNEL_FAILURE Capacity exceeded' this wasn't obvious to me, you need enough balance in the channel to both pay the invoice AND have enough left to maintain your channel
07:03 -githubby:#c-lightning- [lightning] cdecker opened pull request #756: Disable channel when losing the underlying connection (master...disable-on-shutdown) https://git.io/vNKOt
07:12 -!- jojeyh [~delphi@2602:306:b8b6:b970:21d0:4d4c:1b4b:b54c] has joined #c-lightning     
07:13 < Sam____> @cdecker how do I reconnect? when I run `lightning-cli connect 022d065a059294ff8796cf0b9df467ba76420c62eda92771a4063d15e7170020e0`, I get "channel ALL: Funding transaction spent"
07:20 -!- fullstep [~fullstep@52.144.114.197] has joined #c-lightning     
07:28 < c-tester> you need to specify IP and port...
07:28 < c-tester> li/lightning-cli connect 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 104.198.32.198 9735
07:47 < Sam____> I restarted lightning-cli and reconnected to the 2 nodes. Now, `listpeers` shows 4 peers instead of 2. { "peers" : 	[ 		{ "id" : "0371190acfb2e92bd1faa6ce4d12ff248798515a92ac903ac14d31b5172d9b2917", "connected" : false, "channels" : 			[ 				{ "state" : "ONCHAIND_THEIR_UNILATERAL", "owner" : "lightning_onchaind", "short_channel_id" : "505883:564:0", "funding_txid" : "9c9b4926556c14882f020480a2bd8f89d831c2d88da78269628c410dc7c861
07:48 < Sam____> However, they all still say connected: false.
07:50 < Sam____> After the restart, it can't find a route.  lightning-cli getroute 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 20000000 1 "Could not find a route"
07:52 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #c-lightning     
07:54 -!- Sam____ [40ecd01a@gateway/web/freenode/ip.64.236.208.26] has quit [Ping timeout: 260 seconds]     
07:59 -!- xocite [local@gateway/vpn/privateinternetaccess/xocite] has quit [Quit: leaving]     
08:24 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has joined #c-lightning     
08:29 <@cdecker> Ok, so the remote end has decided not to wait for you to come back. Funds should show up in listfunds
08:29 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vNKEG
08:29 -githubby:#c-lightning- lightning/master 96d093f practicalswift: Fix typos
08:30 -githubby:#c-lightning- [lightning] cdecker closed pull request #728: pylightning: Add and move example to README (master...pylightning-fix-example) https://git.io/vNV0R
08:31 < c-tester> what should my bitcoin.conf contain in order to support c-lightning??  my node is not appearing on  https://lnmainnet.gaben.win/
08:42 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vNKz2
08:42 -githubby:#c-lightning- lightning/master 3cb03ab William Casarin: bitcoin: add test programs to ALL_TEST_PROGRAMS...
08:43 -githubby:#c-lightning- [lightning] cdecker closed pull request #687: Require nonzero payments (master...pay-nonzero) https://git.io/vNzp1
08:52 < vigorousbearhunt> cdecker, My node panics with that: https://pastebin.com/raw/bmWtqiNV
08:52 < vigorousbearhunt> I have opened a channel with that node days ago.
08:53 < vigorousbearhunt> I used the close command, now it says: "Peer is in state CHANNELD_SHUTTING_DOWN"
08:55 <@cdecker> vigorousbearhunt, seems that node changed its identity (!?!?) so you won't be able to connect anymore
08:55 <@cdecker> Closing is the correct thing to do here
08:57 < vigorousbearhunt> cdecker, Thanks. I cannot even ping their ip. I used the close command. I cannot for info on closing channels in the c-lightning docs though.
08:57 < vigorousbearhunt> Is the close command sufficient?
08:57 <@cdecker> Probably the channel was already closed, but it's lingering since we don't clear DB entries until #740 gets merged
08:57 < vigorousbearhunt> oh     
08:57 <@cdecker> vigorousbearhunt, yep, close will settle on-chain and return any funds you owned, - the on-chain fee
08:58 < vigorousbearhunt> Ok. Will it send back to the same address?
08:59 < vigorousbearhunt> If that's the case, 2NA5ViFDeCY34VZijYf71frgSv4fvPE4NFE has no balance. (My address)
08:59 < vigorousbearhunt> (Will be away for some hours)
09:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lwcabvtkfmybtjpt] has quit [Quit: Connection closed for inactivity]     
09:31 < grubles> is there a way to query for a channel's balance?
09:32 < c-tester> cli/lightning-cli listfunds ?
09:32 < grubles> no that's for what funds you have available to open channels
09:32 < grubles> (i think)
09:33 < truk_> cdecker, Thank you for the update on #751. Question - If I run into any more issues should I post in the IRC first or open on git? 
09:36 < c-tester> ok.. grubles, any idea what i need in my bitcoin.conf file to support c-lightning.. my node is still not appearing on #recksplorer site
09:38 < c-tester> so far i have ports 8333 and 9735 open on router,  bitcoind synced,   launched lightningd with alias, and IP.   Connected to blockstream node....
09:39 < grubles> do you have a channel open?
09:39 < grubles> i think recksplorer tracks channels
09:39 < grubles> using describegraph
09:39 < grubles> (in lnd)
09:40 < c-tester> channel open requires funding?
09:41 < grubles> you have to fund an address, then open a channel with fundchannel
09:43 < c-tester> ok, so   cli/lightning-cli newadddr, send satoshis to adress with trezor wallet,  wait for 6 confirmations,  then cli/lightning-cli fundchannel ??
09:44 < grubles> yep     
09:44 < c-tester> ok, not sure of the syntax of fundchannel,, which "id"
09:44 < grubles> fundchannel pubkey
09:44 < grubles> or id
09:45 < c-tester> ah...
09:45 < c-tester> right.
09:45 < c-tester> ok     
09:45 < grubles> fundchannel pubkey amount
09:45 < grubles> i believe is the syntax
09:45 < c-tester> then connect to blockstream node?
09:49 < grubles> well you should be connected to a node/peer to begin with
09:52 < c-tester> thanks.. .will try
09:59 < grubles> hm so how do i actually pay an invoice?
09:59 < grubles> is it with: pay <invoice>
10:01 < ebx> that's what I've been using grubles
10:02 < grubles> ok yeah
10:02 < grubles> the description mentions bolt11 
10:02 < grubles> which is...'BOLT #11: Invoice Protocol for Lightning Payments'
10:02 < c-tester> cli/lightning-cli pay "Need bolt11 string"
10:03 < grubles> hehe ye
10:03 < grubles> yep     
10:03 -!- freerk [577b8baf@gateway/web/freenode/ip.87.123.139.175] has joined #c-lightning     
10:03 < ebx> ah sorry I was thinking invoice and bolt11 were synonymous
10:04 < c-tester> wait isnt't the bolt11 string what blockstream provides during store checkout?
10:05 < ebx> that's my understanding of it
10:05 < ebx> the 'lnbc.....'
10:09 < grubles> yea bolt11 is the standard invoice (i think)
10:09 < c-tester> ok..
10:09 < grubles> https://github.com/lightningnetwork/lightning-rfc/blob/master/11-payment-encoding.md
10:15 -!- alexann [~Alex@46.217.155.153] has joined #c-lightning     
10:15 -!- ebx_ [~ebx@12.226.6.52] has joined #c-lightning     
10:16 -!- vitaminc [~vitaminc@192.5.151.254] has joined #c-lightning     
10:16 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 264 seconds]     
10:19 -!- AndyMillar [~andy-free@andymillar.co.uk] has joined #c-lightning     
10:31 -!- fullstep [~fullstep@52.144.114.197] has quit [Quit: WeeChat 2.0]     
10:35 -githubby:#c-lightning- [lightning] cdecker closed pull request #694: Fix zero msatoshi (master...fix-zero-msatoshi) https://git.io/vNgVb
10:37 < c-tester> just realized I don't have a Bitcoin.conf file... If I fund my address, am I not exposed to losing satoshis?
10:43 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 248 seconds]     
10:45 < grubles> so how does sendpay work
10:45 < grubles> sendpay pubkey?
10:45 < grubles> not sure what that is used for
10:48 < c-tester> "sendpay", "description" : "Send along {route} in return for preimage of {rhash}" }, 
10:48 < c-tester> could it be you can specify the route the payment takes?
10:48 < ebx_> grubles, you can specify the route json (like gotten from `getroute`) directly to the command
10:49 < grubles> oh i see
10:49 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Remote host closed the connection]     
10:50 < ebx_> it used to be the recommended way to send in the readme, you can look what it said if you look at: https://github.com/elementsproject/lightning/commit/3f2d93de930ad180060530b61c9a626c0033d252
10:50 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #c-lightning     
10:50 < ebx_> -route=$(cli/lightning-cli getroute <recipient_id> <amount> 1 | jq --raw-output .route -)
10:50 < ebx_> -cli/lightning-cli sendpay "$route" <rhash>
10:54 < c-tester> ebx.  before I fund my channel, is there any fee setting in lightning that should be changed?
10:55 < grubles> c-tester, it was recommended to me to use bitcoin-cli settxfee to set your fee
10:55 < grubles> but my bitcoind apparently doesn't have that command (deprecated?)
10:56 < c-tester> ok     
10:57 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has joined #c-lightning     
10:58 < c-tester> Hey Jonass, saw your stickers package on twitter this morning!  good job
10:59 < ebx_> ah, I wasn't even aware of the settxfee recommendation (I didn't realize it took that info) -- if you meant the base_fee stuff that is fine at default with latest code anyway
10:59 < c-tester> <grubles>, if I do a bitcoin-cli getinfo it shows.  "relayfee": 0.00001000,
11:00 < ebx_> grubles, what version of bitcoin-cli? I have an old version of 0.15.1 and it has it, not sure if it was removed later though
11:00 < c-tester> actually two fee related settings.  "paytxfee": 0.00000000,   "relayfee": 0.00001000,
11:00 < grubles> ebx_, hm mine is 0.15.1
11:01 -githubby:#c-lightning- [lightning] jb55 opened pull request #758: chainparams: fix regtest bip173_name (master...rt-173-fix) https://git.io/vNKHe
11:07 < ebx_> yeah, just double checked and settxfee is definitely there/working for me for the 0.15.1 release -- fwiw I built it back in december
11:07 -!- ebx_ [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
11:12 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
11:16 < freerk> Hi, any ideas how I can get access to my funds again? I installed c-lightning on sunday and tried to open a few channels (mainnet). Probably before I got enough confirmations on the transaction where I funded the c-lightning address, so probably I ran into issue 707 or 689 on the bugtracker. I tried to change the output status in the sqlite like explained in issue 634, but then funding new channels fails with "Missing inputs, co
11:16 < c-tester> freerk, what do you see when you listfunds
11:17 < freerk> several txids, some with output 0 and some with output 1
11:18 < freerk> only one of the txids can be found on the blockchain, the other 5 not
11:24 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has quit [Remote host closed the connection]     
11:25 < c-tester> sorry not sure
11:28 -!- lugg_ [uid274294@gateway/web/irccloud.com/x-lwfypvsdkwxjphva] has joined #c-lightning     
11:30 < lugg_> any idea what could be causing WIRE_TEMPORARY_CHANNEL_FAILURE: Maximum value exceeded ?
11:30 < lugg_> I'm getting that with a pay command, and the amount isn't all that large (0.0018 btc)
11:33 < c-tester> lugg,, someone tweeted this earlier today...
11:33 < c-tester> For those struggling with 'WIRE_TEMPORARY_CHANNEL_FAILURE Capacity exceeded' this wasn't obvious to me, you need enough balance in the channel to both pay the invoice AND have enough left to maintain your channel
11:33 < lugg_> oh, hmmm
11:34 < lugg_> that last part -- "enough left to maintain your channel" -- how do you know how much that is?
11:34 < lugg_> in my case, I moved 0.002 btc to my lightning wallet. And then opened a channel with 0.0018 btc to pay for a 0.0014 purchase
11:35 -githubby:#c-lightning- [lightning] practicalswift opened pull request #761: Onboarding: Make log output texts friendlier to new users (master...make-onboarding-more-userfriendly) https://git.io/vNKFe
11:39 < c-tester> lugg, not sure.. I just funded my address with 100,000 satoshis, waiting for confirms before ordering a couple of stickers....
11:40 -githubby:#c-lightning- [lightning] practicalswift opened pull request #762: Onboarding: Adjust logging for common non-fatal conditions from info … (master...adjust-loglevel-to-avoid-console-spam) https://git.io/vNKFb
11:41 < lugg_> I have such a hard time thinking in terms of satoshis, lol
11:42 < lugg_> I guess my 0.0018 BTC is 180,000 satoshis
11:42 < c-tester> use these sites for conversion... https://99bitcoins.com/satoshi-usd-converter/  or  preev.com
11:42 < lugg_> I used my own page that I forgot I had even made, heh https://pug.sh/bitcoin/units/
11:45 < c-tester> nice... bookmarkd
11:49 < c-tester> how many confirms did you wait for before funding channel?
11:50 < c-tester> i'm getting "can't afford funding transaction" after 2 confirms
11:52 < lugg_> I believe it let me fund the channel with a single confirm
11:54 < lugg_> I closed the channel (going to try opening one directly with blockstream's store) ... first time trying that. The status switches to CHANNELD_SHUTTING_DOWN and it sits there for a while, it seems
11:55 < vigorousbearhunt> lugg_, I have the same problem on testnet
11:55 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Remote host closed the connection]     
11:56 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #c-lightning     
11:56 < vigorousbearhunt> lugg_, I got CHANNELD_SHUTTING_DOWN on testnet
11:57 < lugg_> how long does it stay that way? (or do you know?)
11:57 < vigorousbearhunt> lugg_, cdecker said: Probably the channel was already closed, but it's lingering since we don't clear DB entries until #740 gets merged
12:00 < c-tester> ..vigorousbearhunt.... any ideas on this message....
12:00 < c-tester> li/lightning-cli fundchannel 0201c0a1c3fdbefdd72fba461df6500f7ed773f3d9d63f794634c973c70dbc096b 100000 "Cannot afford funding transaction"
12:00 < vigorousbearhunt> I think it wont change unless the channel entry in the DB is removed
12:01 < vigorousbearhunt> c-tester, I don't know, you should try sending funds from a faucet to ensure it has nonzero balance
12:03 < c-tester> listfunds shows..    "output" : 0, "value" : 100114 } ] }
12:03 < c-tester> i sent from my Trezor
12:03 < vigorousbearhunt> mainnet?
12:03 < c-tester> yes     
12:04 < c-tester> 5 confirms so far
12:05 < vigorousbearhunt> I guess you already have a channel open
12:05 < vigorousbearhunt> right?
12:05 < c-tester> cli/lightning-cli listpeers { "peers" :  	[  		{ "state" : "GOSSIPING", "id" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "netaddr" :  			[ "104.198.32.198:9735" ], "connected" : true, "owner" : "lightning_gossipd" } ] }
12:06 < c-tester> that  newaddr command created a wallet address from the backend  bitcoind right?
12:08 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 260 seconds]     
12:16 < lugg_> @vigorousbearhunt hmmm, interesting. If the channel was closed, though, wouldn't the funds show up again when I do a list funds?
12:16 < lugg_> listfunds*
12:17 < c-tester> lugg, what does your bitcoin-cli getwalletinfo show
12:18 < lugg_> "balance": 0.00000000
12:18 < lugg_> (I never put any coins in there, I only put them into the wallet generated within c-lightning)
12:18 < vigorousbearhunt> hm     
12:18 < c-tester> same here... I thought the backend node/wallet held the btc
12:18 < lugg_> I think it's a separate wallet
12:19 < c-tester> ok good.. 
12:19 < c-tester> was worried..
12:19 < lugg_> that's my assumption anyway
12:19 < vigorousbearhunt> yeah It's a separate wallet afaik.
12:19 < lugg_> I feel like every lightning discussion in every channel/slack/whatever I'm having is the blind leading the blind :P
12:19 < lugg_> but it's fun to be learning
12:19 < lugg_> (even the hard way, heh)
12:20 < c-tester> for sure...
12:20 < lugg_> so yeah, that one channel that's still showing as shutting down is holding "msatoshi_total" : 180000000 and I assume I'll eventually somehow see that again when I do a listfunds command, but I don't as of now
12:20 < c-tester> now when I half the satohsi amount... i get a differenet  status...
12:20 < lugg_> is closing a channel supposed to be an instantaneous process?
12:20 < c-tester> cli/lightning-cli fundchannel 0201c0a1c3fdbefdd72fba461df6500f7ed773f3d9d63f794634c973c70dbc096b 50000 "Peer not connected"
12:21 < c-tester> but my list peers shows im connected.
12:21 < lugg_> strange...
12:26 < jojeyh> c-tester, what state is the connection with the peer in? 
12:26 < c-tester> I got.. it...
12:27 < c-tester> I was using my own id instead of blockstreams
12:28 < c-tester> 	{ "state" : "CHANNELD_AWAITING_LOCKIN", "owner" : "lightning_channeld", "funding_txid" :
12:30 < c-tester> wonder how long that will take to lock in
12:37 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has joined #c-lightning     
12:39 < peterm> Hello all: I have a setup issue. I am running bitcoind, fully downloaded, and want to add c-lightning. However I get: lightning_gossipd(...): TRACE: Failed to bind on 2 socket: Address already in use
12:39 < peterm> any ideas what might be wrong?
12:39 < c-tester> Hi peter,, i got that also..  doesnt seem to affect anything...
12:39 < peterm> Compilation went fine, I see the blocks being downloaded
12:39 < c-tester> my channel is UP.
12:39 < c-tester> { "state" : "CHANNELD_NORMAL", "owner" : "lightning_channeld", "short_channel_id" 
12:40 < peterm> How can i check if the it is runing fine?
12:41 < peterm> Is there any place where my node should popup in a network graph?
12:41 < c-tester> what command did you use to launch?
12:42 < peterm>  ./lightningd/lightningd --ipaddr xx.xxx.xxx.xx  --log-level=debug --network=bitcoin
12:42 < c-tester> dont forget alias name..
12:42 < c-tester> lightningd/lightningd --network=bitcoin --rgb=ff00ff --alias =YOURALIASNAME --ipaddr=XXX.XXX.XXX.XXX --log-level=debug
12:42 < c-tester> rgb is color of label..
12:43 < peterm> Let me try
12:43 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
12:43 < c-tester> my channel just confirmed, so waiting for it to appear on network graph.
12:44 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
12:45 < peterm> Should it appear in https://lnmainnet.gaben.win/ ?
12:46 -githubby:#c-lightning- [lightning] jb55 opened pull request #763: Implement bech32 p2wpkh funding addresses (master...bech32-notests) https://git.io/vN6eA
12:46 < c-tester> yes     
12:47 < c-tester> after you have funded an address, then connected to blockstream node..
12:47 < c-tester> have you done that?
12:48 < peterm> Nope, it is just running
12:48 < c-tester> ok i can walk you through what to do 
12:48 < peterm> wold be nice
12:48 -githubby:#c-lightning- [lightning] jb55 opened pull request #764: tests: bech32 p2wpkh funding tests (master...bech32-tests) https://git.io/vN6vY
12:48 < c-tester> ok here is a recap of what I did... 
12:49 < c-tester> opened port 8333 and 9735 on router
12:49 < peterm> they are open
12:49 < c-tester> ok. launched bitcoind and got it fully synced.
12:49 < peterm> done
12:50 < c-tester> launched lightning with the command above... let it run for a few minutes until add block scrolling stops...
12:50 < AndyMillar> bah, waiting for bitcoind to sync sucks :(
12:50 < peterm> :-) Mine is synced
12:51 < peterm> last block: 0000000000000000007968c4352f7c0c930d2a893c13f97661cb98ea350c9033
12:51 < peterm> done I guess
12:51 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has joined #c-lightning     
12:52 < c-tester> perfect... next I created a funding address with this command...   cli/lightning-cli newaddr
12:52 < c-tester> cli/lightning-cli newaddr
12:52 -githubby:#c-lightning- [lightning] jb55 closed pull request #758: chainparams: fix regtest bip173_name (master...rt-173-fix) https://git.io/vNKHe
12:53 < peterm> ok got new address
12:53 < peterm> starts with a 3
12:53 < c-tester> yep! segwit
12:53 < peterm> now I need to fund it, right? How much?
12:53 < peterm> How can I see that address again?
12:54 < c-tester> I sent 100,000 satoshis to it with my trezor...  use this site for conversion https://99bitcoins.com/satoshi-usd-converter/
12:54 < c-tester> about 12 bucks
12:54 < peterm> firing up my trezor
12:54 < c-tester> I only intend on getting a sticker for now..
12:54 < c-tester> now I paid 240 satoshis per byte... got 6 confirms pretty quickly...
12:55 < c-tester> used this site for fee estimation https://bitcoinfees.earn.com/
12:55 < c-tester> could have been alot less.. but was impatient..
12:55 < peterm> done, sent
12:56 < peterm> is there a way to see this address again ?
12:56 < peterm> cli/lightning-cli oldaddr
12:56 < peterm> ?     
12:57 < c-tester> checking..
12:57 < peterm> cli/lightning-cli listfunds is empty
12:58 < c-tester> yes.. needs confirmations
12:58 < peterm> waits ...
12:59 < peterm> what is your alias ?
12:59 < c-tester> while you wait you can connect to blockstream node....
12:59 < c-tester> cli/lightning-cli connect 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 104.198.32.198 9735
12:59 < c-tester> that is node id , ip and port
12:59 < c-tester> then do a listpeers
13:00 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has joined #c-lightning     
13:00 < peterm> nizze
13:00 < peterm> { "state" : "GOSSIPING", "id" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "netaddr" :  			[ "104.198.32.198:9735" ], "connected" : true, "owner" : "lightning_gossipd" } ] }
13:00 < c-tester> My Alias is YYZ_TORONTO_YYZ   but I dont see it yet...
13:01 < c-tester> ok..
13:01 < c-tester> once you have funds visible with listfunds, you fund the channel
13:02 < c-tester> cli/lightning-cli fundchannel 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 100000
13:02 -!- danielh [~danielh@speedtest.sbbs.se] has joined #c-lightning     
13:02 < c-tester> that is node id of blockstream and satoshi amount
13:03 < peterm> ok understood
13:03 < peterm> wow that was fast, thanks a bunch, I ll set you some cents once its is funded
13:03 < danielh> hey, I'm trying to close some channels to increase the capacity however after closing the channels they are stuck in ONCHAIND_MUTUAL state which makes me unable to establish a new channel to the same node
13:04 < danielh> anyone know what Im missing here?
13:05 < c-tester> np peter... took me all day on here with help from others ....    but  i still waiting for my alias to appear and make the sticker purchase
13:07 < c-tester> BTW, once you have confirms you need to wait at least 10 minutes for channel lockin,  you will see its status with the listpeers command
13:07 < c-tester> 	{ "state" : "CHANNELD_NORMAL", "own
13:08 < peterm> so status changes from GOSSIPING to _NORMAL ?
13:09 < c-tester> no different field... once you have funded, you get alot more status fields...
13:09 < c-tester> cli/lightning-cli listpeers { "peers" :  	[  		{ "id" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "connected" : true, "netaddr" :  			[ "104.198.32.198:9735" ], "channels" :  			[  				{ "state" : "CHANNELD_NORMAL", "owner" : "lightning_channeld", "short_channel_id" : "505934:1295:1", "funding_txid" : "197b49670c23dcd6dcfea3af9e0aeb798539f26a2df5591c4e60c8c3df231913", "msatoshi_to_us" : 50000000, "m
13:10 -!- jb55 [~jb55@d108-172-210-7.bchsia.telus.net] has quit [Ping timeout: 252 seconds]     
13:10 -!- freerk [577b8baf@gateway/web/freenode/ip.87.123.139.175] has quit [Quit: Page closed]     
13:10  * peterm waits for a block
13:15 < buZz> ;;tslb
13:15 < buZz> dang, no gribble
13:17 -!- PockeT [4da2683e@gateway/web/freenode/ip.77.162.104.62] has joined #c-lightning     
13:17 < PockeT> Hello
13:17 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]     
13:17 < c-tester> Hi Pocket
13:18 < buZz> lo     
13:18 < PockeT> Is there a way to see how many tx I have routed trough and if i have fees collected?
13:20 < c-tester> wouldnt getlog show any routed txs?
13:25 < PockeT> could be.. I guess
13:26 < peterm> the miners are sleeping
13:26 < c-tester> "Three Armed Men Attempted to Rob a Bitcoin Exchange In Canada"
13:26 < peterm> :-)     
13:26 < c-tester> QuadrigaCx?
13:27 < c-tester> http://www.cbc.ca/news/canada/ottawa/robbery-ottawa-search-bitcoin-1.4501719
13:28 < peterm> strange people those Canadians ...
13:28 < peterm> :-)     
13:28 < c-tester> lol     
13:29 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #c-lightning     
13:30 < c-tester> damn, my alias still not showing on the graph... but confirmed my channel is public.
13:30 < c-tester> You can check the status of the channel using cli/lightning-cli listpeers, which after 1 confirmation should say that state is CHANNELD_NORMAL; after 6 confirmations you can use cli/lightning-cli listchannels to verify that the public field is now true
13:31 < c-tester> actually no.. my channel is public" : false,   WTF
13:34 < c-tester> any ideas why my channel would not be public,,, have way over 6 confirms.
13:34 < peterm> let met check
13:35 < peterm> donot see your alias
13:36 < peterm> 46 mins since last block
13:36 < c-tester> yeah it wont appear if the public status is false
13:37 < peterm> how do you see that ?
13:37 < peterm> listpeers?
13:39 < c-tester> listchannels
13:40 < c-tester> its a big list.... i pipe it to text file    >list.txt  then search on my id
13:40 < c-tester> or grep it
13:40 < peterm> ok, so you see all the channels then?
13:40 < c-tester> yes     
13:41 < c-tester> check it out.. 
13:41 < c-tester> cli/lightning-cli listchannels |grep 0201c0a1c3fdbefdd72fba4
13:41 < peterm> that will be a large file
13:41 < peterm> hmm     
13:41 < peterm> I donot see this
13:42 < peterm> grep does not get any result
13:42 < peterm> strange
13:42 < c-tester> cli/lightning-cli listchannels  does not show anythng for you?
13:42 < peterm> yes     
13:42 < peterm> but not after the grep, your channel is not in my list
13:43 < c-tester> replace the first 10 or so characters with your id...
13:43 < peterm> (almost one hour wothout blokcs)
13:44 < c-tester> you mean confirmations on the blockchain?
13:44 < peterm> yep     
13:44 < c-tester> how many sats  per byte did you pay?
13:44 < peterm> enough
13:44 < peterm> 220 or so
13:44 < peterm> but there was no single block 
13:44 < c-tester> there is a block every 10 mins
13:46 < peterm> on average
13:46 < peterm> so no
13:46 < c-tester> let me confirm that
13:46 < c-tester> your right.. last block was 53 mins ago
13:46 < c-tester> https://tradeblock.com/bitcoin
13:47 < c-tester> I got my 6 confirms super quick... lucked out I guess.
13:48 < peterm> Finally a block
13:48 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning     
13:52 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-aictmwivytctoebf] has joined #c-lightning     
13:59 < c-tester> What happens if I restart my bitcoind and lightning instances?  do funded channels remain active?
13:59 < peterm> I hope so
14:01 < c-tester> active" : true, "public" : true, "last_update" : 1516831196,
14:01 < c-tester> im good.. must have been that slow block 
14:02 < c-tester> now I'm on the network Graph
14:02 < peterm> I see you
14:02 < c-tester> cool.. how about your channel list.. do you see everyone?
14:03 < peterm> let me see
14:03 < peterm> nope
14:03 < peterm> no 0236640
14:04 < peterm> wait
14:04 < c-tester> cli/lightning-cli listchannels 
14:04 < peterm> yep i  see you
14:05 < peterm> to 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432
14:05 < peterm> 5 blocks in a row
14:05 < peterm> 4 confirms
14:10 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has joined #c-lightning     
14:10 < c-tester> nice.. your listpeers should show channel status
14:11 < peterm> your channel is double sided
14:12 < peterm> I see two channels 
14:13 < peterm> 50000 sat?
14:14 < c-tester> yes 50000
14:15 < c-tester> what do you double sided?
14:16 < peterm> from you to 02f6725f9c1 and also the other way around
14:17 < peterm> my channel is not visble
14:19 < c-tester> what are the first 10 characters of your node id...
14:19 < c-tester> ill grep it from the list..
14:20 < peterm> 023640ad2c2f
14:20 < c-tester> don't see it..
14:21 < peterm> should you?
14:21 < peterm> not yet funded
14:21 < c-tester> oh right.. your waiting on 6 confirms
14:21 < peterm> 5 already
14:21 < peterm> should I fund it ?
14:22 < c-tester> now I read somewhere you can "refill" your funds without another onchain tx... how would that work>?
14:23 < peterm> 8 confirms
14:24 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
14:24 < peterm> funded channel
14:24 < peterm> hmm     
14:24 < peterm> no channel seen
14:25 < c-tester> so you ran li/lightning-cli fundchannel 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 100000
14:25 < c-tester> thats blockstreams node id and amount of sats
14:26 < peterm> done
14:27 < c-tester> now listpeers will show channel status
14:28 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds]     
14:30 < peterm> nope
14:30 < c-tester> no response from that command
14:31 < c-tester> ?     
14:32 < c-tester> see if your available funds were reduced  cli/lightning-cli listfunds
14:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
14:34 < peterm> they were
14:34 < peterm> all gone
14:35 < peterm> damn
14:35 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #c-lightning     
14:36 -!- vitaminc_ [~vitaminc@pool-71-114-78-15.washdc.fios.verizon.net] has joined #c-lightning     
14:36 < ossifrage> How do I convince lightningd to use my bitcoin auth cookie?
14:36 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning     
14:37 < c-tester> so listpeers shows your connected to blockstream right?
14:38 < peterm> yep     
14:38 < peterm> CHANNELD_AWAITING_LOCKIN
14:38 -!- vitaminc [~vitaminc@192.5.151.254] has quit [Ping timeout: 248 seconds]     
14:38 < c-tester> ok looks good.. it will eventually show Channeld normal
14:39 < c-tester> took me about 10 minutes
14:39 < peterm> good
14:39 < ossifrage> A grep of the source shows no references to cookie, does it only support having the rpc credentials in bitcoin.conf?
14:39 < peterm> how can i see the channel size?
14:39 < CubicEarths> If I wanted to control my lightning node from python, any ideas about technique I should use? 
14:40 -!- vitaminc_ [~vitaminc@pool-71-114-78-15.washdc.fios.verizon.net] has quit [Ping timeout: 240 seconds]     
14:40 < c-tester> maybe once the channel is normalized.. you will be able to list it with listchannels..
14:41 < peterm> could you list it ?
14:41 < ebx> CubicEarths, https://github.com/elementsproject/lightning/tree/master/contrib/pylightning
14:41 < CubicEarths> ebx: amazing. thanks
14:41 < c-tester> your 023640ad2c2f right>?
14:42 < ebx> np, I'm utilizing it myself as of late
14:42 < peterm> yep     
14:42 < c-tester> don't see it yet.. should show up soon
14:42 < peterm> nizzze
14:42 < peterm> next challange is sending you some 
14:42 < c-tester> ill send you some sats also.. 
14:43 < c-tester> EBX,, are you familiar with refilling channels without another on chain TX?
14:43 < peterm> Wait a nit setting up a channel shoudl not take 6 confirmations ?
14:43 < peterm> *bit
14:44 -!- Saevar [2e166296@gateway/web/freenode/ip.46.22.98.150] has joined #c-lightning     
14:44 < ebx> c-tester: no, I haven't done that yet actually -- though I have some unanswered questions about just that subject so I've been meaning to spend some time reading about it in the spec / testing it out
14:44 < c-tester> ok..
14:44 < c-tester> peter this is what the github doc says.
14:44 < c-tester> This opens a connection and, on top of that connection, then opens a channel. The funding transaction needs 1 confirmations in order for the channel to be usable, and 6 to be broadcast for others to use.
14:44 < peterm> ok i see
14:48 < c-tester> EBX, have you ever restarted your bitcoind or lightning instance while having channels open?  are they persistent?
14:48 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit []     
14:49 < ebx> yes -- I usually shut down, pull in the latest changes every day or so and rebuild, and then relaunch
14:49 < ebx> haven't noticed any ill effects from it yet
14:49 < c-tester> nice.. good to know..
14:50 < c-tester> and for the latest updates..  you do sudo apt-get command?
14:50 < ebx> `git pull`, `make clean; make`
14:50 < c-tester> ok thx.
14:51 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has quit [Remote host closed the connection]     
14:52 -!- vitaminc_ [~vitaminc@192.5.151.254] has joined #c-lightning     
14:55 -!- vitaminc [~vitaminc@192.5.151.254] has joined #c-lightning     
14:56 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has joined #c-lightning     
14:57 < peterm> What decides how much fee you use when setting up a channel?
14:58 < c-tester> not sure
15:01 < c-tester> if there is a fee to establish one...  I know you can earn fees if you relay a payment...
15:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]     
15:03 < peterm> Hey tester
15:03 < c-tester> hey     
15:03 < peterm> I need to go getting late
15:03 < peterm> thanx again for helping me out
15:03 < c-tester> same.. dinner time here..
15:04 < peterm> bye     
15:04 < c-tester> np... ill  be later.. good luck
15:04 < peterm> ok     
15:04 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has quit [Quit: Page closed]     
15:07 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Ping timeout: 255 seconds]     
15:09 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #c-lightning     
15:17 < alexann> little help please,  runnung bitcoind (with docker) looks ok, but with lightning i get "ightning_gossipd(14): TRACE: Failed to bind on 2 socket: Address already in use" . What's the trick here?? 
15:18 < alexann> netstat shows me that ports 9735 and 833 are used by docker-proxy
15:18 < alexann> i have used this command: 
15:18 < alexann> 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 cdecker/lightningd:master --network=bitcoin --log-level=debug
15:19 < alexann> is there anything particular maybe that should be put in bitcoin.conf? 
15:20 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
15:20 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Client Quit]     
15:20 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning     
15:21 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Client Quit]     
15:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
15:54 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
16:00 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Quit: Leaving]     
16:01 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has joined #c-lightning     
16:01 -!- jojeyh [~delphi@2602:306:b8b6:b970:21d0:4d4c:1b4b:b54c] has quit [Ping timeout: 276 seconds]     
16:02 < redstorm> htlc 0 failed from 0th node with code 0x400a (WIRE_UNKNOWN_NEXT_PEER)
16:03 < redstorm> assume no route to destination?
16:04 < redstorm> "failed: WIRE_UNKNOWN_NEXT_PEER (reply from remote)"
16:04 < redstorm> this was trying to send a payment to starblocks. Sending 1711189 over 4 hops to deliver 1700000
16:04 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds]     
16:14 -githubby:#c-lightning- [lightning] rustyrussell pushed 2 new commits to master: https://git.io/vN6EJ
16:14 -githubby:#c-lightning- lightning/master 9588c96 Christian Decker: wallet: Forget channels that are irrevocably settled on-chain...
16:14 -githubby:#c-lightning- lightning/master 7b0d806 Christian Decker: pytest: Check that we forget irrevocably settled channels...
16:16 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vN6Em
16:16 -githubby:#c-lightning- lightning/master 0557467 practicalswift: Adjust log level for feerate warnings...
16:16 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vN6EY
16:16 -githubby:#c-lightning- lightning/master 3a8220d practicalswift: Warn instead of crash when extract_feerate(...) fails...
16:16 -!- PockeT [4da2683e@gateway/web/freenode/ip.77.162.104.62] has quit [Quit: Page closed]     
16:22 < truk_> Any idea on how to get your lightning node updated so it displays the URI ?
16:26 < truk_> @redstorm, I'm having the same issue, however, Looks like the just merged the fix. 
16:26 < lugg_> I'm wondering the same
16:26 < lugg_> --uri= doesn't seem to work
16:29 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #762: Onboarding: Adjust log level for common non-fatal peer state condition from info to debug (master...adjust-loglevel-to-avoid-console-spam) https://git.io/vNKFb
16:29 -!- mlz [~IRCIdent@unaffiliated/molly] has quit [Ping timeout: 265 seconds]     
16:34 -!- mlz [~IRCIdent@unaffiliated/molly] has joined #c-lightning     
16:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds]     
16:40 < redstorm> @truk thanks, 
16:42 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
16:44 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Client Quit]     
16:54 < redstorm> Just pulled the latest source, now my channel is marked active both directions with my peer and public true, but the payment still fails.
16:55 -!- aproc [~aproc@2605:6000:e503:8300:5988:360b:d899:4044] has quit [Quit: Leaving]     
16:59 < truk_> Yeah, I was able to make a 1000sat payment but I get (WIRE_TEMPORARY_CHANNEL_FAILURE: Capacity exceeded) when sending larger funds
17:15 < lugg_> truk_: I was stuck there too, and decided to close my channel
17:15 < lugg_> now I have to wait 24 hours heh
17:16 < redstorm> Might try another channel peer, the one im with has no route to destination. even though it works out 4 hops and the fee requried.
17:17 < redstorm> any recomendations for a well connected channel partner?
17:18 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
17:23 -!- mdrollette [~mdrollett@feynman.drollette.com] has quit [Quit: ZNC 1.6.5 - http://znc.in]     
17:23 -!- mdrollette [~mdrollett@feynman.drollette.com] has joined #c-lightning     
17:37 -!- aproc [~aproc@2605:6000:e503:8300:29d1:398a:3421:bdfb] has joined #c-lightning     
17:39 < aproc> I switched my node from testnet to mainnet, but when i listfunds it's still listing the testnet funds as if they were accessible
17:47 < aproc> is there a way i can clear the funds/peers from testnet?
17:49 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 240 seconds]     
17:52 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
17:52 < lugg_> aproc: hurry, spend them before anyone noticed!
17:53 < aproc> lol     
17:59 -!- truk_ [~truk@76-227-238-58.lightspeed.frsctx.sbcglobal.net] has quit [Remote host closed the connection]     
18:04 -!- jojeyh [~delphi@2602:306:b8b6:b970:54f6:f913:b30f:722e] has joined #c-lightning     
18:17 < redstorm> Q: Peer permanent failure in ONCHAIND_MUTUAL: Funding transaction spent
18:17 < redstorm> cant close channel
18:18 -!- Alex_ [~Alex@46.217.155.153] has joined #c-lightning     
18:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
18:21 < danielh> redstorm: same issue
18:21 -!- alexann [~Alex@46.217.155.153] has quit [Ping timeout: 264 seconds]     
18:23 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds]     
18:26 < danielh> not sure if we have to wait 40 days..
18:27 < danielh> Thus if A closes the channel by signing and broadcasting its commitment
18:27 < danielh>  transaction, B can collect its output immediately, but A must wait 40 days.
18:29 < rusty> danielh: 1 day is the default for c-lightning, but the delay for A is set by B, and we let them set up to 3 days (3 * 6 * 24 blocks)
18:30 < danielh> ah     
18:30 < danielh> but this seems to be the issue then?
18:32 < rusty> danielh: do you have a channel in ONCHAIN_OUR_UNILATERAL state?
18:33 < danielh> no they are in ONCHAIND_MUTUAL after closing the channels
18:33 < rusty> (Sorry, at a conference, so my connectivity is intermittant).
18:33 < rusty> danielh: then your funds should already be in your wallet?  listfunds...
18:33 < danielh> which then makes me unable to reconnect them
18:33 < danielh> they are
18:33 < rusty> danielh: oh,  yeah, that :(
18:34 < danielh> I wanted to increase capacity of some channels
18:36 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
18:39 -!- fred_ [dcef66bc@gateway/web/freenode/ip.220.239.102.188] has joined #c-lightning     
18:39 -!- fred_ is now known as Guest70150     
18:39 -!- Guest70150 [dcef66bc@gateway/web/freenode/ip.220.239.102.188] has quit [Client Quit]     
18:41 < rusty> danielh: yeah, known issue.  Trying to find PR now, I'm sure we had one open/
18:41 < danielh> ah ok
18:43 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 268 seconds]     
18:45 < lugg_> oh hey it's rusty!
18:45 < lugg_> anyone know what the ONCHAIND_OUR_UNILATERAL state means?
18:48 -!- mn3monic [~xxwa@host82-204-dynamic.49-79-r.retail.telecomitalia.it] has joined #c-lightning     
18:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]     
18:50 < mlz> you tried to send a message after the channel was unilaterally closed  ?
18:53 < lugg_> mlz: I see it in the status when I do listpeers
18:53 < lugg_> I did close the channel, but my funds didn't come back...
18:56 < jb55> local unilateral closes are timelocked, you just have to wait
18:56 < lugg_> ah ok
18:57 < mlz> jb55, for how long?
18:58 < jb55> 144 blocks I believe
18:58 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has joined #c-lightning     
19:02 < jb55> only 6 on testnet
19:02 < c-tester> any ideas on how to refill a channel off-chain
19:03 < jb55> lol https://jb55.com/s/cf41b512c45a8ae6.png
19:14 < jb55> you had one job closingd https://jb55.com/s/2737f8f621bf9dec.txt ONE JOB
19:18 < jb55> maybe not its fault. I was too harsh I apologize.
19:32 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-aictmwivytctoebf] has quit [Quit: Connection closed for inactivity]     
19:35 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 264 seconds]     
19:37 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
19:53 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 240 seconds]     
19:53 < windsok> I have one channel in CLOSINGD_SIGEXCHANGE state -- does that mean someone went wrong during the closing?
19:54 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
20:03 -!- ebx [~ebx@12.226.6.52] has quit [Ping timeout: 240 seconds]     
20:03 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
20:05 < windsok> I also have 2 channels in CHANNELD_AWAITING_LOCKIN state, where the funding tx does not seem to actually exist as far as I can tell
20:06 < windsok> (these are channels people have tried to open with me)
20:10 -!- mlz [~IRCIdent@unaffiliated/molly] has quit [Ping timeout: 240 seconds]     
20:12 < jojeyh> windsok, how recently did you broadcast the funding tx?
20:12 < jojeyh> is it still in the mempool?
20:13 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
20:13 < windsok> I did not broadcast it, they tried to connect with me
20:13 -!- alexann [~Alex@79.125.252.208] has joined #c-lightning     
20:13 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has quit [Quit: Page closed]     
20:13 < windsok> looks like one of them is from tokensoft.io (0235447c7485ff2b945bac5fbc366d54a87389bab8cacf1b64b26ec01e96bd165a)
20:13 < windsok> apparent funding tx is c69098347cacb7abdba0991fc2a1c534f4a77b23b7961bcb3f995c87bc9af529
20:14 < windsok> but as far as I can tell, that tx has never been broadcast
20:15 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
20:15 -!- Alex_ [~Alex@46.217.155.153] has quit [Ping timeout: 248 seconds]     
20:16 -!- mlz [~IRCIdent@unaffiliated/molly] has joined #c-lightning     
20:17 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
20:17 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
20:19 < windsok> does c-lightning wait until it sees the tx in the mempool before switching to CHANNELD_AWAITING_LOCKIN, or does it trust that the peer will broadcast it?
20:19 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
20:20 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
20:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
20:26 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 252 seconds]     
20:31 < jojeyh> it will change to state CHANNELD_NORMAL after 1 conf of the funding tx
20:32 < jojeyh> looks like someone connected to your node but then didn't fund a channel
20:32 < jojeyh> so its "awaiting lockin"
20:32 -!- ebx [~ebx@12.226.6.52] has quit [Remote host closed the connection]     
20:32 -!- ebx [~ebx@12.226.6.52] has joined #c-lightning     
20:36 < jojeyh> i wouldn't worry about it if you aren't tryin gto open a channel with those peers directly
20:42 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-igrkulieriyritqa] has joined #c-lightning     
20:49 < windsok> thanks, I might try to contact tokensoft to see what went wrong on their end
20:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]     
20:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
21:12 -!- c-tester [ac618a6a@gateway/web/freenode/ip.172.97.138.106] has quit [Quit: Page closed]     
21:24 < ianthius> has anyone gotten their node that is stuck at a certain block height to move again?
21:33 < ossifrage> Any ideas how to get lightningd to work with .cookie instead of having the rpc auth in the bitcoin.conf?
21:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]     
21:45 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has joined #c-lightning     
21:45 < peterm> Hallo
21:46 < peterm> Want to send some payment, how do I get the bolt11 address?
21:57 < windsok> peterm: the person or service you want to send to should provide you with a bolt11 invoice
21:58 < peterm> yep got it
21:59 < peterm> any shops to try it out?
21:59 < peterm> only blockstream right?
22:01 < ianthius> peterm: i think torguard sells services, you contact their support for details.
22:18 -!- peterm [54c4bb2e@gateway/web/freenode/ip.84.196.187.46] has quit [Quit: Page closed]     
23:25 < jojeyh> ossifrage, i don't know but that sounds like a good side project :)
23:27 < ossifrage> jojeyh, I've always used the .cookie auth it seems much cleaner then putting the auth in the config file
23:28 < jojeyh> much cleaner, i'll see if i can figure it out
23:30 < ossifrage> What I can't quite understand is when lightningd runs bitcoin-cli it looks at the right config file, but fails with: bitcoin-cli exited with code 1: error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set.  See -rpcpassword and -stdinrpcpass.  Configuration file: (/path-to-my-non-standard-conf-file)
23:32 < jojeyh> did you select a network explicitly?
23:32 < jojeyh> i.e. 'lightningd --network testnet' ?
23:33 < jojeyh> it sounds like the network you are specifying isn't running 
23:58 < ossifrage> jojeyh, ah, doh... I didn't specify the network (I assumed it defaulted to mainnet, for the crazy)