`bdk` crate is confusing

[casey]

It's very easy to find the old bdk crate when searching, either on Google or crates.io, and get confused, and not realize you should be looking at the bdk_wallet crate.

Perhaps a new, empty crate should be published to bdk, whose only documentation is an explanation and a link to bdk_wallet?

Alternatively, you could have the bdk crate only contain a single public rexport of bdk_wallet as wallet, which would also provide the link. If you did this, you could also add more public exports in the future, of other bdk related crates, so that adding bdk to a project would be a convenient way of pulling in all bdk crates.

[notmandatory]

We did add a bold !!DEPRECATED!! message on the latest crates.io versions. For now we need to keep the old pre-1.0 bdk around for projects that are still using it in production apps and may need patch fix versions.

But it's good to start thinking about what to do once we think all projects have moved to bdk_wallet to prevent anyone from using this old bdk. I like the idea of re-exporting new bdk repo crates.

[casey]

We did add a bold !!DEPRECATED!! message on the latest crates.io versions. For now we need to keep the old pre-1.0 bdk around for projects that are still using it in production apps and may need patch fix versions.

This definitely helps, but it's easy to land, via google search, on a page other than the main page, which won't have the message.

An easy fix which wouldn't require doing very much is to publish an empty 0.31 crate under bdk.