--- Log opened Thu Aug 11 00:00:47 2022
00:03 -!- u32Luke [~u32Luke@136.144.19.251] has joined #bitcoin-rust
00:47 -!- u32Luke [~u32Luke@136.144.19.251] has quit [Quit: Client closed]
01:15 -!- pablomartin [~pablomart@37.120.148.189] has joined #bitcoin-rust
01:17 -!- tibo [~tibo@240d:1a:afa:4000:dde:6dae:ebc1:f239] has joined #bitcoin-rust
01:17 -!- pablomartin_ [~pablomart@37.120.148.189] has joined #bitcoin-rust
01:18 -!- pablomartin_ [~pablomart@37.120.148.189] has quit [Remote host closed the connection]
01:19 -!- pablomartin [~pablomart@37.120.148.189] has quit [Client Quit]
01:23 < tibo> I'm trying to compile some code that uses rust-secp256k1-zkp and rust-secp256k1-sys on macos and can't solve the error I'm getting: "No available targets are compatible with triple "wasm32-unknown-unknown"". It seems to be happening on target/release/build/secp256k1-sys-92faffd3f50773ba/build-script-build . Anybody has a suggestion on how to solve that? Spent quite some time on it but couldn't make any progress. I can see
01:23 < tibo>  in this PR (https://github.com/ElementsProject/rust-secp256k1-zkp/pull/54) that it should be able to compile at least. The versions I use are 0.6.0 for zkp and 0.5.2 for sys.
01:51 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 268 seconds]
01:52 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
01:56 -!- kcalvinalvin [~kcalvinal@ec2-3-38-183-204.ap-northeast-2.compute.amazonaws.com] has quit [Quit: ZNC 1.7.4 - https://znc.in]
01:58 -!- kcalvinalvin [~kcalvinal@ec2-3-38-183-204.ap-northeast-2.compute.amazonaws.com] has joined #bitcoin-rust
02:09 -!- tibo_ [~tibo@fp5a950abc.tkyc110.ap.nuro.jp] has joined #bitcoin-rust
02:12 -!- tibo [~tibo@240d:1a:afa:4000:dde:6dae:ebc1:f239] has quit [Ping timeout: 264 seconds]
09:50 < BlueMatt[m]> welp, now I want to rip out serde - the serde maintainer is literally arguing with me that the msrv of 1.13 isn't broken by the fact that you cant build serde with a version of cargo that corresponds with rustc 1.48
10:24 < andytoshi> lol jeez
10:24 < BlueMatt[m]> wat
10:24 < BlueMatt[m]> lol, his conclusion was to just remove any MSRV statements from serde
10:24 < andytoshi> sigh
10:24 < BlueMatt[m]> okay, so I think rust-bitcoin should remove all serde support
10:26 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 268 seconds]
10:26 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
10:27 < andytoshi> casey is trying to come up with a general-purpose serialization framework .. his goals seem kinda confused but if we need a serde replacement maybe we could give him some requirements
10:28 < andytoshi> serde already is annoying because it can't support bignums, it doesn't treat bytestrings as first-class (rather as generic arrays of numeric u8s), it -does- support floats and usizes and other things we dislike
10:30 < andytoshi> otoh maintaining a serialization framework is a big job and not one that i want to do..
10:30 < BlueMatt[m]> I mean we already do...for consensus stuff.
10:31 < andytoshi> true
10:31 < andytoshi> we could unseal those traits
10:31 < andytoshi> iirc kixunil thought they weren't production-ready somehow and that we ought to keep them private as possible
10:31 < BlueMatt[m]> and most of the serde stuff is double-encoding anyway, so could always just tell users to use that and not bother with serde
10:32 < andytoshi> yeah
10:32 < andytoshi> i think serde is most useful for json
10:32 < andytoshi> for talking to bitcoin core
10:45 < elichai2> What is this used for? https://docs.rs/bitcoin/latest/bitcoin/util/trait.BitArray.html
10:48 < andytoshi> elichai2: to get zero() and other basic things that have no std trait
10:49 -!- trev [~trev@user/trev] has quit [Remote host closed the connection]
10:49 < andytoshi> it's used internally to abstract over uint128 and uint256 ... we probably could drop the crate if we dropped uint128
10:49 < andytoshi> drop the trait*
10:49 < elichai2> About that: https://github.com/rust-bitcoin/rust-bitcoin/pull/1181#issuecomment-1212276061
11:04 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection]
11:05 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
11:19 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection]
11:20 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
11:53 -!- afilini [~afilini@2001:bc8:1828:245::2] has joined #bitcoin-rust
11:53 < afilini> i personally find serde useful, so i would be against straight away dropping serde support
11:53 < BlueMatt[m]> do you support MSRV of anything but stable on your end?
11:54 < afilini> even if it requires a higher msrv i would just keep it there, maybe document this thing that it requires a higher msrv
11:54 < BlueMatt[m]> it wouldnt be the only time we've had a different MSRV for a different feature, but man "stable, or GFY" is a pretty aggressive MSRV :(
11:54 < afilini> i think we are using 1.57 or something in bdk
11:54 < BlueMatt[m]> or, really, "no defined MSRV, you have to ask if something is supported", which seems to be the attitude.
11:55 < BlueMatt[m]> afilini: heh,yea, I know, I've never been able to build bdk before
11:59 < afilini> yeah we've gotta finish splitting it up to at least drop the msrv of the "core" code
13:54 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection]
13:58 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
13:58 -!- Intdtti [~intdtti@146.70.123.180] has joined #bitcoin-rust
16:58 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection]
16:59 -!- evanlinjin [~root@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
22:24 -!- trev [~trev@user/trev] has joined #bitcoin-rust
--- Log closed Fri Aug 12 00:00:48 2022