--- Log opened Fri Oct 09 00:00:41 2020 00:35 -!- jonatack [~jon@213.152.162.99] has joined #c-lightning 00:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 00:44 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 01:54 -!- fiatjaf [~fiatjaf@179.180.231.131] has quit [Ping timeout: 256 seconds] 02:04 -!- kexkey [~kexkey@37.120.205.214] has quit [Ping timeout: 240 seconds] 02:27 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 02:44 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving] 02:46 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 02:47 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 03:05 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 03:08 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 03:55 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 04:06 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 04:07 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 04:09 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 04:30 -!- vincenzopalazzo [~vincent@mob-109-119-23-10.net.vodafone.it] has joined #c-lightning 04:30 -!- jonatack [~jon@213.152.162.99] has quit [Ping timeout: 258 seconds] 04:53 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 04:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:07 -!- jasan [~jasan@2001:470:6f:200:ec29:2c49:5710:ccb6] has joined #c-lightning 05:08 < jasan> Hello there! 05:09 < vincenzopalazzo> Hello :) 05:10 < jasan> I haven't been here today so maybe you mentioned it already but there is this https://lists.linuxfoundation.org/pipermail/lightning-dev/2020-October/002819.html 05:10 < jasan> (Partial LND Vulnerability Disclosure) 05:10 < jasan> anyone knows the details? 05:12 < jasan> I mean, some more public details. 05:17 <@cdecker> Details will be released on the 20th, if you have more information, please don't share it, respecting LL's timeline and protecting users that haven't upgraded their LND yet 05:18 < jasan> OK. Thank you. 05:19 < darosior> vincenzopalazz: thanks for being so reactive with my constant flow of issue tickets on Lamp :) https://github.com/lvaccaro/lamp/issues 05:21 < vincenzopalazzo> darosior: you choose a good moment to open an issue on lamp yesterday :-) I hope to finish the work at the end of this week :-) 05:22 < darosior> Sure, no worry it does not prevent usability. And i'm still lagging behind by 4 thousands blocks ^^ 05:23 < jasan> Wow! 05:23 < jasan> So https://github.com/lvaccaro/esplora_clnd_plugin is what I was looking for. 05:25 < vincenzopalazzo> darosior: I have the same situation on my "offical" lamp wallet :-) the solution on the "Found update" is so easy, I just check only the correct log line when the node receive some funds. Maybe you can help me without I need to run two node for this test :-) 05:25 < darosior> Sure, can test it once i have a minute 05:26 -!- sword_smith [sword_smit@bitcoinfundamentals.org] has joined #c-lightning 05:27 < vincenzopalazzo> jasan: Is so cool esplora plugin, however you need to customize your node instance, if you don't want to customize your lightnind node, you can try sauron https://github.com/lightningd/plugins/tree/master/sauron or btcli4j https://github.com/clightning4j/btcli4j 05:28 < vincenzopalazzo> darosior: Thanks, when I will start to test it I will ping you to don't make a double work :-) 05:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 05:52 < jasan> I have sixty minutes. But I know about lamp for less than an hour, so do not have it installed yet. 05:52 < jasan> vincenzopalazzo: How to install lamp on Android? Is Android 7.1.2 recent enough to install it? 05:58 < jasan> Ah! I have it. I was confused because I first downloaded the lightning_ndk and did not realize that's is just it. Now I found the apk in the Releases of lamp repo. 06:02 < vincenzopalazzo> jasan: We are working to release a new apk, if you have experience with android studio, you can install lamp from it, we have fix some "bug" in the last months 06:04 < jasan> Not much experience with android studio yet. And my machine was made in 2014. 4GB RAM. Will try installing Android Studio on Monday. 06:07 < vincenzopalazzo> jasan: Maybe you can try from the console to build the APK this is one reference https://developer.android.com/studio/build/building-cmdline 06:07 < jasan> OK, thanks for info. Noting that. 06:09 < vincenzopalazzo> :-) 06:10 < jasan> I smile back. No facemask. 06:10 < jasan> :-) 06:12 < jasan> vincenzopalazzo: A bit confused still. Does the release contain lightningd binary or is it looking for it in some PATH? 06:13 < jasan> I am on the latest APK release. And have the binaries from arm-linux-androideabi_bitcoin.tar.xz extracted in /storage/emulated/0/Downloads 06:14 < jasan> Download not s 06:15 < vincenzopalazzo> jasan: lamp download the lightnind binary and move the binary in the app directory and only after you can run the lightnind 06:15 < vincenzopalazzo> The application use the subprocess to run the command, is a pure lightnind code on android device 06:17 < jasan> when I press the lamp it does something for a while, then the screen blinks and lamp stays turned off 06:17 < jasan> nothing in the logs 06:17 < jasan> (I mean lamp picture stays gray after the screen blinks) 06:18 < vincenzopalazzo> This is why the app was old and somethings wrong are happening. I suggest you to update at the last master release, because we fix some UI problem and improve some connection with lightnind 06:19 < jasan> Ah, now it works. I have previously set IPv6 address into bind_address. 06:20 < jasan> My node is running. 02105f693d0090b8adf80b512c6a11cdcd25f87cdab525f07e3988d1dbd6495ce5@2001:470:6f:200:dc69:d3ab:4b01:1ce1 06:20 < vincenzopalazzo> Cool :-) sometimes you have some error with tor because at this moment some android wallet implement the own library to use tor, and this make some tor crash. Good play 06:20 < jasan> Yeah. Tor I have disabled. 06:20 < jasan> I am running a real tor on that host in Ubuntu chroot. 06:21 < jasan> (yes Android can run Ubuntu in a chroot) 06:21 < jasan> (it's a rooted Lineage Android) 06:23 < vincenzopalazzo> so, you know better than me what are happening :-) 06:25 < jasan> maybe 06:25 < jasan> but I always learn 06:25 < jasan> every day 06:25 < jasan> Today I learned about lamp :) 06:25 < jasan> vincenzopalazzo: kudos for lamp! 06:30 < jasan> vincenzopalazzo: one note: QR code seems to be generated every time the main screen is shown, any caching? 06:32 < jasan> Channel opening only from console yet? 06:34 < jasan> I just opened a channel from outside (thanks to quick blocks on testnet today it should be active soon). 06:35 < vincenzopalazzo> >one note: QR code seems to be generated every time the main screen is shown, any caching? 06:35 < vincenzopalazzo> Good feature :-) 06:35 < vincenzopalazzo> >Channel opening only from console yet? 06:36 < vincenzopalazzo> With the last version you can do all the main operation with the UI 06:36 < jasan> vincenzopalazzo: I just filed an issue for QR code caching. 06:36 < jasan> Ah. Nice. 06:37 < jasan> So I will have a look at the last version (at compiling it) next week. 06:37 < jasan> All the best so far! 06:37 < jasan> And keep smiling! :) 06:38 < jasan> Have a nice weekend everyone! 06:38 -!- jasan [~jasan@2001:470:6f:200:ec29:2c49:5710:ccb6] has quit [Quit: Have a nice weekend!] 06:38 < vincenzopalazzo> always with lightnind up :-) have a good weekend you too! 08:01 -!- kexkey [~kexkey@89.36.78.246] has joined #c-lightning 08:06 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 08:11 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 08:12 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 08:45 < grubles> so c-lightning's makefile looks for sha256sum, but openbsd does not have sha256sum - only sha256. is there a less hacky way of getting configure to find sha256 than symlinking sha256 to sha256sum ? 08:47 < darosior> grubles: yes https://github.com/ElementsProject/lightning/issues/4075 08:48 < grubles> ah i should've searched through issues. thanks! 08:50 < grubles> that doesn't appear to work for openbsd actually. 08:51 < grubles> checking for shasum -a 256... not found. "We need sha256sum or shasum -a 256!" 08:56 -!- vincenzopalazzo [~vincent@mob-109-119-23-10.net.vodafone.it] has quit [Quit: Leaving] 08:57 < darosior> What's the OpenBSD shasum flavor ? 08:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 08:57 < grubles> sha256 08:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 09:36 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 10:29 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 10:56 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver] 11:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds] 11:05 -!- jonatack [~jon@213.152.162.15] has joined #c-lightning 11:19 -!- ksedgwic_ [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has joined #c-lightning 11:19 -!- ksedgwic [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has quit [Quit: leaving] 11:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 11:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 12:03 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 12:33 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 13:25 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 14:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds] 14:37 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds] 14:41 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 15:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:34 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 15:45 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 15:51 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 15:56 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 16:02 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 264 seconds] 16:25 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 16:25 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 16:34 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 16:39 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 272 seconds] 16:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 16:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 17:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 17:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 18:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 19:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:03 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 19:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 19:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 19:56 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 20:00 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 20:40 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Read error: Connection reset by peer] 20:42 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 21:07 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 21:10 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds] 21:12 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 21:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 21:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 21:47 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 22:05 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds] 22:10 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 22:48 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning --- Log closed Sat Oct 10 00:00:42 2020