From 8031b6f0904d67d4c5e7bf9703d0e0b7cb3845f0 Mon Sep 17 00:00:00 2001 From: zancas Date: Mon, 24 Aug 2026 21:43:52 -0700 Subject: [PATCH] docs: rename "Correspondent" to "Destination" in comments The comments in the FFI layer and the wallet-backend utilities still used the term "Correspondent" for the curated transmission pool. This change renames every prose occurrence to "Destination". The three references to the zingolib symbols NoEligibleCorrespondent and zingolib::correspondent::NoEligibleCorrespondents keep their names, because the crate pinned at tag zingolib_nym_rc0 defines them. Co-Authored-By: Claude Fable 5 --- app/walletBackend/utils/walletUtils.ts | 2 +- rust/lib/src/lib.rs | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/app/walletBackend/utils/walletUtils.ts b/app/walletBackend/utils/walletUtils.ts index 8825f8169..eb6e02fd5 100644 --- a/app/walletBackend/utils/walletUtils.ts +++ b/app/walletBackend/utils/walletUtils.ts @@ -81,7 +81,7 @@ export async function walletExists(): Promise { // Runs before every wallet init. A custom (off-registry) server pins migration // transmission to itself, since no registry pool applies. A registry server -// leaves it unset so the library's curated Correspondent pool, which excludes +// leaves it unset so the library's curated Destination pool, which excludes // the sync operator, routes instead. async function applyBroadcastCandidates( serverUri: string, diff --git a/rust/lib/src/lib.rs b/rust/lib/src/lib.rs index 3060e7090..49dad6046 100644 --- a/rust/lib/src/lib.rs +++ b/rust/lib/src/lib.rs @@ -167,7 +167,7 @@ fn ffi_error(e: LightClientError) -> ZingolibError { LightClientError::MixnetNotReady(_) | LightClientError::ProbeRequiresMixnet => { ZingolibError::Mixnet(text) } - // A deliberate verdict (#1229): exhausting the eligible Correspondents + // A deliberate verdict (#1229): exhausting the eligible Destinations // is a server-topology problem, not a mixnet refusal — switching the // synchronization endpoint changes eligibility, so the app's // switch-and-retry routing can genuinely help. Mapping it to Mixnet @@ -350,7 +350,7 @@ lazy_static! { } // An optional dedicated migration-transmission endpoint, read at every client -// construction. The library owns the curated Correspondent pool and always +// construction. The library owns the curated Destination pool and always // excludes the synchronization operator (ADR 0022), so a mixnet migration works // without any app input. `Some` names one dedicated endpoint distinct from the // sync operator; `None` (the default) lets the library draw its curated pool. @@ -610,7 +610,7 @@ fn build_client_config( None => builder, }; // Point migration transmission at a dedicated endpoint when the app set - // one. Absent it, the library draws its curated Correspondent pool. + // one. Absent it, the library draws its curated Destination pool. let migration_uri = MIGRATION_TRANSMISSION_URI .read() .ok() @@ -626,7 +626,7 @@ fn build_client_config( /// client construction — `{ transmissionUri: "" }` names one endpoint /// distinct from the sync operator, while `null`, `{}`, or the legacy /// `{ candidates, allowSyncEndpoint }` shape clears it so the library's -/// embedded curated Correspondent pool, which always excludes the +/// embedded curated Destination pool, which always excludes the /// synchronization operator, routes instead. pub fn set_broadcast_candidates(candidates_json: String) -> Result { let parsed = json::parse(&candidates_json)