--- Log opened Wed Jan 27 00:00:27 2021 00:21 -!- lio17 [~lio17@80.ip-145-239-89.eu] has quit [Ping timeout: 256 seconds] 00:47 -!- lio17 [~lio17@80.ip-145-239-89.eu] has joined #c-lightning 00:50 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 01:23 -!- earnestly [~earnestly@unaffiliated/earnestly] has joined #c-lightning 02:00 -!- belcher_ is now known as belcher 02:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 02:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 02:26 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 02:26 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 02:26 -!- vasild_ is now known as vasild 02:55 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 03:23 -!- sr_gi [~sr_gi@static-6-109-229-77.ipcom.comunitel.net] has joined #c-lightning 04:01 < m-schmoock> cdecker: chained another hook: https://github.com/ElementsProject/lightning/pull/4358 04:01 < m-schmoock> custommsg 04:01 < m-schmoock> now only rpc_command hook is left as single hook 04:55 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 264 seconds] 05:07 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 05:53 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 268 seconds] 06:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 06:04 -!- earnestly [~earnestly@unaffiliated/earnestly] has quit [Ping timeout: 256 seconds] 07:14 <@cdecker> Great, thanks m-schmoock :+1: 07:36 < m-schmoock> I will also make rpc_command hook chainable just to have them all. In this case different plugins can hook different rpc commands. If two plugins try to replace/return/error the same rpc command, the first plugin in the chain will win 07:55 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has left #c-lightning [] 07:55 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has joined #c-lightning 08:07 -!- kexkey [~kexkey@static-198-54-132-152.cust.tzulo.com] has joined #c-lightning 08:37 -!- Galvas [sid459296@gateway/web/irccloud.com/x-bwbwszkdaytmfgex] has quit [Read error: Connection reset by peer] 08:37 -!- felixweis [sid154231@gateway/web/irccloud.com/x-mdptrwlrtlphtxkd] has quit [Ping timeout: 264 seconds] 08:38 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-uzigebtuljkhnqcp] has quit [Read error: Connection reset by peer] 08:38 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-xiafkyvtjtuehoop] has quit [Read error: Connection reset by peer] 08:38 -!- fjahr [sid374480@gateway/web/irccloud.com/x-wkigcsbdradvztsy] has quit [Read error: Connection reset by peer] 08:38 -!- Letze [sid63391@gateway/web/irccloud.com/x-ukqqpctwqpwdujzv] has quit [Read error: Connection reset by peer] 08:42 -!- Galvas [sid459296@gateway/web/irccloud.com/x-oxwszmwkhmipkqtn] has joined #c-lightning 08:42 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-jdprefwyhgpusmtg] has joined #c-lightning 08:43 -!- fjahr [sid374480@gateway/web/irccloud.com/x-rcvxpwznmxtiozvi] has joined #c-lightning 08:44 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-ukeiamoftqdxfbvz] has joined #c-lightning 08:45 -!- felixweis [sid154231@gateway/web/irccloud.com/x-smefinmvkaltzcwo] has joined #c-lightning 08:56 -!- Letze [sid63391@gateway/web/irccloud.com/x-zxmxzwnmnhicyyag] has joined #c-lightning 09:57 -!- kexkey [~kexkey@static-198-54-132-152.cust.tzulo.com] has quit [Read error: Connection reset by peer] 10:31 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Remote host closed the connection] 10:31 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 10:31 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection] 10:32 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 11:10 < HelloShitty> m-schmoock: do you know what might am I missing to get this message: 2021-01-27T18:15:31.938Z UNUSUAL plugin-summary.py: [PriceThread] Missing dependencies for SOCKS support. 11:43 -!- sr_gi [~sr_gi@static-6-109-229-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 11:44 -!- sr_gi [~sr_gi@static-6-109-229-77.ipcom.comunitel.net] has joined #c-lightning 12:00 -!- kexkey [~kexkey@static-198-54-132-152.cust.tzulo.com] has joined #c-lightning 12:08 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 12:08 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 12:24 <@cdecker> You probably need pysocks to be able to retrieve the exchange rates over Tor. It should fall back to cleartext without it 14:24 < HelloShitty> cdecker: thank you... After installing pysocks with 'pip3 install pysocks' I see now this error message: 14:24 < HelloShitty> 2021-01-27T22:23:36.005Z UNUSUAL plugin-summary.py: [PriceThread] Expecting value: line 1 column 1 (char 0) 14:25 < HelloShitty> well, it's not an error message, but is it ok (or expected)? 14:26 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 14:26 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 14:26 -!- vasild_ is now known as vasild 15:52 -!- grubles [~unknown@unaffiliated/grubles] has joined #c-lightning 15:53 < grubles> what would be causing WIRE_INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS in a simple 2-node LN setup? 15:53 < grubles> using getroute and sendpay 15:54 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has left #c-lightning ["my computer exploded"] 16:09 < HelloShitty> grubles: 16:13 < HelloShitty> forget it 16:13 < HelloShitty> :( 16:16 < grubles> ? 16:18 < HelloShitty> I was looking into the code 16:18 < HelloShitty> and I thought I found something 16:18 < HelloShitty> but I guess not 16:18 < HelloShitty> But now I found a comment about that message 16:19 < HelloShitty> but I think it's a special case for that message 16:20 < HelloShitty> https://github.com/ElementsProject/lightning/blob/6bed85bac2e2dfa41bec39dea2ed2c2f4c5cc821/plugins/pay.c#L453 16:20 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has left #c-lightning [] 16:20 < darosior> grubles: it's sent when the payer didn't respect the payee's requested parameters (cltv etc). We had an issue when the payee's block height differed from the payer's one in the past but this should be fixed. 16:20 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has joined #c-lightning 16:21 < darosior> Yeah, the comment HelloShitty linked explains the fix 16:21 < darosior> Oh but you are using sendpay :) 16:21 < grubles> yeah 16:21 < darosior> Then you are probably generating blocks too quickly in your setup 16:22 < darosior> And the recipient thinks that you violated his request for minimum cltv 16:22 < grubles> i have a little python script (using pylightning) that creates an invoice on one node, and the 2nd node pays the invoice with sendpay 16:22 < grubles> so just to throw another curveball into this, i'm running lightningd with --network liquid 16:22 < grubles> so blocks will be generated every 1 minute 16:25 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 260 seconds] 16:26 < darosior> 1 minute seems reasonable, you could sanity check that both lightningd are at the same blockheight before the payment with a call to getinfo 16:26 < grubles> strangely using `pay` works fine 16:26 < darosior> Otherwise, the only remaining cause would be the payment hash 16:27 < darosior> Then you may be running into this block height issue 16:51 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 16:54 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 18:20 -!- liberliver1 [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 18:21 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Read error: Connection reset by peer] 18:21 -!- kexkey [~kexkey@static-198-54-132-152.cust.tzulo.com] has quit [Read error: Connection reset by peer] 18:21 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-jdprefwyhgpusmtg] has quit [Ping timeout: 256 seconds] 18:21 -!- liberliver1 is now known as liberliver 18:22 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 18:22 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-sulwoxgyopxoqgnl] has joined #c-lightning 19:20 -!- kexkey [~kexkey@static-198-54-132-152.cust.tzulo.com] has joined #c-lightning 19:27 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 20:31 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 21:00 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 21:02 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 21:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 21:22 < az0re> What does this message mean? 21:22 < az0re> Attempt to send HTLC but unowned (CHANNELD_NORMAL) 21:24 < az0re> (preceded by the pubkey of a channel peer) 21:25 < az0re> Something funky going on with my peer's channel state? Maybe they turned their node off during an HTLC forward and then turned it back on? 21:25 < az0re> Or is someone routing garbage (or exploits) to my node, reaching me through that channel peer? 21:26 < zmnscpxj> the peer is disconnected I think? If my memory serves 21:27 < zmnscpxj> normally if the peer is connected *some* daemon "owns" the connection 21:37 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 21:40 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds] 21:41 < az0re> Oh, I see 21:41 < az0re> It's that sense of ownership 21:42 < az0re> So basically someone just tried to forward a payment through my node to that offline peer? 22:49 -!- kexkey [~kexkey@static-198-54-132-152.cust.tzulo.com] has quit [Read error: Connection reset by peer] 23:57 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #c-lightning 23:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 268 seconds] --- Log closed Thu Jan 28 00:00:28 2021