Steve Myers

I've done a little googling and not found any good analysis about BIP47. There may be other issues but I suspect one of the concerns is with the on-chain "Notification...

Thanks having a chat with that team on Monday.

The team is certainly open to PRs to integrate Nakamoto as an optional blockchain backend for bdk. I briefly discussed it with Alexis here: https://bitdevsla.org/socratic-seminar-18/ Or you can build on...

The current `testing` debian release is 11 (bullseye) and it will ship with `rustc 1.48.0`. I think it's worth considering that bullseye may be the `stable` debian by the time...

Something else to note is there appear to be CVEs that affect `rustc` versions prior to `1.52.0`. It looks like the debian `rustc` maintainer is trying to get the fixes...

Based on discussion above, how does this sound as a policy: 1. The `bdk` lib with default features ("key-value-db", "electrum") will have MSRV equal to version of [rustc shipped with...

Good point, how does this sound for a third rule: 3. The MSRV for default or non-default features will be incremented the minimum over the above policies if needed to...

I agree it doesn't make sense to extract features right now. And makes sense to not pin down the MSRV on non-default features yet. I'd like to try keeping the...

At this point I think the best option is set MSRV to 1.56.X, it's not the current stable for Debian but is being tested and should be shipped with next...

I think as a policy we can state, the `bdk` MSRV: 1. Will only be changed with a new MINOR release, never a PATCH release. 2. Will target Debian "stable"...