The mixnet proxy shim (rust/nym-proxy-ffi/, moved here from zingolib)
depends on zingo-netutils as a git dependency with branch = "dev".
Its committed Cargo.lock supplies reproducibility, and cargo update
advances the pin deliberately.
The main workspace pins zingolib the same way in its own lockfile. The
two lockfiles therefore pin different zingolib revisions over time. The
wallet reaches the shim only through its SOCKS5 listener and the UniFFI
surface, never through shared Rust types, so we accepted the skew in
the 2026-08-10 design session (ADR 0005, follow-up).
This issue schedules the revisit of that choice. The alternative is a
rev pin that a human bumps in both lockfiles together. Revisit once the
shim has shipped in a release, or sooner if the skew bites.
The mixnet proxy shim (
rust/nym-proxy-ffi/, moved here from zingolib)depends on
zingo-netutilsas a git dependency withbranch = "dev".Its committed
Cargo.locksupplies reproducibility, andcargo updateadvances the pin deliberately.
The main workspace pins zingolib the same way in its own lockfile. The
two lockfiles therefore pin different zingolib revisions over time. The
wallet reaches the shim only through its SOCKS5 listener and the UniFFI
surface, never through shared Rust types, so we accepted the skew in
the 2026-08-10 design session (ADR 0005, follow-up).
This issue schedules the revisit of that choice. The alternative is a
rev pin that a human bumps in both lockfiles together. Revisit once the
shim has shipped in a release, or sooner if the skew bites.