--- Log opened Sun Sep 05 00:00:58 2021
01:23 -!- Guest60 [~Guest60@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Quit: Client closed]
01:46 < nathanael> ok weird, i restarted my node. then my 'num_pending_channels' were gone. then i connected to niftyneis node and now it says i have 1 pending channel... (i only connected and did nothing else)
02:22 < darosior> cdecker[m]: got a sauron crash with https://blockstream.info/api/block/0000000000000000000e16bdb1b905fae1a9dfdabcfb86bb48aa4d877ddac460/raw , backtrace: https://0bin.net/paste/YP7whZGM#X2EeUeukuY00Gj6T7vKp3-Wm/lnv1S8CspRJQdaJNcO
02:33 < darosior> So this doesn't happen with a specific block, got the same issue at block 698887
02:36 < darosior> Ok found it
02:53 < darosior> So it (rightly) fails to decode 020000000001016495d4067b402d084b802497c4518db12466d094626f3578c07c631a8e10beb00100000000ffffffff02070a0300000000001976a914bf2bb0adb2d22cf535ac08d1622812f68c22
03:11 -!- Nebraskka_ [~Nebraskka@user/nebraskka] has joined #c-lightning
03:17 < darosior> Ok so i think the stream was somehow trimmed and we returned an incomplete block to lightningd..
03:18 -!- Nebraskka [~Nebraskka@user/nebraskka] has quit [Ping timeout: 276 seconds]
03:18 -!- Nebraskka_ is now known as Nebraskka
03:32 < mschmoock> darosior: uuho. this means that pull_bitcoin_tx (one line before the crash) returned one of the   'return tall_fee(tx)' paths
03:32 < darosior> Yeah because the block was incomplete
03:32 < mschmoock> what caused the stream to be timmed?
03:32 < mschmoock> the plugin should not report half blocks to lightningd :D
03:33 < mschmoock> sauron is proof of blockstream anyway. haha :D
03:35 < mschmoock> okay, you can use your own esplora instance since it does not set blockstreams per default, right?
03:35 < mschmoock> I would use that as default :D
03:36 < mschmoock> what could be handy to have a set of addresses. if one API fails with incomplete block or some other error, try next one
03:36 < darosior> Yeah i'm running it against my instance. Trying to figure how comes a trimmed block gets reported in a first place
03:36 < darosior> Yes
03:37 < darosior> Fuck i'd have to compute the merkle root to make sure all transactions are present... 😭
03:37 < darosior> Ooooh no i'll just use the tx count
03:37 < darosior> hehe
03:37 < mschmoock> phew
03:46 < darosior> But it's so suboptimal.. I can't just do *exactly* what lightningd is going to do after me
03:46 < darosior> (in Python)
03:47 < darosior> Isn't there so HTTP level trick to know whether the download was complete? Like a checksum, content length idk
03:59 < darosior> Yay the headers of the response contain a Content-length
04:00  * darosior **BROKEN** plugin-sauron.py: Esplora gave us an incomplete block, retrying
04:00 < darosior> fixed :)
04:09 < darosior> https://github.com/lightningd/plugins/pull/297
04:19 < darosior> FWIW i've been hacking around the idea of a cache and background block fetcher for sauron to speed up initial sync but didn't come up with something that isn't ugly
09:29 -!- aechu [~major@gateway/tor-sasl/major] has quit [Remote host closed the connection]
09:30 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
11:46 < vincenzopalazzo> darosior: I would like to see some usage of onion messages over the lightning network, one cool thinks to have I think is some storage ln node where you can store some data and get other data
11:46 < vincenzopalazzo> one of this data can be a part of chain
11:47 < vincenzopalazzo> but this idea it too hight level to think an possible real application
12:47 < darosior> vincenzopalazzo: related to this did you see t-bast's proposal?
12:48 < darosior> I wonder how much you can abuse nodes' bandwidth though..
13:28 -!- aechu [~major@gateway/tor-sasl/major] has quit [Remote host closed the connection]
13:28 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
17:17 -!- belcher [~belcher@user/belcher] has quit [Read error: Connection reset by peer]
17:33 -!- belcher [~belcher@user/belcher] has joined #c-lightning
18:49 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
19:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:33 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 250 seconds]
20:49 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
20:58 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 240 seconds]
22:24 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
23:09 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 250 seconds]
--- Log closed Mon Sep 06 00:00:59 2021