--- Log opened Fri Feb 26 00:00:40 2021
00:36 -!- Kiminuo [~Kiminuo@141.98.103.116] has joined #rust-bitcoin
00:53 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #rust-bitcoin
01:24 -!- Jarred30Howe [~Jarred30H@static.57.1.216.95.clients.your-server.de] has quit [Remote host closed the connection]
01:27 -!- Joesph15Kutch [~Joesph15K@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
02:02 -!- Guest7650 [~real_or_r@2a02:c207:3002:7468::1] has quit [Quit: ZNC 1.8.2 - https://znc.in]
02:03 -!- real_or_random [~real_or_r@173.249.7.254] has joined #rust-bitcoin
03:17 -!- Joesph15Kutch [~Joesph15K@static.57.1.216.95.clients.your-server.de] has quit [Remote host closed the connection]
03:18 -!- Lauretta77Hyatt [~Lauretta7@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
03:57 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has joined #rust-bitcoin
05:00 -!- tibo [~tibo@2400:4050:2a83:7000:81bf:120a:4906:c269] has quit [Remote host closed the connection]
05:03 -!- Kiminuo [~Kiminuo@141.98.103.116] has quit [Quit: Leaving]
05:40 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:04 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has joined #rust-bitcoin
06:08 -!- jonatack [~jon@37.173.36.152] has joined #rust-bitcoin
06:13 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
06:14 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:17 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
06:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
06:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
06:41 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has joined #rust-bitcoin
06:48 -!- jonatack [~jon@37.173.36.152] has quit [Read error: Connection reset by peer]
06:48 -!- jonatack_ [~jon@37.173.36.152] has joined #rust-bitcoin
06:53 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:55 -!- jonatack_ [~jon@37.173.36.152] has quit [Quit: jonatack_]
06:56 -!- jonatack [~jon@37.173.36.152] has joined #rust-bitcoin
07:07 -!- jonatack_ [~jon@37.173.36.152] has joined #rust-bitcoin
07:07 -!- jonatack [~jon@37.173.36.152] has quit [Read error: Connection reset by peer]
07:08 -!- jonatack_ [~jon@37.173.36.152] has quit [Client Quit]
07:09 -!- jonatack [~jon@37.173.36.152] has joined #rust-bitcoin
07:12 -!- jonatack [~jon@37.173.36.152] has quit [Excess Flood]
07:14 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #rust-bitcoin
07:19 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 276 seconds]
07:26 -!- jonatack [~jon@37.173.36.152] has joined #rust-bitcoin
07:50 < BlueMatt> ariard: can I merge 791 despite your comment about Poll? https://github.com/rust-bitcoin/rust-lightning/pull/791#discussion_r583277821
07:53 < BlueMatt> andytoshi: plz2conceptack https://github.com/rust-bitcoin/rust-secp256k1/pull/282
07:53 < ariard> BlueMatt: sure it was a nit!
07:53 < BlueMatt> :100:
07:54 < ariard> congrats jkczyz!
07:55 < BlueMatt> ok! now just need mpp and a few followups....
07:55 < BlueMatt> almost release time...I do wanna land the rust-bitcoin bump, but that needs upstream secp
07:55 < ariard> BlueMatt: yeah gonna look on mpp tonight, reviewing multiprocess in core rn
07:55 < ariard> like finally mature
07:56 < BlueMatt> mpp needs the new fuzz failures debugged. it'll be a slog but I dont think more code review time is gonna solve it.
07:56 < ariard> BlueMatt: still wanna include 756 in release?
07:56 < BlueMatt> no.
07:56 < ariard> well just re-ack mpp if you prefer
07:57 < BlueMatt> I need to finish the test I wrote and it doesnt need to land in time
07:57 < BlueMatt> I do wanna fix the issue I mentioned to jeff on 791 on slack but I only started that yesterday
07:57 -!- Lauretta77Hyatt [~Lauretta7@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 264 seconds]
07:57 < BlueMatt> as a separate pr, obviously
07:57 < ariard> good
07:58 < BlueMatt> anyway, I've got a lot of work to do...we'll see how far I get today but ideally we'll have all the fixes we need open by monday.
07:58 < BlueMatt> ariard: if you're looking for work on RL, either anchors or custom scripts would be cool
07:59 < ariard> yeah rebasing sample on 791 broke a lot of things, master has moved fast
08:00 < ariard> BlueMatt: well actually hacking on your headers-over-dns in core, building on multiprocess
08:00 < ariard> when done, hopefully end next week, focusing on anchors
08:01 < ariard> and yeah custom scripts, cleaning up internal interfaces in prevision of taproot would be great
08:01 < ariard> note, custom scripts is pending on anchor 1/3, the refactoring part
08:01 < BlueMatt> right.
08:01 < BlueMatt> cool, have fun.
08:01 < BlueMatt> I'm still a ways from having time to work on spec stuff in RL :( too much binding stuff left
08:02 < BlueMatt> but at least i have time to do reviews again
08:03 < BlueMatt> also one day need to look at trampoline :(
08:03 < ariard> or you still wanna explore minisketch to compress gossips?
08:03 < BlueMatt> eventually...
08:04 < BlueMatt> honestly the people pushing trampoline need to download the graph from a server
08:04 < BlueMatt> its not big, doubly so if you delete the signatures
08:04 < BlueMatt> I mean, sorry, its not "not big", its damn tiny
08:04 < ariard> yeah I wanna also write a new reseach paper on security of anchor w.r.t to mempool congestion
08:04 < BlueMatt> the focus on anchor is almost embarassing
08:05 < ariard> you mean current spec effort ?
08:05 < BlueMatt> yea
08:05 < BlueMatt> and implementation effort
08:05 < BlueMatt> I mean electrum did anchor instead of just having the electrum servers fetch the route graph
08:05 < ariard> I know, when we don't know how to do secure fee-bumping yet
08:06 < BlueMatt> like, its a lot of work to implement anchor, its comparatively less work to implement graph download
08:06 < BlueMatt> and way more private
08:06 < ariard> hmmm, but it's 2 different areas of LN, the issue is more we're able to advance in parallel
08:06 < ariard> on different topics in the spec effort
08:07 < ariard> I chat about it with t-bast, have different tracks for LN specification to move faster
08:07 < ariard> but likely to wait a big spec meeting to decide
08:07 < ariard> *we're not able
08:08 < BlueMatt> s/the focus on anchor is almost embarassing/the focus on trampoline is almost emberassing/
08:08 < BlueMatt> I'm sorry, I now realize why we're having two conversations lol
08:09 < BlueMatt> I'm tired :/
08:09 < ariard> ahahah take a day off tmrw ;)
08:09 < BlueMatt> my point is more, like, *why* is t-bast spending his time on trampoline - sure, we can parallelize the spec a bunch but, like, trampoline seems like incredibly misplaced effort
08:09 < BlueMatt> after I got covid I stopped drinking coffee (it makes me not sleep now, to an astounding degree?!), so I'm a mess
08:10 < ariard> lol really you stop driking coffee!
08:10 < BlueMatt> if I have one cup of coffee I dont sleep until 3am
08:10 < BlueMatt> its bad
08:10 < ariard> yeah do meditation before sleep, works well (for me at least)
08:11 < BlueMatt> I mean now that I'm not drinking coffee I sleep fine lol
08:11 < ariard> but yeah trampoline is a cool crypto project, might open cool future applications (like smarter packet routing?), but might not solve the right problem...
08:12 < BlueMatt> right, I'm not screaming that we shouldnt merge it into the spec precisely because it may be useful for other things
08:12 < BlueMatt> but the thing its being used for makes me really sad
08:12 < BlueMatt> lightning privacy is so broken already, and that just makes it a lot worse
08:13 < ariard> yeah I agree, well up to us to come with better practices and advocate for it
08:13 < ariard> i should do a session on lightning privacy for the upcoming online training, few good papers on it last year
08:14 < BlueMatt> yea, there's good papers explaining that its broken af but no one has time to really work on that issue
08:14 < BlueMatt> but we do have time to work on making it worse :(
08:15 < ariard> we'll get there, just to have be patient...
08:15 < BlueMatt> yea
08:15 < ariard> I'll try to write this lightclient howto for ldk next week
08:15 < ariard> good place to educate on ln privacy issues
08:16 < BlueMatt> make sure you chat with val first, she's made a lot of progress already
08:16 < BlueMatt> probably best to do it as a website update
08:17 < ariard> oh yeah sure at least rn website==doc
08:17 < BlueMatt> right lol
08:17 < BlueMatt> good place to put things :)
08:18 < ariard> yeah we have ldk sample meeting in ~30min if you wan to join, gotta finish this review before :p
08:19 < andytoshi> BlueMatt: concept ack
08:20 < BlueMatt> ariard: I should probably listen in to those, but not sure I have much to add.
08:20 < BlueMatt> andytoshi: note there's a bitcoin_hashes companion which checks for 0 hashes and returns 1 instead
08:21 < andytoshi> nice, concept ack that too
08:21 < BlueMatt> ok, thanks
08:22 < BlueMatt> I'm gonna depend on those PRs in rust-lightning's fuzzing subcrate, fwiw
08:22 < BlueMatt> and also depend on https://github.com/rust-bitcoin/rust-secp256k1/pull/279 in our c bindings
08:22 < BlueMatt> (though *most* of our contexts are randomized, thats just for one group of them, which honestly I should probably just drop in the api)
08:25 < andytoshi> yeah concept ack that too
08:25 < BlueMatt> oh, no, I cant drop all of them, damn.
08:25 < andytoshi> i'm not so worried about the context randomization, it's a defense in depth against sidechannel attacks and i'd be hard-pressed to demonstrate a benefit
08:26 < andytoshi> not that you shouldn't do it ... but it's far from critical
08:26 < BlueMatt> yea....I'd need to audit, but it may very well be the only places we actually use the global contexts are verify tables anyway
08:27 < BlueMatt> oh, no, we do public key combines and private key multiplies and such which takes a signing context
08:29 -!- belcher_ is now known as belcher
09:35 -!- jonatack [~jon@37.173.36.152] has quit [Ping timeout: 265 seconds]
09:40 -!- jonatack [~jon@37.173.36.152] has joined #rust-bitcoin
10:31 < BlueMatt> stevenro- or andytoshi: I dunno how active you (or anyone else) is on maintaining rust-jsonrpc's http client, but jkczyz wrote a much fancier one at https://github.com/rust-bitcoin/rust-lightning/blob/main/lightning-block-sync/src/http.rs that uses async (though if you had a macro to make a function optionally async it'd be turned off with just a flag) and supports (via feature flag) tokio sockets, plus will work with http chunked
10:31 < BlueMatt> responses as well as normal ones (so can be used for bitcoin core REST)
10:31 < BlueMatt> Ideally if we could use that one in rust-bitcoinrpc we'd also be able to support rest, and then we could drop our json parsing code and just call rust-bitcoinrpc directly.
10:33 < andytoshi> yeah i think that's a good idea
10:33 < andytoshi> no need to macroize the async/await, just feature gate the whole thing
10:33 < andytoshi> if you insist on using JSONRPC with rust 1.29 you have the simple_http
10:33 < BlueMatt> yea, thats the approach we took. the code is so close to not needing it, though
10:34 < BlueMatt> I mean you literally just need to figure out how to make a macro that either does or does not print async into the function definition and you could drop it
10:34 < BlueMatt> but, whatever.
10:34 < andytoshi> yeah, maybe in principle it'd be worth trying to macroize it
10:34 < andytoshi> but in practice
10:34 < BlueMatt> yea, well, we didnt bother and I'm not gonna fight with it :)
10:34 < andytoshi> it's next to impossible to get anything done in rust-jsonrpc because there's so much tension between 1.29 and HTTP
10:35 < andytoshi> lol yeah
10:35 < andytoshi> so better to just do _something_ and crudely feature-gate the whole module if it can't hit the msrv target
10:37 -!- yojoots [~justin@2600:1700:19e0:4b10:395d:4876:3b09:9fed] has quit [Quit: Leaving]
10:39 < BlueMatt> right....would need to check but I'd think the code there is basically already 1.29, just with one async keyword in the way.
10:39 < andytoshi> lol if it's really just one async keyword i guess we could find a way to feature-gate that
11:04 -!- Kiminuo [~Kiminuo@141.98.103.116] has joined #rust-bitcoin
11:20 -!- jeremyrubin [~jr@024-176-247-182.res.spectrum.com] has joined #rust-bitcoin
12:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
12:02 -!- belcher [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
13:08 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
13:11 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 276 seconds]
13:20 -!- belcher_ is now known as belcher
13:24 -!- jonatack_ [~jon@37.167.224.27] has joined #rust-bitcoin
13:25 -!- jonatack [~jon@37.173.36.152] has quit [Ping timeout: 265 seconds]
13:45 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has joined #rust-bitcoin
13:46 -!- geyaeb_ [~geyaeb@gateway/tor-sasl/geyaeb] has quit [Remote host closed the connection]
14:18 -!- Kiminuo [~Kiminuo@141.98.103.116] has quit [Quit: Leaving]
14:25 -!- th0th1 [~th0th@gateway/tor-sasl/th0th] has joined #rust-bitcoin
14:28 -!- th0th1 [~th0th@gateway/tor-sasl/th0th] has quit [Remote host closed the connection]
14:28 -!- th0th1 [~th0th@gateway/tor-sasl/th0th] has joined #rust-bitcoin
14:29 -!- th0th [~th0th@gateway/tor-sasl/th0th] has quit [Ping timeout: 268 seconds]
14:35 -!- th0th1 [~th0th@gateway/tor-sasl/th0th] has quit [Quit: Leaving]
15:05 -!- jeremyrubin [~jr@024-176-247-182.res.spectrum.com] has quit [Ping timeout: 256 seconds]
15:26 -!- jonatack_ [~jon@37.167.224.27] has quit [Ping timeout: 264 seconds]
15:51 < ariard> BlueMatt:  (a), sending a monitor update which broadcasts a
15:51 < ariard> conflicting holder commitment transaction is far from
15:51 < ariard> time-critical
15:51 < ariard> from 808, IIUC you're connecting block which have not never been processed
15:51 < ariard> but discovered by backended since shutdown?
15:52 < ariard> at the contrary, I would say we might have really time-critical txn to broadcast
15:55 < BlueMatt> ariard: the time-critical ones are already handled by chainmonitor in its own block connection
15:55 < ariard> ah okay reading PR, it doesn't concern ChannelMonitor block_connected updates
15:55 < BlueMatt> the only transaction being braodcast there is the conflicting (useless) local state
15:55 < BlueMatt> which we broadcast cause, like, it could be some crazy spv partition or something
15:55 < BlueMatt> but its kinda stupid that we even bother.
15:56 < ariard> yeah that's the same for disconnection, if funding is reorged-out
15:56 < ariard> it should still in miner mempools
15:56 < ariard> otherwise means its feerate isn't good anymore and we should bump it
15:56 < ariard> like i'm not sure if it really matters
15:57 < BlueMatt> lol does github actions have no timeout? I have jobs that are clearly hanging that are already at 3hours of runtime and still generating output?
15:57 < BlueMatt> ariard: right, it borderline doesnt. I figured it doesnt hurt to keep it, though, and also removing it means a billion test updates.
16:17 < BlueMatt> ouchhhh....no, it was just the fuzzing updates, which take the channel state machine fuzzer from 1k/sec to about 50/sec :(
16:17 < BlueMatt> yea, thats not really acceptable, damn.
16:36 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has joined #rust-bitcoin
16:38 -!- jonatack_ [~jon@37.167.35.203] has joined #rust-bitcoin
16:42 -!- jonatack_ [~jon@37.167.35.203] has quit [Read error: Connection reset by peer]
17:49 -!- jeremyrubin [~jr@024-176-247-182.res.spectrum.com] has joined #rust-bitcoin
18:29 < BlueMatt> TIL rustc will compile `const a: [u8; 1] = [0; 1];` to be in the program image, and thus loaded into an RO segment of memory.
18:29 < BlueMatt> errr, s/const/static/
20:11 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:45 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
20:45 -!- shesek [~shesek@164.90.217.137] has joined #rust-bitcoin
20:45 -!- shesek [~shesek@164.90.217.137] has quit [Changing host]
20:45 -!- shesek [~shesek@unaffiliated/shesek] has joined #rust-bitcoin
22:51 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has joined #rust-bitcoin
23:04 -!- da39a3ee5e6b4b0d [~da39a3ee5@2403:6200:8876:c8ae:4c2c:c3c0:6062:2fc9] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:14 -!- jeremyrubin [~jr@024-176-247-182.res.spectrum.com] has quit [Ping timeout: 276 seconds]
--- Log closed Sat Feb 27 00:00:41 2021