Skip to content

chore(deps): move the zingolib pin to dev head - #1297

Open
zancas wants to merge 2 commits into
devfrom
bump_zingolib_to_dev_head
Open

chore(deps): move the zingolib pin to dev head#1297
zancas wants to merge 2 commits into
devfrom
bump_zingolib_to_dev_head

Conversation

@zancas

@zancas zancas commented Aug 22, 2026

Copy link
Copy Markdown
Member

What this changes

The zingolib dependency resolves through branch = "dev". The pin therefore
lives in the lockfiles, not in the manifests. This change moves the pin to
zingolib ffd16c22. That revision is twenty commits ahead of the previous
pin, 00950535.

The change touches two lockfiles. The rust/nym-proxy-ffi crate resolves in
its own workspace, with its own lockfile. A cargo update on the main
workspace never touches it. That crate pins zingo-netutils and the patched
rustls-platform-verifier at the same branch. Both move here.

Why now

zingolib merged pull request 2719, "Make the conduit dial a proper guard".
That pull request also rewrites zingo-price.

Risk

Two commits in the range carry a breaking marker. Both change
zingo-netutils.

  • 8d5f9488 gives a conduit dial the fetch it guards. The wallet now drives
    the price source race. first_quote now only picks the winner from the
    outcomes.
  • acd5e540 prunes the reqwest features that the fetch inherited.

Neither commit reaches this repository's source. The lightclient mixnet
module is byte-identical across the two revisions. update_current_price
still returns MixnetPriceFetch. zec_price still reads the usd field.

Verification

Static checks:

  • Both workspaces compile against ffd16c22 with all targets enabled.
  • The main workspace passes its 60 unit tests.
  • nym-proxy-ffi passes its 7 unit tests.

Device test, on an x86_64 emulator at API 36:

  • The build produces both native libraries for x86_64. The prodDebug
    build installs, opens its wallet, and syncs mainnet to height 3456314. The
    scan covers Sapling, Orchard, and Ironwood outputs.
  • The betaDebug build creates a new wallet and syncs to the chain tip.
  • Mixnet Mode reaches a live state. The client sends and receives real
    packets under cover traffic, at an average delay of 20 ms.
  • A price fetch races four sources over the mixnet: Gemini, CoinGecko,
    Kraken, and Coinbase. Every source answers. The winning quote arrives about
    0.7 seconds after the tap. The race drains in under 7 seconds.
  • The app renders the price. The header shows $ 840.70 for ZEC.

The price path is the surface that pull request 2719 rewrote, so the device
test exercises the change rather than the pin alone.

🤖 Generated with Claude Code

zancas and others added 2 commits August 21, 2026 20:26
The zingolib dependency resolves through `branch = "dev"`, so the pin lives
in the lockfiles rather than in the manifests. Both lockfiles now name
ffd16c22, twenty commits ahead of 00950535.

Two of those commits change zingo-netutils and carry a breaking marker. One
gives a conduit dial the fetch it guards, which rewrites zingo-price so the
wallet drives the source race and first_quote only picks the winner. The
other prunes the reqwest features the fetch inherited. Neither reaches this
repository's source. The lightclient's mixnet module is byte-identical
across the two revisions, so update_current_price still returns
MixnetPriceFetch and zec_price still reads its usd field.

The nym-proxy-ffi crate resolves in its own workspace and its own lockfile,
which cargo update on the main workspace never touches. It pins
zingo-netutils and the patched rustls-platform-verifier at the same branch,
and this change moves both.

Both workspaces compile against the new revision with all targets enabled,
and the sixty unit tests in the main workspace and the seven in
nym-proxy-ffi pass.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant