The rust-sdk workspace (hanzoai/rust-sdk) just published these crate names at
1.1.21 with different implementations. To preserve clean namespaces:
- crates.io name: hanzonet-pqc / hanzonet-did / hanzonet-config / hanzonet-mcp
- Rust lib name: hanzo_pqc / hanzo_did / hanzo_config / hanzo_mcp (unchanged)
This is achieved via `[lib] name = "hanzo_<x>"` on the renamed packages and
`package = "hanzonet-<x>"` in workspace.dependencies — consumers keep using
`hanzo-<x>.workspace = true` and `use hanzo_<x>::...` with zero code churn.
Also: bumped patch versions on all members per crates.io state, pinned every
path-dep in workspace.dependencies with a `version = ` so the workspace can
publish to crates.io. workspace.package.version → 1.1.21.
Effect: 32 net crates become publishable in topo order; hanzo-vm,
hanzo-consensus, hanzo-l2 remain `publish = false` because they path-depend
on cross-repo lux crates (luxprecompile-sys, lux-consensus) that aren't on
crates.io.
Hanzo Dev
cdccbacd40