fix(ledgrpc): align ImportPartyAcsRequest with Canton 3.5.3 - #21
Open
schronck wants to merge 1 commit into
Open
Conversation
Canton 3.5 inserted synchronizer_id (field 2) and party_id (field 6) into ImportPartyAcsRequest and made the existing fields optional, shifting workflow_id_prefix/contract_import_mode/representative_package_id_override down by one. Clients built against the 3.4 layout send workflow_id_prefix in field 2, which 3.5 nodes decode as synchronizer_id and reject. Refreshed the message to the 3.5.3 shape (verified via gRPC reflection against a live 3.5.3 participant). Only this message changed in the party-management API surface.
PumpkinSeed
approved these changes
Jun 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Canton 3.5 changed
ImportPartyAcsRequest: it insertedsynchronizer_id(field 2) andparty_id(field 6), made the existing fieldsoptional, and shiftedworkflow_id_prefix→ 3,contract_import_mode→ 4,representative_package_id_override→ 5. Our vendored proto still has the 3.4 layout (workflow_id_prefixat field 2). A client built against 3.4 sends its workflow prefix in field 2, which a 3.5 node decodes assynchronizer_idand rejects:(Reproduced from
dec-party-manager's add-party / offline party replication flow against a devnet participant.)Fix
Refreshed
ImportPartyAcsRequestto the Canton 3.5.3 shape, verified field-by-field via gRPC reflection against a live 3.5.3 participant:This is the only message in the party-management admin API that drifted between 3.4 and 3.5.3 for our call set —
ExportPartyAcsRequest,ClearPartyOnboardingFlagRequest, andGetHighestOffsetByTimestampRequestall still match (confirmed via the same reflection check), so the blast radius is one message.Crate version
3.4.0→3.5.3to reflect the targeted Canton version.🤖 Generated with Claude Code