--- Log opened Tue Jan 28 00:00:22 2020
01:24 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Quit: Leaving]
01:32 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Ping timeout: 268 seconds]
01:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
02:05 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has joined #c-lightning
02:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
02:39 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
02:45 < darosior> fiatjaf: python3 -c 'print("MPP") if 0x028200 & (1<<16 | 1<<17) else print("NO MPP")' :-)
02:45 < darosior> spoiler
02:45 < darosior> MPP
02:46 < darosior> https://github.com/lightningnetwork/lightning-rfc/blob/master/09-features.md
02:49 < darosior> r32a: Great, which one is it ?
03:08 -!- k3tan [~ketan@unaffiliated/k3tan] has quit [Ping timeout: 265 seconds]
03:11 -!- k3tan [~ketan@unaffiliated/k3tan] has joined #c-lightning
03:25 -!- k3tan [~ketan@unaffiliated/k3tan] has quit [Ping timeout: 265 seconds]
03:29 -!- k3tan [~ketan@unaffiliated/k3tan] has joined #c-lightning
03:37 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has quit [Ping timeout: 260 seconds]
03:38 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
03:42 -!- k3tan [~ketan@unaffiliated/k3tan] has quit [Ping timeout: 240 seconds]
03:43 -!- k3tan [~ketan@unaffiliated/k3tan] has joined #c-lightning
03:46 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Ping timeout: 240 seconds]
03:47 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
03:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
03:48 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
03:58 -!- orlovsky [~dr-orlovs@194.230.147.90] has joined #c-lightning
04:00 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Ping timeout: 272 seconds]
05:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode]
05:06 -!- treehug88 [~textual@pool-173-56-90-115.nycmny.fios.verizon.net] has joined #c-lightning
05:06 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:48 -!- xi27pox [b96e6ecd@185.110.110.205] has joined #c-lightning
05:48 < xi27pox> which iOS mobile wallets support connecting to c-lightning through tor?
05:49 -!- orlovsky [~dr-orlovs@194.230.147.90] has quit [Read error: Connection reset by peer]
05:49 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has joined #c-lightning
05:51 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has quit [Read error: Connection reset by peer]
05:52 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has joined #c-lightning
06:14 < darosior> Can you run a Tor proxy on iOS ?
06:21 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has quit [Read error: Connection reset by peer]
06:22 -!- orlovsky [~dr-orlovs@194.230.147.90] has joined #c-lightning
06:32 < xi27pox> good question. let me find out.
06:34 < xi27pox> yes.
06:59 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
07:01 -!- justanotheruser is now known as FeudalBear
07:49 -!- xi27pox [b96e6ecd@185.110.110.205] has quit [Remote host closed the connection]
08:46 -!- moneyball [sid299869@gateway/web/irccloud.com/x-ovnazfnmowvbxxke] has quit []
08:46 -!- moneyball [sid299869@gateway/web/irccloud.com/x-nygdhnfgbmhpblqo] has joined #c-lightning
08:48 < darosior> Ok, I would've bet you cannot ^^
08:48 < darosior> Unfortunately I think  the appstore listing price is a restriction to open source remote controls..
08:53 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-ychgpeigdrmerrwf] has quit []
08:54 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-bwhyuyenhxtslndx] has joined #c-lightning
09:02 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
09:05 -!- orlovsky [~dr-orlovs@194.230.147.90] has quit [Ping timeout: 268 seconds]
09:14 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz...]
09:17 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has joined #c-lightning
09:23 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined #c-lightning
09:26 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has quit [Ping timeout: 265 seconds]
11:14 < vasild> The sporadic test failures on travis (even if the patch is healthy) are very nasty.
11:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
11:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
11:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
12:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
12:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
12:38 <@cdecker> vasild_: yep, the flaky tests are rather annoying. Usually I spend a couple of hours to stabilize them every once in a while, but they tend to accumulate when I dont get around to do it for a while
12:39 < vasild_> cdecker: you mean new flaky tests being added?
12:39 -!- vasild_ is now known as vd
12:39 -!- vd is now known as vasild
12:45 <@cdecker> That and slight behavior changes can cause flaky tests further down the line, it's the cost of doing business I guess :-)
12:46 -!- FeudalBear is now known as justanotheruser
12:47 < vasild> Yes :/ there is no good solution to nondeterministically failing tests. One way to mitigate that is to collect stats from test runs and keep records which test is unstable, so that at least when it fails on your PR you know immediately that it is not the PR's fault (or at least that it was broken before the PR, maybe the PR broke it even more).
15:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:50 < fiatjaf> how can I get mrkd on freebsd?
16:51 < fiatjaf> nevermind
17:13 -!- kristapsk_ is now known as kristapsk
17:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
17:54 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
17:55 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
17:55 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
17:55 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
17:55 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
18:00 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
18:15 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
18:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:49 < fiatjaf> how can I decrypt the next_onion on htlc_accepted?
18:50 < fiatjaf> considering that I have the private key of the next node
18:50 < fiatjaf> I have no experience in these things, but I suppose I have to decrypt some shared secret, where is the shared secret
18:50 < fiatjaf> nevermind, I think I should read the relevant BOLT
18:51 < zmnscpxj> devtools/ directory has a devtools/onion.c, maybe that is relevant
18:51 < zmnscpxj> not sure though --- did not write it
18:51 < zmnscpxj> mostly cdecker and rusty
18:51 < zmnscpxj> In theory devtools/onion decode ${FILE} ${PRIVKEY}
18:52 < zmnscpxj> you could try it first before going to read the BOLT and implement it yourself
19:09 < fiatjaf> thank you
19:09 < fiatjaf> that was helpful
19:10 < fiatjaf> however I got a "onion: Error processing message."
19:10 < fiatjaf> I think the onion hex htlc_accepted gives me is not the full onion?
19:10 < fiatjaf> wait, it is
19:12 < zmnscpxj> I think devtools/onion wants it in binary in a file
19:13 < fiatjaf> no, it wants hex
19:13 < fiatjaf> I tried binary first
19:13 < zmnscpxj> hmmm
19:13 < fiatjaf> it said "onion: Invalid onion hex ''"
19:14 < fiatjaf> if I give an invalid private key I get the same "error processing message"
19:14 < zmnscpxj> Yes it wants hex, sorry
19:14 < fiatjaf> that private key is the node's private key, right?
19:15 < zmnscpxj> of the next hop I think yes
19:17 < fiatjaf> yes
19:17 < zmnscpxj> hmm from htlc_accepted I guess from this node then
19:17 < fiatjaf> but I'm taking the "next_onion" field
19:17 < zmnscpxj> ah
19:18 < zmnscpxj> yes we already decoded our own onion at that point, sorry
19:20 < zmnscpxj> sorry, do not know at this point
19:22 < fiatjaf> thank you
19:22 < rusty> fiatjaf: that tools lacks decent diagnostics.
19:22 < rusty> fiatjaf: but it managed to get a shared secret, then process_onionpacket got upset.
19:23 < rusty> fiatjaf: I would gdb and break process_onionpacket
19:25 < fiatjaf> thank you, I'll try that tomorrow then]
21:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
21:19 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
21:19 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
21:38 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
21:38 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
22:29 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
23:13 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has quit [Ping timeout: 246 seconds]
23:16 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
23:17 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
23:40 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
23:41 < PaulTroon> Has anyone tried to cross-compile to Android from an OSX machine? I've got QEMU installed, but it's not clear if qemu-user is something that works on OSX.
23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
23:45 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
--- Log closed Wed Jan 29 00:00:23 2020