--- Log opened Mon Oct 08 00:00:31 2018 00:11 < blockstream_bot> [Christian Decker, Blockstream] spinza, probably the remote end not sending a channel depth confirmation. Might be out of sync, or just broken. Do you have an idea what the remote end might be running? 00:39 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning 01:29 < t0mix> blockstream_bot, thank you 02:18 -!- Victor_sueca is now known as Victorsueca 02:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:21 -!- mn3monic_ [jsz@unaffiliated/mn3monic] has joined #c-lightning 02:22 -!- mn3monic_ is now known as mn3monic 03:54 -!- deusexbeer [~deusexbee@080-250-075-064-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 04:05 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 04:08 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 04:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds] 05:13 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:14 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: Textual IRC Client: www.textualapp.com] 05:17 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode] 05:19 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 05:22 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 05:41 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Remote host closed the connection] 05:41 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning 06:19 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Quit: farmerwampum] 06:19 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 06:23 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Client Quit] 06:24 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 06:59 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [] 07:59 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Quit: farmerwampum] 07:59 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 08:03 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Client Quit] 08:04 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 08:05 -!- tweeeaks [~tweeeaks@unaffiliated/tweeeaks] has joined #c-lightning 08:07 < molz> I have a tx with "status": "pending", Will this tx go to "failed" eventually because the invoice has expired? 08:08 -!- tweeeaks is now known as tweaks 08:25 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving] 08:50 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 09:58 <@cdecker> molz: is this a payment or an invoice? Tx usually refers to on-chain transfers (and can therefore not expire) 09:58 <@cdecker> Invoices do expires after the timeout 09:59 < molz> cdecker, i tried to pay an invoice but evidently there was no liquidity/no route so my tx went into "pending" and the invoice expired in 10 min 10:00 < molz> here's some info: { "code" : 200, "message" : "Stopped retrying during payment attempt; continue monitoring with pay or listpayments", "data" : 10:00 < molz> "getroute_tries": 3, 10:00 < molz> "sendpay_tries": 3, 10:00 < molz> "status": "pending", 10:01 < molz> so i keep checking "listpayments" and it's still in "pending" 10:02 <@cdecker> Yeah, that'll stay pending indefinitely for now, we need to sweep through and mark them as failed once we know we can't continue to try 10:03 < molz> cdecker, do you know how long it takes? 10:03 <@cdecker> How long what takes? 10:04 < molz> what i mean is: is my coin amount stuck in the channel that failed? and i need to wait for a while? 10:05 <@cdecker> Nope, the funds should be back under your control 10:05 < molz> oh really.. but what about the message "status": "pending" in "listpayments"? will it change? 10:05 <@cdecker> Here's the code that causes the above error message: https://github.com/ElementsProject/lightning/blob/ca40cfa0cebd3a6d27eebfdc457eee1fee037f16/lightningd/payalgo.c#L576-L597 10:06 <@cdecker> It's basically saying "my retry timer expired but there might still be one last chance to get it through" 10:06 <@cdecker> Oh, it might still be hanging on the last HTLC, that is not cleared 10:07 < molz> yea that's what i'm wondering about 10:08 <@cdecker> `listpeers` recently got the ability to list in-flight HTLCs, do you have an `htlcs` key in its output? 10:08 < molz> cdecker, for LND it would tell us which channel where it's stuck and at what blockheight the htlc would be cleared 10:08 < molz> hold on 10:09 <@cdecker> Same thing we do here: https://github.com/ElementsProject/lightning/blob/9455331575b56718a289ea200395d864683568e3/lightningd/peer_control.c#L611-L647 10:09 <@cdecker> (added 12 days ago, so really recent) 10:10 < molz> cdecker, ah i don't have it 10:10 < molz> my node is on v0.6.1 release 10:11 <@cdecker> Hm, yeah that won't include that info yet 10:11 <@cdecker> You could always grab that info from the DB 10:14 < molz> cdecker, how do you grab the info? 10:14 <@cdecker> This might help: `sqlite3 ~/.lightning/lightningd.sqlite3 "select channel_id, direction, msatoshi, cltv_expiry, HEX(payment_hash), hstate from channel_htlcs WHERE payment_key IS NULL"` 10:15 <@cdecker> Not sure if it contains all necessary fields to debug 10:15 <@cdecker> But it should spit out stuck HTLCs (payment_key is null) 10:46 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 10:46 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 10:51 < molz> cdecker, i guess im not doing it right, it doesn't spit out anything except ...> 10:52 < molz> but im guessing it would take about 3 days, i'll just wait 10:55 < molz> hm if i update the node to master, will it show the stuck htlc? 10:57 <@cdecker> It should yes 10:58 <@cdecker> And not having any output is good here, that means there is no stuck HTLCs (if my query is correct that is) 10:59 < molz> oh really.. :) 10:59 < molz> ok let me pull the master and we'll see 11:04 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Quit: farmerwampum] 11:04 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 11:08 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Client Quit] 11:09 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 11:19 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Quit: farmerwampum] 11:19 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 11:23 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Client Quit] 11:24 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 11:28 < molz> cdecker, cool, this is much better, it shows: "expiry": 545493, 11:29 < molz> so it'll be unstuck in 4 days, i'll just wait 11:29 < molz> "state": "SENT_ADD_ACK_REVOCATION" 11:39 <@cdecker> Ok, strange it didn't show up in the sqlite3 query though 11:44 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Quit: farmerwampum] 11:44 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 11:48 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Client Quit] 11:49 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 12:15 < molz> cdecker, i didn't understand this part so i didn't put in the sqlite3 query: "hstate from channel_htlcs" 12:33 < spinza> cdecker, no idea. all i can see is localfeatures 8082 if that means anything. 12:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:15 <@cdecker> molz: that part is actually telling the query from which table to grab the info, so that's important 13:18 < molz> cdecker, but where do you find it? 13:45 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has quit [Remote host closed the connection] 14:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 268 seconds] 14:21 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning 15:07 -!- deusexbeer [~deusexbee@080-250-075-064-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 15:12 <@cdecker> Mh? That whole command should spit out a number of lines, each with an HTLC 15:33 < jb55> cdecker: what do you think of having an eltoo testnet or would that be too early 15:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:56 < molz> is there a way to set tx fee when sending an onchain tx? 15:57 < molz> cdecker, i misunderstood then because i tried to fill in those fields with chan_id, etc.. but i tried again and it spit out a bunch of block info or something 15:57 < molz> but anyways, it's better now that i can see the info of this stuck htlc in 'listpeers' 16:23 < molz> cdecker, i wish you guys change the way funds are listed to be in satoshi and not msatoshi, to make it easier for reading 16:25 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 16:36 < jb55> molz: that's on ongoing debate about consistency. I think the consensus is to make everything msat as much as possible. The main reason is that clightning is most likely going to be a more low level tool called out to by higher level libraries and applications. Consistency is more important than human usability in those cases. 16:41 -!- deusexbeer [~deusexbee@080-250-075-064-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 16:47 < molz> jb55, so are you saying i shouldn't use it to pay satoshis.place? 16:47 < jb55> molz: hmm? not sure what you mean. 17:59 -!- Nebraskka [~Nebraskka@178.62.130.190] has quit [Ping timeout: 246 seconds] 18:00 -!- Nebraskka [~Nebraskka@178.62.130.190] has joined #c-lightning 18:51 < rusty> jb55: yeah, but the transition is going to be immensely painful, unfortuntely :( 18:52 < rusty> molz: funds need to be in msatoshi unless we truncate or start adding decimal points (neither appeals...) 18:53 < jb55> rusty: hey is an eltoo testnet on anyone's horizon? or is that still far away? 18:53 < molz> rusty, but don't you think they're confusing for most people ? plus this is a new tech, even more difficult for them 18:54 < rusty> jb55: not yet... 18:54 < jb55> just need to clone you shouldn't be that hard 18:55 < molz> rusty, only funds are in msatoshi in c-lightning, not in the other impls 18:57 < aj> rusty: eltoo signed blocked testnet? :) 18:58 < rusty> molz: yeah, originally all the lnd stuff was out by 1000 because they didn't support it. How would they handle a satoshihalfplace which cost 500 msat? 18:59 < molz> rusty, lnd has msat in handling fees, not in funds 18:59 < rusty> molz: so if you pay half a satoshi, how much funds do you have? 18:59 < molz> i can use lnd to pay you half satoshi 19:00 < jb55> 0.5? :P 19:00 < molz> but i can't create an invoice for half satoshi with lnd 19:00 < molz> because funds are in sat 19:00 < rusty> molz: but you said they display funds in satoshi? 19:00 < molz> yes 19:00 < rusty> molz: right, so if you have 1000 satoshi and pay me 0.5, you have.... 999? 19:01 < molz> i probably have 0 idk, you have to ask roasbeef 19:01 < rusty> molz: well, this is why we're headed to msat everywhere. It's the minimal unit of lightning, and so to makes sense... 19:02 < jb55> and there's bcalc for everything else /shill 19:10 < molz> jb55, i have your bcalc installed :P 19:11 < molz> but i haven't used it, something is missing 19:11 < jb55> ? 19:11 < molz> can't remember now why i downloaded it but found out i couldn't use it 19:14 < jb55> yeah I haven't really packaged it yet 19:25 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.2] 19:28 < molz> rusty, also, we don't use msat onchain, it's not used practically anywhere and we don't even know if it will ever be used, what do you think about it? 19:28 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 20:12 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection] 20:12 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 20:30 < jb55> life of a c-lightning user https://i.imgflip.com/2jp72c.jpg 20:31 < jb55> much harder to get others to connect to you when only a single channel is allowed ;_; 20:43 < rusty> jb55: splicing FTW... 20:45 < jb55> is there a bolt for that 20:45 < rusty> jb55: not yet, but as we're the ones most eager for it, I expect there will be before November... looks at cdecker... 20:48 < roasbeef> i haz some partially fin code ;) 20:49 < roasbeef> and splicing doesn't address inbound capacity issues really 20:52 < jb55> I think dual channels would be more helpful for inbound capacity issues. then negotiation would be simpler instead of me opening and channel and then hoping they connect back by splicing in later or something 20:52 < jb55> if that makes sense 21:04 < roasbeef> jb55: nah it's really an out of band thing imo 21:04 < roasbeef> doesn't address incentive issues 21:08 < rusty> roasbeef: yeah, I expect some people will set up their nodes to contribute 10% to any incoming channels if we had dual-funding; I would. 21:47 < jb55> /join #bitcoin-workshops 21:47 < jb55> oops 22:09 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 22:42 < niftynei> rusty if we publish a `htlc_maximum_msat` for a c-lightning node, do we actually care if an incoming htlc exceeds our indicated max? 22:44 < niftynei> the spec doesn't specify the behavior of the node advertizing the `htlc_maximum_msat` in this case 22:48 < niftynei> relevant: as is, there's no corresponding routing error code to signal that that's why your payment failed 22:54 < niftynei> nvm. i think i just talked myself into ignoring it when deciding to accept htlc's 22:54 < niftynei> i really gotta get over this desire to treat it as more than a 'routing aid' 22:58 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 268 seconds] 23:30 < rusty> niftynei: yes :) 23:31 < rusty> niftynei: 'temporary_channel_failure' means "something went wrong", including insufficient capacity, too many htlcs, other side offline... it's deliberately vague. 23:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds] 23:59 -!- thorie [~thorie@107-131-122-22.lightspeed.sntcca.sbcglobal.net] has joined #c-lightning 23:59 < thorie> howdy, folks :) can someone help me with my channel? it seems to be stuck --- Log closed Tue Oct 09 00:00:32 2018