TransferRegistryClient
Client for a CIP-0056 registry's off-ledger transfer-instruction API (/registry/transfer-instruction/v1/...).
Registries hand out two things a wallet cannot derive on its own: the factory contract to exercise for a new transfer, and per-choice contexts (referenced contracts + disclosed contracts) for accept/reject/withdraw.
Types
What a registry returns for one choice. choiceContextData is the Daml-JSON ChoiceContext the choice's extraArgs must carry — ChoiceContextJson.extraArgsValue re-encodes it for gRPC — or null when the registry sent none; disclosedContracts must be submitted with the command.
A contract the registry asks us to disclose with the command.
The registry's answer to transferFactory: which factory contract to exercise, how the registry will route the transfer, and the choice context to submit with it.
Functions
POST /transfer-factory: the factory + context for a new transfer.
POST /{id}/choice-contexts/{accept|reject|withdraw}.