--- Log opened Sun Apr 26 00:00:04 2020
00:05 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
00:34 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ec47:4cfe:fdff:656c] has joined #rust-bitcoin
01:15 < ariard> BlueMatt: yeah I was willingly moving LocalOnchainCommitment further in OnchainTxHandler, but that doesn't make sense to add a storage requirement on signer
01:16 < ariard> like I can see a signer storing previous htlc hash, but that doesn't mean we should impose something like this
01:18 < ariard> will do the move back in 562
05:02 -!- jonatack [~jon@37.172.109.60] has quit [Ping timeout: 260 seconds]
05:02 -!- jonatack [~jon@82.102.27.195] has joined #rust-bitcoin
05:28 < elichai2> I wonder if https://github.com/bitcoin-core/secp256k1/issues/702#issuecomment-619162479 could work for a user of rust-secp who wants to use the `sha2` crate for SHA-NI/SIMD implementations
05:33 < elichai2> So the sha2 crate exposes: `pub fn compress256(state: &mut [u32; 8], block: &[u8; 64])` so wrapping that with an `extern C` function that also implements the `while blocks--` should work. but the user will need to do that in compile time
06:14 -!- jonatack [~jon@82.102.27.195] has quit [Ping timeout: 240 seconds]
06:16 -!- jonatack [~jon@37.172.132.110] has joined #rust-bitcoin
06:28 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:199d:ea40:f2ff:fe85:d2dc] has quit [Quit: WeeChat 2.6]
06:38 < elichai2> wumpus: you might be interested, updating libsecp can reduce the size `lowmemory` takes. currently running `cargo test --no-run --release --features=lowmemory,recovery` and then the binary under valgrind it takes `==830421==   total heap usage: 1,679 allocs, 1,679 frees, 3,222,787 bytes allocated`. after updating it will take `==829435==   total heap usage: 1,677 allocs, 1,677 frees, 2,240,003 bytes allocated`
06:38 < elichai2> is 1MB of heap interesting for you? I'm debating if I should open a PR to bump libsecp
07:06 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:199d:ea40:f2ff:fe85:d2dc] has joined #rust-bitcoin
10:21 < BlueMatt> ariard: cool! thanks.
10:22 < BlueMatt> elichai2: doesnt the SIMD stuff for sha2 only mostly make sense if you're hashing two things in parallel? I mean SHA-NI a bit different but....
10:24 -!- TiffanyDoll [5571c4c5@gateway/web/cgi-irc/kiwiirc.com/ip.85.113.196.197] has joined #rust-bitcoin
10:31 -!- TiffanyDoll [5571c4c5@gateway/web/cgi-irc/kiwiirc.com/ip.85.113.196.197] has quit [Ping timeout: 260 seconds]
10:40 < elichai2> I do think that SSE 4.2 enables faster SHA2 even without parallelizing, but I might be wrong
10:56 -!- jonatack [~jon@37.172.132.110] has quit [Ping timeout: 246 seconds]
11:02 -!- jonatack [~jon@134.19.179.235] has joined #rust-bitcoin
11:16 -!- jonatack [~jon@134.19.179.235] has quit [Ping timeout: 244 seconds]
11:17 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
11:31 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
11:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
15:12 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 244 seconds]
15:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
15:16 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
16:06 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
16:07 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
16:52 -!- CandyWendy [79ed9586@gateway/web/cgi-irc/kiwiirc.com/ip.121.237.149.134] has joined #rust-bitcoin
16:54 -!- CandyWendy [79ed9586@gateway/web/cgi-irc/kiwiirc.com/ip.121.237.149.134] has quit [Client Quit]
17:33 -!- mauz555 [~mauz555@2a01:e0a:56d:9090:ec47:4cfe:fdff:656c] has quit [Remote host closed the connection]
--- Log closed Mon Apr 27 00:00:06 2020