@c7-digital/ledger 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (98) hide show
  1. package/BUILD.md +125 -0
  2. package/LICENSE +17 -0
  3. package/README.md +97 -0
  4. package/lib/scripts/build.d.ts +9 -0
  5. package/lib/scripts/build.js +366 -0
  6. package/lib/scripts/enhance-types.d.ts +3 -0
  7. package/lib/scripts/enhance-types.js +174 -0
  8. package/lib/scripts/generate-asyncapi-types.d.ts +9 -0
  9. package/lib/scripts/generate-asyncapi-types.js +129 -0
  10. package/lib/scripts/generate-schema-modules.d.ts +3 -0
  11. package/lib/scripts/generate-schema-modules.js +33 -0
  12. package/lib/src/TemplateEmitterMap.d.ts +40 -0
  13. package/lib/src/TemplateEmitterMap.js +57 -0
  14. package/lib/src/client.d.ts +55 -0
  15. package/lib/src/client.js +62 -0
  16. package/lib/src/generated/api.d.ts +7147 -0
  17. package/lib/src/generated/api.js +1 -0
  18. package/lib/src/generated/async-api.d.ts +1665 -0
  19. package/lib/src/generated/async-api.js +1 -0
  20. package/lib/src/generated/asyncapi-schema.d.ts +1 -0
  21. package/lib/src/generated/asyncapi-schema.js +2233 -0
  22. package/lib/src/generated/openapi-schema.d.ts +1 -0
  23. package/lib/src/generated/openapi-schema.js +7321 -0
  24. package/lib/src/generated/sdk-version.d.ts +1 -0
  25. package/lib/src/generated/sdk-version.js +3 -0
  26. package/lib/src/index.d.ts +8 -0
  27. package/lib/src/index.js +8 -0
  28. package/lib/src/ledger.d.ts +188 -0
  29. package/lib/src/ledger.js +849 -0
  30. package/lib/src/ledger.test.d.ts +1 -0
  31. package/lib/src/ledger.test.js +23 -0
  32. package/lib/src/logger.d.ts +41 -0
  33. package/lib/src/logger.js +56 -0
  34. package/lib/src/multistream.d.ts +47 -0
  35. package/lib/src/multistream.js +123 -0
  36. package/lib/src/translate.d.ts +5 -0
  37. package/lib/src/translate.js +30 -0
  38. package/lib/src/types.d.ts +201 -0
  39. package/lib/src/types.js +1 -0
  40. package/lib/src/util.d.ts +3 -0
  41. package/lib/src/util.js +7 -0
  42. package/lib/src/validation.d.ts +27 -0
  43. package/lib/src/validation.js +182 -0
  44. package/lib/src/valueTypes.d.ts +34 -0
  45. package/lib/src/valueTypes.js +76 -0
  46. package/lib/src/websocket.d.ts +69 -0
  47. package/lib/src/websocket.js +125 -0
  48. package/lib/tsconfig.tsbuildinfo +1 -0
  49. package/lib-lite/scripts/build.d.ts +9 -0
  50. package/lib-lite/scripts/build.js +366 -0
  51. package/lib-lite/scripts/enhance-types.d.ts +3 -0
  52. package/lib-lite/scripts/enhance-types.js +174 -0
  53. package/lib-lite/scripts/generate-asyncapi-types.d.ts +9 -0
  54. package/lib-lite/scripts/generate-asyncapi-types.js +129 -0
  55. package/lib-lite/scripts/generate-schema-modules.d.ts +3 -0
  56. package/lib-lite/scripts/generate-schema-modules.js +33 -0
  57. package/lib-lite/src/TemplateEmitterMap.d.ts +40 -0
  58. package/lib-lite/src/TemplateEmitterMap.js +57 -0
  59. package/lib-lite/src/client.d.ts +55 -0
  60. package/lib-lite/src/client.js +62 -0
  61. package/lib-lite/src/generated/api.d.ts +7147 -0
  62. package/lib-lite/src/generated/api.js +1 -0
  63. package/lib-lite/src/generated/async-api.d.ts +1665 -0
  64. package/lib-lite/src/generated/async-api.js +1 -0
  65. package/lib-lite/src/generated/asyncapi-schema.d.ts +1 -0
  66. package/lib-lite/src/generated/asyncapi-schema.js +2 -0
  67. package/lib-lite/src/generated/openapi-schema.d.ts +1 -0
  68. package/lib-lite/src/generated/openapi-schema.js +2 -0
  69. package/lib-lite/src/generated/sdk-version.d.ts +1 -0
  70. package/lib-lite/src/generated/sdk-version.js +3 -0
  71. package/lib-lite/src/index.d.ts +8 -0
  72. package/lib-lite/src/index.js +8 -0
  73. package/lib-lite/src/ledger.d.ts +188 -0
  74. package/lib-lite/src/ledger.js +849 -0
  75. package/lib-lite/src/ledger.test.d.ts +1 -0
  76. package/lib-lite/src/ledger.test.js +23 -0
  77. package/lib-lite/src/logger.d.ts +41 -0
  78. package/lib-lite/src/logger.js +56 -0
  79. package/lib-lite/src/multistream.d.ts +47 -0
  80. package/lib-lite/src/multistream.js +123 -0
  81. package/lib-lite/src/translate.d.ts +5 -0
  82. package/lib-lite/src/translate.js +30 -0
  83. package/lib-lite/src/types.d.ts +201 -0
  84. package/lib-lite/src/types.js +1 -0
  85. package/lib-lite/src/util.d.ts +3 -0
  86. package/lib-lite/src/util.js +7 -0
  87. package/lib-lite/src/validation.d.ts +14 -0
  88. package/lib-lite/src/validation.js +31 -0
  89. package/lib-lite/src/valueTypes.d.ts +34 -0
  90. package/lib-lite/src/valueTypes.js +76 -0
  91. package/lib-lite/src/websocket.d.ts +69 -0
  92. package/lib-lite/src/websocket.js +125 -0
  93. package/lib-lite/tsconfig.temp.tsbuildinfo +1 -0
  94. package/package.json +72 -0
  95. package/scripts/build.ts +456 -0
  96. package/scripts/enhance-types.ts +223 -0
  97. package/scripts/generate-asyncapi-types.ts +158 -0
  98. package/scripts/generate-schema-modules.ts +52 -0
@@ -0,0 +1,1665 @@
1
+ import { LedgerString, PartyIdString, UserIdString, NameString, PackageIdString } from "../valueTypes.js";
2
+ /**
3
+ * This file was auto-generated by openapi-typescript.
4
+ * Do not make direct changes to the file.
5
+ */
6
+ export type paths = Record<string, never>;
7
+ export type webhooks = Record<string, never>;
8
+ export interface components {
9
+ schemas: {
10
+ /** JsCantonError */
11
+ JsCantonError: {
12
+ code: string;
13
+ cause: string;
14
+ correlationId?: string;
15
+ traceId?: string;
16
+ context: components["schemas"]["Map_String"];
17
+ resources?: components["schemas"]["Tuple2_String_String"][];
18
+ /** Format: int32 */
19
+ errorCategory: number;
20
+ /** Format: int32 */
21
+ grpcCodeValue?: number;
22
+ retryInfo?: string;
23
+ definiteAnswer?: boolean;
24
+ };
25
+ /** Map_String */
26
+ Map_String: {
27
+ [key: string]: string;
28
+ };
29
+ /** Tuple2_String_String */
30
+ Tuple2_String_String: [
31
+ string,
32
+ string
33
+ ];
34
+ /** CompletionStreamRequest */
35
+ CompletionStreamRequest: {
36
+ /**
37
+ * @description Only completions of commands submitted with the same user_id will be visible in the stream.
38
+ * Must be a valid UserIdString (as described in ``value.proto``).
39
+ * Required unless authentication is used with a user token.
40
+ * In that case, the token's user-id will be used for the request's user_id.
41
+ */
42
+ userId: UserIdString;
43
+ /**
44
+ * @description Non-empty list of parties whose data should be included.
45
+ * The stream shows only completions of commands for which at least one of the ``act_as`` parties is in the given set of parties.
46
+ * Must be a valid PartyIdString (as described in ``value.proto``).
47
+ * Required
48
+ */
49
+ parties?: PartyIdString[];
50
+ /**
51
+ * Format: int64
52
+ * @description This optional field indicates the minimum offset for completions. This can be used to resume an earlier completion stream.
53
+ * If not set the ledger uses the ledger begin offset instead.
54
+ * If specified, it must be a valid absolute offset (positive integer) or zero (ledger begin offset).
55
+ * If the ledger has been pruned, this parameter must be specified and greater than the pruning offset.
56
+ */
57
+ beginExclusive: number;
58
+ };
59
+ /** Either_JsCantonError_CompletionStreamResponse */
60
+ Either_JsCantonError_CompletionStreamResponse: components["schemas"]["CompletionStreamResponse"] | components["schemas"]["JsCantonError"];
61
+ /** Map_K_V */
62
+ Map_K_V: {
63
+ [key: string]: string;
64
+ };
65
+ /** CompletionStreamResponse */
66
+ CompletionStreamResponse: {
67
+ completionResponse: components["schemas"]["CompletionResponse"];
68
+ };
69
+ /** CompletionResponse */
70
+ CompletionResponse: {
71
+ Completion: components["schemas"]["Completion"];
72
+ } | {
73
+ Empty: components["schemas"]["Empty1"];
74
+ } | {
75
+ OffsetCheckpoint: components["schemas"]["OffsetCheckpoint"];
76
+ };
77
+ /**
78
+ * Completion
79
+ * @description A completion represents the status of a submitted command on the ledger: it can be successful or failed.
80
+ */
81
+ Completion: {
82
+ value: components["schemas"]["Completion1"];
83
+ };
84
+ /**
85
+ * Completion
86
+ * @description A completion represents the status of a submitted command on the ledger: it can be successful or failed.
87
+ */
88
+ Completion1: {
89
+ /**
90
+ * @description The ID of the succeeded or failed command.
91
+ * Must be a valid LedgerString (as described in ``value.proto``).
92
+ * Required
93
+ */
94
+ commandId: LedgerString;
95
+ /**
96
+ * @description Identifies the exact type of the error.
97
+ * It uses the same format of conveying error details as it is used for the RPC responses of the APIs.
98
+ * Optional
99
+ */
100
+ status?: components["schemas"]["JsStatus"];
101
+ /**
102
+ * @description The update_id of the transaction or reassignment that resulted from the command with command_id.
103
+ * Only set for successfully executed commands.
104
+ * Must be a valid LedgerString (as described in ``value.proto``).
105
+ */
106
+ updateId: LedgerString;
107
+ /**
108
+ * @description The user-id that was used for the submission, as described in ``commands.proto``.
109
+ * Must be a valid UserIdString (as described in ``value.proto``).
110
+ * Optional for historic completions where this data is not available.
111
+ */
112
+ userId: UserIdString;
113
+ /**
114
+ * @description The set of parties on whose behalf the commands were executed.
115
+ * Contains the ``act_as`` parties from ``commands.proto``
116
+ * filtered to the requesting parties in CompletionStreamRequest.
117
+ * The order of the parties need not be the same as in the submission.
118
+ * Each element must be a valid PartyIdString (as described in ``value.proto``).
119
+ * Optional for historic completions where this data is not available.
120
+ */
121
+ actAs?: string[];
122
+ /**
123
+ * @description The submission ID this completion refers to, as described in ``commands.proto``.
124
+ * Must be a valid LedgerString (as described in ``value.proto``).
125
+ * Optional
126
+ */
127
+ submissionId: LedgerString;
128
+ deduplicationPeriod: components["schemas"]["DeduplicationPeriod"];
129
+ /**
130
+ * @description Optional; ledger API trace context
131
+ *
132
+ * The trace context transported in this message corresponds to the trace context supplied
133
+ * by the client application in a HTTP2 header of the original command submission.
134
+ * We typically use a header to transfer this type of information. Here we use message
135
+ * body, because it is used in gRPC streams which do not support per message headers.
136
+ * This field will be populated with the trace context contained in the original submission.
137
+ * If that was not provided, a unique ledger-api-server generated trace context will be used
138
+ * instead.
139
+ */
140
+ traceContext?: components["schemas"]["TraceContext"];
141
+ /**
142
+ * Format: int64
143
+ * @description May be used in a subsequent CompletionStreamRequest to resume the consumption of this stream at a later time.
144
+ * Required, must be a valid absolute offset (positive integer).
145
+ */
146
+ offset: number;
147
+ /**
148
+ * @description The synchronizer along with its record time.
149
+ * The synchronizer id provided, in case of
150
+ *
151
+ * - successful/failed transactions: identifies the synchronizer of the transaction
152
+ * - for successful/failed unassign commands: identifies the source synchronizer
153
+ * - for successful/failed assign commands: identifies the target synchronizer
154
+ *
155
+ * Required
156
+ */
157
+ synchronizerTime?: components["schemas"]["SynchronizerTime"];
158
+ };
159
+ /** JsStatus */
160
+ JsStatus: {
161
+ /** Format: int32 */
162
+ code: number;
163
+ message: string;
164
+ details?: components["schemas"]["ProtoAny"][];
165
+ };
166
+ /** ProtoAny */
167
+ ProtoAny: {
168
+ typeUrl: string;
169
+ value: string;
170
+ unknownFields: components["schemas"]["UnknownFieldSet"];
171
+ valueDecoded?: string;
172
+ };
173
+ /** UnknownFieldSet */
174
+ UnknownFieldSet: {
175
+ fields: components["schemas"]["Map_Int_Field"];
176
+ };
177
+ /** Map_Int_Field */
178
+ Map_Int_Field: {
179
+ [key: string]: components["schemas"]["Field"];
180
+ };
181
+ /** Field */
182
+ Field: {
183
+ varint?: number[];
184
+ fixed64?: number[];
185
+ fixed32?: number[];
186
+ lengthDelimited?: string[];
187
+ };
188
+ /** DeduplicationPeriod */
189
+ DeduplicationPeriod: {
190
+ DeduplicationDuration: components["schemas"]["DeduplicationDuration"];
191
+ } | {
192
+ DeduplicationOffset: components["schemas"]["DeduplicationOffset"];
193
+ } | {
194
+ Empty: components["schemas"]["Empty"];
195
+ };
196
+ /** DeduplicationDuration */
197
+ DeduplicationDuration: {
198
+ value: components["schemas"]["Duration"];
199
+ };
200
+ /** Duration */
201
+ Duration: {
202
+ /** Format: int64 */
203
+ seconds: number;
204
+ /** Format: int32 */
205
+ nanos: number;
206
+ /** @description This field is automatically added as part of protobuf to json mapping */
207
+ unknownFields?: components["schemas"]["UnknownFieldSet"];
208
+ };
209
+ /** DeduplicationOffset */
210
+ DeduplicationOffset: {
211
+ /** Format: int64 */
212
+ value: number;
213
+ };
214
+ /** Empty */
215
+ Empty: Record<string, never>;
216
+ /** TraceContext */
217
+ TraceContext: {
218
+ /** @description https://www.w3.org/TR/trace-context/ */
219
+ traceparent?: string;
220
+ tracestate?: string;
221
+ };
222
+ /** SynchronizerTime */
223
+ SynchronizerTime: {
224
+ /**
225
+ * @description The id of the synchronizer.
226
+ * Required
227
+ */
228
+ synchronizerId: string;
229
+ /**
230
+ * @description All commands with a maximum record time below this value MUST be considered lost if their completion has not arrived before this checkpoint.
231
+ * Required
232
+ */
233
+ recordTime?: string;
234
+ };
235
+ /** Empty */
236
+ Empty1: Record<string, never>;
237
+ /**
238
+ * OffsetCheckpoint
239
+ * @description OffsetCheckpoints may be used to:
240
+ *
241
+ * - detect time out of commands.
242
+ * - provide an offset which can be used to restart consumption.
243
+ */
244
+ OffsetCheckpoint: {
245
+ value: components["schemas"]["OffsetCheckpoint1"];
246
+ };
247
+ /**
248
+ * OffsetCheckpoint
249
+ * @description OffsetCheckpoints may be used to:
250
+ *
251
+ * - detect time out of commands.
252
+ * - provide an offset which can be used to restart consumption.
253
+ */
254
+ OffsetCheckpoint1: {
255
+ /**
256
+ * Format: int64
257
+ * @description The participant's offset, the details of the offset field are described in ``community/ledger-api/README.md``.
258
+ * Required, must be a valid absolute offset (positive integer).
259
+ */
260
+ offset: number;
261
+ synchronizerTimes?: components["schemas"]["SynchronizerTime"][];
262
+ };
263
+ /**
264
+ * GetActiveContractsRequest
265
+ * @description If the given offset is different than the ledger end, and there are (un)assignments in-flight at the given offset,
266
+ * the snapshot may fail with "FAILED_PRECONDITION/PARTICIPANT_PRUNED_DATA_ACCESSED".
267
+ * Note that it is ok to request acs snapshots for party migration with offsets other than ledger end, because party
268
+ * migration is not concerned with incomplete (un)assignments.
269
+ */
270
+ GetActiveContractsRequest: {
271
+ /**
272
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
273
+ * Templates to include in the served snapshot, per party.
274
+ * Optional, if specified event_format must be unset, if not specified event_format must be set.
275
+ */
276
+ filter?: components["schemas"]["TransactionFilter"];
277
+ /**
278
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
279
+ * If enabled, values served over the API will contain more information than strictly necessary to interpret the data.
280
+ * In particular, setting the verbose flag to true triggers the ledger to include labels for record fields.
281
+ * Optional, if specified event_format must be unset.
282
+ */
283
+ verbose: boolean;
284
+ /**
285
+ * Format: int64
286
+ * @description The offset at which the snapshot of the active contracts will be computed.
287
+ * Must be no greater than the current ledger end offset.
288
+ * Must be greater than or equal to the last pruning offset.
289
+ * Required, must be a valid absolute offset (positive integer) or ledger begin offset (zero).
290
+ * If zero, the empty set will be returned.
291
+ */
292
+ activeAtOffset: number;
293
+ /**
294
+ * @description Format of the contract_entries in the result. In case of CreatedEvent the presentation will be of
295
+ * TRANSACTION_SHAPE_ACS_DELTA.
296
+ * Optional for backwards compatibility, defaults to an EventFormat where:
297
+ *
298
+ * - filters_by_party is the filter.filters_by_party from this request
299
+ * - filters_for_any_party is the filter.filters_for_any_party from this request
300
+ * - verbose is the verbose field from this request
301
+ */
302
+ eventFormat?: components["schemas"]["EventFormat"];
303
+ };
304
+ /**
305
+ * TransactionFilter
306
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
307
+ * Used both for filtering create and archive events as well as for filtering transaction trees.
308
+ */
309
+ TransactionFilter: {
310
+ /**
311
+ * @description Each key must be a valid PartyIdString (as described in ``value.proto``).
312
+ * The interpretation of the filter depends on the transaction-shape being filtered:
313
+ *
314
+ * 1. For **transaction trees** (used in GetUpdateTreesResponse for backwards compatibility) all party keys used as
315
+ * wildcard filters, and all subtrees whose root has one of the listed parties as an informee are returned.
316
+ * If there are ``CumulativeFilter``s, those will control returned ``CreatedEvent`` fields where applicable, but will
317
+ * not be used for template/interface filtering.
318
+ * 2. For **ledger-effects** create and exercise events are returned, for which the witnesses include at least one of
319
+ * the listed parties and match the per-party filter.
320
+ * 3. For **transaction and active-contract-set streams** create and archive events are returned for all contracts whose
321
+ * stakeholders include at least one of the listed parties and match the per-party filter.
322
+ */
323
+ filtersByParty: components["schemas"]["Map_Filters"];
324
+ /**
325
+ * @description Wildcard filters that apply to all the parties existing on the participant. The interpretation of the filters is the same
326
+ * with the per-party filter as described above.
327
+ */
328
+ filtersForAnyParty?: components["schemas"]["Filters"];
329
+ };
330
+ /** Map_Filters */
331
+ Map_Filters: {
332
+ [key: string]: components["schemas"]["Filters"];
333
+ };
334
+ /**
335
+ * Filters
336
+ * @description The union of a set of template filters, interface filters, or a wildcard.
337
+ */
338
+ Filters: {
339
+ /**
340
+ * @description Every filter in the cumulative list expands the scope of the resulting stream. Each interface,
341
+ * template or wildcard filter means additional events that will match the query.
342
+ * The impact of include_interface_view and include_created_event_blob fields in the filters will
343
+ * also be accumulated.
344
+ * A template or an interface SHOULD NOT appear twice in the accumulative field.
345
+ * A wildcard filter SHOULD NOT be defined more than once in the accumulative field.
346
+ * Optional, if no ``CumulativeFilter`` defined, the default of a single ``WildcardFilter`` with
347
+ * include_created_event_blob unset is used.
348
+ */
349
+ cumulative?: components["schemas"]["CumulativeFilter"][];
350
+ };
351
+ /**
352
+ * CumulativeFilter
353
+ * @description A filter that matches all contracts that are either an instance of one of
354
+ * the ``template_filters`` or that match one of the ``interface_filters``.
355
+ */
356
+ CumulativeFilter: {
357
+ identifierFilter: components["schemas"]["IdentifierFilter"];
358
+ };
359
+ /** IdentifierFilter */
360
+ IdentifierFilter: {
361
+ Empty: components["schemas"]["Empty2"];
362
+ } | {
363
+ InterfaceFilter: components["schemas"]["InterfaceFilter"];
364
+ } | {
365
+ TemplateFilter: components["schemas"]["TemplateFilter"];
366
+ } | {
367
+ WildcardFilter: components["schemas"]["WildcardFilter"];
368
+ };
369
+ /** Empty */
370
+ Empty2: Record<string, never>;
371
+ /**
372
+ * InterfaceFilter
373
+ * @description This filter matches contracts that implement a specific interface.
374
+ */
375
+ InterfaceFilter: {
376
+ value: components["schemas"]["InterfaceFilter1"];
377
+ };
378
+ /**
379
+ * InterfaceFilter
380
+ * @description This filter matches contracts that implement a specific interface.
381
+ */
382
+ InterfaceFilter1: {
383
+ /**
384
+ * @description The interface that a matching contract must implement.
385
+ * The ``interface_id`` needs to be valid: corresponding interface should be defined in
386
+ * one of the available packages at the time of the query.
387
+ * Both package-name and package-id reference formats for the identifier are supported.
388
+ * Note: The package-id reference identifier format is deprecated. We plan to end support for this format in version 3.4.
389
+ *
390
+ * Required
391
+ */
392
+ interfaceId?: string;
393
+ /**
394
+ * @description Whether to include the interface view on the contract in the returned ``CreatedEvent``.
395
+ * Use this to access contract data in a uniform manner in your API client.
396
+ * Optional
397
+ */
398
+ includeInterfaceView: boolean;
399
+ /**
400
+ * @description Whether to include a ``created_event_blob`` in the returned ``CreatedEvent``.
401
+ * Use this to access the contract create event payload in your API client
402
+ * for submitting it as a disclosed contract with future commands.
403
+ * Optional
404
+ */
405
+ includeCreatedEventBlob: boolean;
406
+ };
407
+ /**
408
+ * TemplateFilter
409
+ * @description This filter matches contracts of a specific template.
410
+ */
411
+ TemplateFilter: {
412
+ value: components["schemas"]["TemplateFilter1"];
413
+ };
414
+ /**
415
+ * TemplateFilter
416
+ * @description This filter matches contracts of a specific template.
417
+ */
418
+ TemplateFilter1: {
419
+ /**
420
+ * @description A template for which the payload should be included in the response.
421
+ * The ``template_id`` needs to be valid: corresponding template should be defined in
422
+ * one of the available packages at the time of the query.
423
+ * Both package-name and package-id reference formats for the identifier are supported.
424
+ * Note: The package-id reference identifier format is deprecated. We plan to end support for this format in version 3.4.
425
+ *
426
+ * Required
427
+ */
428
+ templateId?: string;
429
+ /**
430
+ * @description Whether to include a ``created_event_blob`` in the returned ``CreatedEvent``.
431
+ * Use this to access the contract event payload in your API client
432
+ * for submitting it as a disclosed contract with future commands.
433
+ * Optional
434
+ */
435
+ includeCreatedEventBlob: boolean;
436
+ };
437
+ /**
438
+ * WildcardFilter
439
+ * @description This filter matches all templates.
440
+ */
441
+ WildcardFilter: {
442
+ value: components["schemas"]["WildcardFilter1"];
443
+ };
444
+ /**
445
+ * WildcardFilter
446
+ * @description This filter matches all templates.
447
+ */
448
+ WildcardFilter1: {
449
+ /**
450
+ * @description Whether to include a ``created_event_blob`` in the returned ``CreatedEvent``.
451
+ * Use this to access the contract create event payload in your API client
452
+ * for submitting it as a disclosed contract with future commands.
453
+ * Optional
454
+ */
455
+ includeCreatedEventBlob: boolean;
456
+ };
457
+ /**
458
+ * EventFormat
459
+ * @description A format for events which defines both which events should be included
460
+ * and what data should be computed and included for them.
461
+ *
462
+ * Note that some of the filtering behavior depends on the `TransactionShape`,
463
+ * which is expected to be specified alongside usages of `EventFormat`.
464
+ */
465
+ EventFormat: {
466
+ /**
467
+ * @description Each key must be a valid PartyIdString (as described in ``value.proto``).
468
+ * The interpretation of the filter depends on the transaction-shape being filtered:
469
+ *
470
+ * 1. For **ledger-effects** create and exercise events are returned, for which the witnesses include at least one of
471
+ * the listed parties and match the per-party filter.
472
+ * 2. For **transaction and active-contract-set streams** create and archive events are returned for all contracts whose
473
+ * stakeholders include at least one of the listed parties and match the per-party filter.
474
+ *
475
+ * Optional
476
+ */
477
+ filtersByParty: components["schemas"]["Map_Filters"];
478
+ /**
479
+ * @description Wildcard filters that apply to all the parties existing on the participant. The interpretation of the filters is the same
480
+ * with the per-party filter as described above.
481
+ * Optional
482
+ */
483
+ filtersForAnyParty?: components["schemas"]["Filters"];
484
+ /**
485
+ * @description If enabled, values served over the API will contain more information than strictly necessary to interpret the data.
486
+ * In particular, setting the verbose flag to true triggers the ledger to include labels for record fields.
487
+ * Optional
488
+ */
489
+ verbose: boolean;
490
+ };
491
+ /** Either_JsCantonError_JsGetActiveContractsResponse */
492
+ Either_JsCantonError_JsGetActiveContractsResponse: components["schemas"]["JsCantonError"] | components["schemas"]["JsGetActiveContractsResponse"];
493
+ /** JsGetActiveContractsResponse */
494
+ JsGetActiveContractsResponse: {
495
+ /**
496
+ * @description The workflow ID used in command submission which corresponds to the contract_entry. Only set if
497
+ * the ``workflow_id`` for the command was set.
498
+ * Must be a valid LedgerString (as described in ``value.proto``).
499
+ * Optional
500
+ */
501
+ workflowId: LedgerString;
502
+ contractEntry: components["schemas"]["JsContractEntry"];
503
+ };
504
+ /** JsContractEntry */
505
+ JsContractEntry: {
506
+ JsActiveContract: components["schemas"]["JsActiveContract"];
507
+ } | {
508
+ JsEmpty: components["schemas"]["JsEmpty"];
509
+ } | {
510
+ JsIncompleteAssigned: components["schemas"]["JsIncompleteAssigned"];
511
+ } | {
512
+ JsIncompleteUnassigned: components["schemas"]["JsIncompleteUnassigned"];
513
+ };
514
+ /** JsActiveContract */
515
+ JsActiveContract: {
516
+ /**
517
+ * @description Required
518
+ * The event as it appeared in the context of its last update (i.e. daml transaction or
519
+ * reassignment). In particular, the last offset, node_id pair is preserved.
520
+ * The last update is the most recent update created or assigned this contract on synchronizer_id synchronizer.
521
+ * The offset of the CreatedEvent might point to an already pruned update, therefore it cannot necessarily be used
522
+ * for lookups.
523
+ */
524
+ createdEvent: components["schemas"]["CreatedEvent"];
525
+ /**
526
+ * @description A valid synchronizer id
527
+ * Required
528
+ */
529
+ synchronizerId: string;
530
+ /**
531
+ * Format: int64
532
+ * @description Each corresponding assigned and unassigned event has the same reassignment_counter. This strictly increases
533
+ * with each unassign command for the same contract. Creation of the contract corresponds to reassignment_counter
534
+ * equals zero.
535
+ * This field will be the reassignment_counter of the latest observable activation event on this synchronizer, which is
536
+ * before the active_at_offset.
537
+ * Required
538
+ */
539
+ reassignmentCounter: number;
540
+ };
541
+ /**
542
+ * CreatedEvent
543
+ * @description Records that a contract has been created, and choices may now be exercised on it.
544
+ */
545
+ CreatedEvent: {
546
+ /**
547
+ * Format: int64
548
+ * @description The offset of origin, which has contextual meaning, please see description at messages that include a CreatedEvent.
549
+ * Offsets are managed by the participant nodes.
550
+ * Transactions can thus NOT be assumed to have the same offsets on different participant nodes.
551
+ * Required, it is a valid absolute offset (positive integer)
552
+ */
553
+ offset: number;
554
+ /**
555
+ * Format: int32
556
+ * @description The position of this event in the originating transaction or reassignment.
557
+ * The origin has contextual meaning, please see description at messages that include a CreatedEvent.
558
+ * Node IDs are not necessarily equal across participants,
559
+ * as these may see different projections/parts of transactions.
560
+ * Required, must be valid node ID (non-negative integer)
561
+ */
562
+ nodeId: number;
563
+ /**
564
+ * @description The ID of the created contract.
565
+ * Must be a valid LedgerString (as described in ``value.proto``).
566
+ * Required
567
+ */
568
+ contractId: LedgerString;
569
+ /**
570
+ * @description The template of the created contract.
571
+ * The identifier uses the package-id reference format.
572
+ *
573
+ * Required
574
+ */
575
+ templateId: PackageIdString;
576
+ /**
577
+ * @description The key of the created contract.
578
+ * This will be set if and only if ``template_id`` defines a contract key.
579
+ * Optional
580
+ */
581
+ contractKey?: unknown;
582
+ createArgument?: unknown;
583
+ /**
584
+ * @description Opaque representation of contract create event payload intended for forwarding
585
+ * to an API server as a contract disclosed as part of a command
586
+ * submission.
587
+ * Optional
588
+ */
589
+ createdEventBlob: string;
590
+ /**
591
+ * @description Interface views specified in the transaction filter.
592
+ * Includes an ``InterfaceView`` for each interface for which there is a ``InterfaceFilter`` with
593
+ *
594
+ * - its party in the ``witness_parties`` of this event,
595
+ * - and which is implemented by the template of this event,
596
+ * - and which has ``include_interface_view`` set.
597
+ *
598
+ * Optional
599
+ */
600
+ interfaceViews?: components["schemas"]["JsInterfaceView"][];
601
+ /**
602
+ * @description The parties that are notified of this event. When a ``CreatedEvent``
603
+ * is returned as part of a transaction tree or ledger-effects transaction, this will include all
604
+ * the parties specified in the ``TransactionFilter`` that are witnesses of the event
605
+ * (the stakeholders of the contract and all informees of all the ancestors
606
+ * of this create action that this participant knows about).
607
+ * If served as part of a ACS delta transaction those will
608
+ * be limited to all parties specified in the ``TransactionFilter`` that
609
+ * are stakeholders of the contract (i.e. either signatories or observers).
610
+ * If the ``CreatedEvent`` is returned as part of an AssignedEvent,
611
+ * ActiveContract or IncompleteUnassigned (so the event is related to
612
+ * an assignment or unassignment): this will include all parties of the
613
+ * ``TransactionFilter`` that are stakeholders of the contract.
614
+ *
615
+ * The behavior of reading create events visible to parties not hosted
616
+ * on the participant node serving the Ledger API is undefined. Concretely,
617
+ * there is neither a guarantee that the participant node will serve all their
618
+ * create events on the ACS stream, nor is there a guarantee that matching archive
619
+ * events are delivered for such create events.
620
+ *
621
+ * For most clients this is not a problem, as they only read events for parties
622
+ * that are hosted on the participant node. If you need to read events
623
+ * for parties that may not be hosted at all times on the participant node,
624
+ * subscribe to the ``TopologyEvent``s for that party by setting a corresponding
625
+ * ``UpdateFormat``. Using these events, query the ACS as-of an offset where the
626
+ * party is hosted on the participant node, and ignore create events at offsets
627
+ * where the party is not hosted on the participant node.
628
+ * Required
629
+ */
630
+ witnessParties?: string[];
631
+ /**
632
+ * @description The signatories for this contract as specified by the template.
633
+ * Required
634
+ */
635
+ signatories?: string[];
636
+ /**
637
+ * @description The observers for this contract as specified explicitly by the template or implicitly as choice controllers.
638
+ * This field never contains parties that are signatories.
639
+ * Required
640
+ */
641
+ observers?: string[];
642
+ /**
643
+ * @description Ledger effective time of the transaction that created the contract.
644
+ * Required
645
+ */
646
+ createdAt: string;
647
+ /**
648
+ * @description The package name of the created contract.
649
+ * Required
650
+ */
651
+ packageName: string;
652
+ /**
653
+ * @description A package-id present in the participant package store that typechecks the contract's argument.
654
+ * This may differ from the package-id of the template used to create the contract.
655
+ * For contracts created before Canton 3.4, this field matches the contract's creation package-id.
656
+ *
657
+ * NOTE: Experimental, server internal concept, not for client consumption. Subject to change without notice.
658
+ *
659
+ * Required
660
+ */
661
+ representativePackageId: string;
662
+ /**
663
+ * @description Whether this event would be part of respective ACS_DELTA shaped stream,
664
+ * and should therefore considered when tracking contract activeness on the client-side.
665
+ * Required
666
+ */
667
+ acsDelta: boolean;
668
+ };
669
+ /**
670
+ * JsInterfaceView
671
+ * @description View of a create event matched by an interface filter.
672
+ */
673
+ JsInterfaceView: {
674
+ /**
675
+ * @description The interface implemented by the matched event.
676
+ * The identifier uses the package-id reference format.
677
+ *
678
+ * Required
679
+ */
680
+ interfaceId: PackageIdString;
681
+ /**
682
+ * @description Whether the view was successfully computed, and if not,
683
+ * the reason for the error. The error is reported using the same rules
684
+ * for error codes and messages as the errors returned for API requests.
685
+ * Required
686
+ */
687
+ viewStatus: components["schemas"]["JsStatus"];
688
+ /**
689
+ * @description The value of the interface's view method on this event.
690
+ * Set if it was requested in the ``InterfaceFilter`` and it could be
691
+ * successfully computed.
692
+ * Optional
693
+ */
694
+ viewValue?: unknown;
695
+ };
696
+ /** JsEmpty */
697
+ JsEmpty: Record<string, never>;
698
+ /** JsIncompleteAssigned */
699
+ JsIncompleteAssigned: {
700
+ /** @description Required */
701
+ assignedEvent: components["schemas"]["JsAssignedEvent"];
702
+ };
703
+ /**
704
+ * JsAssignedEvent
705
+ * @description Records that a contract has been assigned, and it can be used on the target synchronizer.
706
+ */
707
+ JsAssignedEvent: {
708
+ /**
709
+ * @description The ID of the source synchronizer.
710
+ * Must be a valid synchronizer id.
711
+ * Required
712
+ */
713
+ source: string;
714
+ /**
715
+ * @description The ID of the target synchronizer.
716
+ * Must be a valid synchronizer id.
717
+ * Required
718
+ */
719
+ target: string;
720
+ /**
721
+ * @description The ID from the unassigned event.
722
+ * For correlation capabilities.
723
+ * Must be a valid LedgerString (as described in ``value.proto``).
724
+ * Required
725
+ */
726
+ reassignmentId: LedgerString;
727
+ /**
728
+ * @description Party on whose behalf the assign command was executed.
729
+ * Empty if the assignment happened offline via the repair service.
730
+ * Must be a valid PartyIdString (as described in ``value.proto``).
731
+ * Optional
732
+ */
733
+ submitter: PartyIdString;
734
+ /**
735
+ * Format: int64
736
+ * @description Each corresponding assigned and unassigned event has the same reassignment_counter. This strictly increases
737
+ * with each unassign command for the same contract. Creation of the contract corresponds to reassignment_counter
738
+ * equals zero.
739
+ * Required
740
+ */
741
+ reassignmentCounter: number;
742
+ /**
743
+ * @description Required
744
+ * The offset of this event refers to the offset of the assignment,
745
+ * while the node_id is the index of within the batch.
746
+ */
747
+ createdEvent: components["schemas"]["CreatedEvent"];
748
+ };
749
+ /** JsIncompleteUnassigned */
750
+ JsIncompleteUnassigned: {
751
+ /**
752
+ * @description Required
753
+ * The event as it appeared in the context of its last activation update (i.e. daml transaction or
754
+ * reassignment). In particular, the last activation offset, node_id pair is preserved.
755
+ * The last activation update is the most recent update created or assigned this contract on synchronizer_id synchronizer before
756
+ * the unassigned_event.
757
+ * The offset of the CreatedEvent might point to an already pruned update, therefore it cannot necessarily be used
758
+ * for lookups.
759
+ */
760
+ createdEvent: components["schemas"]["CreatedEvent"];
761
+ /** @description Required */
762
+ unassignedEvent: components["schemas"]["UnassignedEvent"];
763
+ };
764
+ /**
765
+ * UnassignedEvent
766
+ * @description Records that a contract has been unassigned, and it becomes unusable on the source synchronizer
767
+ */
768
+ UnassignedEvent: {
769
+ /**
770
+ * @description The ID of the unassignment. This needs to be used as an input for a assign ReassignmentCommand.
771
+ * Must be a valid LedgerString (as described in ``value.proto``).
772
+ * Required
773
+ */
774
+ reassignmentId: LedgerString;
775
+ /**
776
+ * @description The ID of the reassigned contract.
777
+ * Must be a valid LedgerString (as described in ``value.proto``).
778
+ * Required
779
+ */
780
+ contractId: LedgerString;
781
+ /**
782
+ * @description The template of the reassigned contract.
783
+ * The identifier uses the package-id reference format.
784
+ *
785
+ * Required
786
+ */
787
+ templateId?: PackageIdString;
788
+ /**
789
+ * @description The ID of the source synchronizer
790
+ * Must be a valid synchronizer id
791
+ * Required
792
+ */
793
+ source: string;
794
+ /**
795
+ * @description The ID of the target synchronizer
796
+ * Must be a valid synchronizer id
797
+ * Required
798
+ */
799
+ target: string;
800
+ /**
801
+ * @description Party on whose behalf the unassign command was executed.
802
+ * Empty if the unassignment happened offline via the repair service.
803
+ * Must be a valid PartyIdString (as described in ``value.proto``).
804
+ * Optional
805
+ */
806
+ submitter: PartyIdString;
807
+ /**
808
+ * Format: int64
809
+ * @description Each corresponding assigned and unassigned event has the same reassignment_counter. This strictly increases
810
+ * with each unassign command for the same contract. Creation of the contract corresponds to reassignment_counter
811
+ * equals zero.
812
+ * Required
813
+ */
814
+ reassignmentCounter: number;
815
+ /**
816
+ * @description Assignment exclusivity
817
+ * Before this time (measured on the target synchronizer), only the submitter of the unassignment can initiate the assignment
818
+ * Defined for reassigning participants.
819
+ * Optional
820
+ */
821
+ assignmentExclusivity?: string;
822
+ /**
823
+ * @description The parties that are notified of this event.
824
+ * Required
825
+ */
826
+ witnessParties?: string[];
827
+ /**
828
+ * @description The package name of the contract.
829
+ * Required
830
+ */
831
+ packageName: string;
832
+ /**
833
+ * Format: int64
834
+ * @description The offset of origin.
835
+ * Offsets are managed by the participant nodes.
836
+ * Reassignments can thus NOT be assumed to have the same offsets on different participant nodes.
837
+ * Required, it is a valid absolute offset (positive integer)
838
+ */
839
+ offset: number;
840
+ /**
841
+ * Format: int32
842
+ * @description The position of this event in the originating reassignment.
843
+ * Node IDs are not necessarily equal across participants,
844
+ * as these may see different projections/parts of reassignments.
845
+ * Required, must be valid node ID (non-negative integer)
846
+ */
847
+ nodeId: number;
848
+ };
849
+ /** GetUpdatesRequest */
850
+ GetUpdatesRequest: {
851
+ /**
852
+ * Format: int64
853
+ * @description Beginning of the requested ledger section (non-negative integer).
854
+ * The response will only contain transactions whose offset is strictly greater than this.
855
+ * If zero, the stream will start from the beginning of the ledger.
856
+ * If positive, the streaming will start after this absolute offset.
857
+ * If the ledger has been pruned, this parameter must be specified and be greater than the pruning offset.
858
+ */
859
+ beginExclusive: number;
860
+ /**
861
+ * Format: int64
862
+ * @description End of the requested ledger section.
863
+ * The response will only contain transactions whose offset is less than or equal to this.
864
+ * Optional, if empty, the stream will not terminate.
865
+ * If specified, the stream will terminate after this absolute offset (positive integer) is reached.
866
+ */
867
+ endInclusive?: number;
868
+ /**
869
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
870
+ * Requesting parties with template filters.
871
+ * Template filters must be empty for GetUpdateTrees requests.
872
+ * Optional for backwards compatibility, if defined update_format must be unset
873
+ */
874
+ filter?: components["schemas"]["TransactionFilter"];
875
+ /**
876
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
877
+ * If enabled, values served over the API will contain more information than strictly necessary to interpret the data.
878
+ * In particular, setting the verbose flag to true triggers the ledger to include labels, record and variant type ids
879
+ * for record fields.
880
+ * Optional for backwards compatibility, if defined update_format must be unset
881
+ */
882
+ verbose: boolean;
883
+ /**
884
+ * @description Must be unset for GetUpdateTrees request.
885
+ * Optional for backwards compatibility for GetUpdates request: defaults to an UpdateFormat where:
886
+ *
887
+ * - include_transactions.event_format.filters_by_party = the filter.filters_by_party on this request
888
+ * - include_transactions.event_format.filters_for_any_party = the filter.filters_for_any_party on this request
889
+ * - include_transactions.event_format.verbose = the same flag specified on this request
890
+ * - include_transactions.transaction_shape = TRANSACTION_SHAPE_ACS_DELTA
891
+ * - include_reassignments.filter = the same filter specified on this request
892
+ * - include_reassignments.verbose = the same flag specified on this request
893
+ * - include_topology_events.include_participant_authorization_events.parties = all the parties specified in filter
894
+ */
895
+ updateFormat?: components["schemas"]["UpdateFormat"];
896
+ };
897
+ /**
898
+ * UpdateFormat
899
+ * @description A format specifying what updates to include and how to render them.
900
+ */
901
+ UpdateFormat: {
902
+ /**
903
+ * @description Include Daml transactions in streams.
904
+ * Optional, if unset, no transactions are emitted in the stream.
905
+ */
906
+ includeTransactions?: components["schemas"]["TransactionFormat"];
907
+ /**
908
+ * @description Include (un)assignments in the stream.
909
+ * The events in the result take the shape TRANSACTION_SHAPE_ACS_DELTA.
910
+ * Optional, if unset, no (un)assignments are emitted in the stream.
911
+ */
912
+ includeReassignments?: components["schemas"]["EventFormat"];
913
+ /**
914
+ * @description Include topology events in streams.
915
+ * Optional, if unset no topology events are emitted in the stream.
916
+ */
917
+ includeTopologyEvents?: components["schemas"]["TopologyFormat"];
918
+ };
919
+ /**
920
+ * TransactionFormat
921
+ * @description A format that specifies what events to include in Daml transactions
922
+ * and what data to compute and include for them.
923
+ */
924
+ TransactionFormat: {
925
+ /** @description Required */
926
+ eventFormat?: components["schemas"]["EventFormat"];
927
+ /**
928
+ * @description What transaction shape to use for interpreting the filters of the event format.
929
+ * Required
930
+ * @enum {string}
931
+ */
932
+ transactionShape: "TRANSACTION_SHAPE_UNSPECIFIED" | "TRANSACTION_SHAPE_ACS_DELTA" | "TRANSACTION_SHAPE_LEDGER_EFFECTS";
933
+ };
934
+ /**
935
+ * TopologyFormat
936
+ * @description A format specifying which topology transactions to include and how to render them.
937
+ */
938
+ TopologyFormat: {
939
+ /**
940
+ * @description Include participant authorization topology events in streams.
941
+ * Optional, if unset no participant authorization topology events are emitted in the stream.
942
+ */
943
+ includeParticipantAuthorizationEvents?: components["schemas"]["ParticipantAuthorizationTopologyFormat"];
944
+ };
945
+ /**
946
+ * ParticipantAuthorizationTopologyFormat
947
+ * @description A format specifying which participant authorization topology transactions to include and how to render them.
948
+ */
949
+ ParticipantAuthorizationTopologyFormat: {
950
+ /**
951
+ * @description List of parties for which the topology transactions should be sent.
952
+ * Empty means: for all parties.
953
+ */
954
+ parties?: string[];
955
+ };
956
+ /** Either_JsCantonError_JsGetUpdatesResponse */
957
+ Either_JsCantonError_JsGetUpdatesResponse: components["schemas"]["JsCantonError"] | components["schemas"]["JsGetUpdatesResponse"];
958
+ /** JsGetUpdatesResponse */
959
+ JsGetUpdatesResponse: {
960
+ update: components["schemas"]["Update"];
961
+ };
962
+ /** Update */
963
+ Update: {
964
+ OffsetCheckpoint: components["schemas"]["OffsetCheckpoint2"];
965
+ } | {
966
+ Reassignment: components["schemas"]["Reassignment"];
967
+ } | {
968
+ TopologyTransaction: components["schemas"]["TopologyTransaction"];
969
+ } | {
970
+ Transaction: components["schemas"]["Transaction"];
971
+ };
972
+ /**
973
+ * OffsetCheckpoint
974
+ * @description OffsetCheckpoints may be used to:
975
+ *
976
+ * - detect time out of commands.
977
+ * - provide an offset which can be used to restart consumption.
978
+ */
979
+ OffsetCheckpoint2: {
980
+ value: components["schemas"]["OffsetCheckpoint1"];
981
+ };
982
+ /**
983
+ * Reassignment
984
+ * @description Complete view of an on-ledger reassignment.
985
+ */
986
+ Reassignment: {
987
+ value: components["schemas"]["JsReassignment"];
988
+ };
989
+ /**
990
+ * JsReassignment
991
+ * @description Complete view of an on-ledger reassignment.
992
+ */
993
+ JsReassignment: {
994
+ /**
995
+ * @description Assigned by the server. Useful for correlating logs.
996
+ * Must be a valid LedgerString (as described in ``value.proto``).
997
+ * Required
998
+ */
999
+ updateId: LedgerString;
1000
+ /**
1001
+ * @description The ID of the command which resulted in this reassignment. Missing for everyone except the submitting party on the submitting participant.
1002
+ * Must be a valid LedgerString (as described in ``value.proto``).
1003
+ * Optional
1004
+ */
1005
+ commandId: LedgerString;
1006
+ /**
1007
+ * @description The workflow ID used in reassignment command submission. Only set if the ``workflow_id`` for the command was set.
1008
+ * Must be a valid LedgerString (as described in ``value.proto``).
1009
+ * Optional
1010
+ */
1011
+ workflowId: LedgerString;
1012
+ /**
1013
+ * Format: int64
1014
+ * @description The participant's offset. The details of this field are described in ``community/ledger-api/README.md``.
1015
+ * Required, must be a valid absolute offset (positive integer).
1016
+ */
1017
+ offset: number;
1018
+ /** @description The collection of reassignment events. Required. */
1019
+ events?: components["schemas"]["JsReassignmentEvent"][];
1020
+ /**
1021
+ * @description Optional; ledger API trace context
1022
+ *
1023
+ * The trace context transported in this message corresponds to the trace context supplied
1024
+ * by the client application in a HTTP2 header of the original command submission.
1025
+ * We typically use a header to transfer this type of information. Here we use message
1026
+ * body, because it is used in gRPC streams which do not support per message headers.
1027
+ * This field will be populated with the trace context contained in the original submission.
1028
+ * If that was not provided, a unique ledger-api-server generated trace context will be used
1029
+ * instead.
1030
+ */
1031
+ traceContext?: components["schemas"]["TraceContext"];
1032
+ /**
1033
+ * @description The time at which the reassignment was recorded. The record time refers to the source/target
1034
+ * synchronizer for an unassign/assign event respectively.
1035
+ * Required
1036
+ */
1037
+ recordTime: string;
1038
+ /**
1039
+ * @description A valid synchronizer id.
1040
+ * Identifies the synchronizer that synchronized this Reassignment.
1041
+ * Required
1042
+ */
1043
+ synchronizerId: string;
1044
+ };
1045
+ /** JsReassignmentEvent */
1046
+ JsReassignmentEvent: {
1047
+ JsAssignmentEvent: components["schemas"]["JsAssignmentEvent"];
1048
+ } | {
1049
+ JsUnassignedEvent: components["schemas"]["JsUnassignedEvent"];
1050
+ };
1051
+ /** JsAssignmentEvent */
1052
+ JsAssignmentEvent: {
1053
+ source: string;
1054
+ target: string;
1055
+ reassignmentId: string;
1056
+ submitter: string;
1057
+ /** Format: int64 */
1058
+ reassignmentCounter: number;
1059
+ createdEvent: components["schemas"]["CreatedEvent"];
1060
+ };
1061
+ /**
1062
+ * JsUnassignedEvent
1063
+ * @description Records that a contract has been unassigned, and it becomes unusable on the source synchronizer
1064
+ */
1065
+ JsUnassignedEvent: {
1066
+ value: components["schemas"]["UnassignedEvent"];
1067
+ };
1068
+ /** TopologyTransaction */
1069
+ TopologyTransaction: {
1070
+ value: components["schemas"]["JsTopologyTransaction"];
1071
+ };
1072
+ /** JsTopologyTransaction */
1073
+ JsTopologyTransaction: {
1074
+ /**
1075
+ * @description Assigned by the server. Useful for correlating logs.
1076
+ * Must be a valid LedgerString (as described in ``value.proto``).
1077
+ * Required
1078
+ */
1079
+ updateId: LedgerString;
1080
+ /**
1081
+ * Format: int64
1082
+ * @description The absolute offset. The details of this field are described in ``community/ledger-api/README.md``.
1083
+ * Required, it is a valid absolute offset (positive integer).
1084
+ */
1085
+ offset: number;
1086
+ /**
1087
+ * @description A valid synchronizer id.
1088
+ * Identifies the synchronizer that synchronized the topology transaction.
1089
+ * Required
1090
+ */
1091
+ synchronizerId: string;
1092
+ /**
1093
+ * @description The time at which the changes in the topology transaction become effective. There is a small delay between a
1094
+ * topology transaction being sequenced and the changes it contains becoming effective. Topology transactions appear
1095
+ * in order relative to a synchronizer based on their effective time rather than their sequencing time.
1096
+ * Required
1097
+ */
1098
+ recordTime?: string;
1099
+ /**
1100
+ * @description A non-empty list of topology events.
1101
+ * Required
1102
+ */
1103
+ events?: components["schemas"]["TopologyEvent"][];
1104
+ /**
1105
+ * @description Optional; ledger API trace context
1106
+ *
1107
+ * The trace context transported in this message corresponds to the trace context supplied
1108
+ * by the client application in a HTTP2 header of the original command submission.
1109
+ * We typically use a header to transfer this type of information. Here we use message
1110
+ * body, because it is used in gRPC streams which do not support per message headers.
1111
+ * This field will be populated with the trace context contained in the original submission.
1112
+ * If that was not provided, a unique ledger-api-server generated trace context will be used
1113
+ * instead.
1114
+ */
1115
+ traceContext?: components["schemas"]["TraceContext"];
1116
+ };
1117
+ /** TopologyEvent */
1118
+ TopologyEvent: {
1119
+ event: components["schemas"]["TopologyEventEvent"];
1120
+ };
1121
+ /** TopologyEventEvent */
1122
+ TopologyEventEvent: {
1123
+ Empty: components["schemas"]["Empty3"];
1124
+ } | {
1125
+ ParticipantAuthorizationAdded: components["schemas"]["ParticipantAuthorizationAdded"];
1126
+ } | {
1127
+ ParticipantAuthorizationChanged: components["schemas"]["ParticipantAuthorizationChanged"];
1128
+ } | {
1129
+ ParticipantAuthorizationRevoked: components["schemas"]["ParticipantAuthorizationRevoked"];
1130
+ };
1131
+ /** Empty */
1132
+ Empty3: Record<string, never>;
1133
+ /** ParticipantAuthorizationAdded */
1134
+ ParticipantAuthorizationAdded: {
1135
+ value: components["schemas"]["ParticipantAuthorizationAdded1"];
1136
+ };
1137
+ /** ParticipantAuthorizationAdded */
1138
+ ParticipantAuthorizationAdded1: {
1139
+ /** @description Required */
1140
+ partyId: string;
1141
+ /** @description Required */
1142
+ participantId: string;
1143
+ /**
1144
+ * @description Required
1145
+ * @enum {string}
1146
+ */
1147
+ participantPermission: "PARTICIPANT_PERMISSION_UNSPECIFIED" | "PARTICIPANT_PERMISSION_SUBMISSION" | "PARTICIPANT_PERMISSION_CONFIRMATION" | "PARTICIPANT_PERMISSION_OBSERVATION";
1148
+ };
1149
+ /** ParticipantAuthorizationChanged */
1150
+ ParticipantAuthorizationChanged: {
1151
+ value: components["schemas"]["ParticipantAuthorizationChanged1"];
1152
+ };
1153
+ /** ParticipantAuthorizationChanged */
1154
+ ParticipantAuthorizationChanged1: {
1155
+ /** @description Required */
1156
+ partyId: string;
1157
+ /** @description Required */
1158
+ participantId: string;
1159
+ /**
1160
+ * @description Required
1161
+ * @enum {string}
1162
+ */
1163
+ participantPermission: "PARTICIPANT_PERMISSION_UNSPECIFIED" | "PARTICIPANT_PERMISSION_SUBMISSION" | "PARTICIPANT_PERMISSION_CONFIRMATION" | "PARTICIPANT_PERMISSION_OBSERVATION";
1164
+ };
1165
+ /** ParticipantAuthorizationRevoked */
1166
+ ParticipantAuthorizationRevoked: {
1167
+ value: components["schemas"]["ParticipantAuthorizationRevoked1"];
1168
+ };
1169
+ /** ParticipantAuthorizationRevoked */
1170
+ ParticipantAuthorizationRevoked1: {
1171
+ /** @description Required */
1172
+ partyId: string;
1173
+ /** @description Required */
1174
+ participantId: string;
1175
+ };
1176
+ /**
1177
+ * Transaction
1178
+ * @description Filtered view of an on-ledger transaction's create and archive events.
1179
+ */
1180
+ Transaction: {
1181
+ value: components["schemas"]["JsTransaction"];
1182
+ };
1183
+ /**
1184
+ * JsTransaction
1185
+ * @description Filtered view of an on-ledger transaction's create and archive events.
1186
+ */
1187
+ JsTransaction: {
1188
+ /**
1189
+ * @description Assigned by the server. Useful for correlating logs.
1190
+ * Must be a valid LedgerString (as described in ``value.proto``).
1191
+ * Required
1192
+ */
1193
+ updateId: LedgerString;
1194
+ /**
1195
+ * @description The ID of the command which resulted in this transaction. Missing for everyone except the submitting party.
1196
+ * Must be a valid LedgerString (as described in ``value.proto``).
1197
+ * Optional
1198
+ */
1199
+ commandId: LedgerString;
1200
+ /**
1201
+ * @description The workflow ID used in command submission.
1202
+ * Must be a valid LedgerString (as described in ``value.proto``).
1203
+ * Optional
1204
+ */
1205
+ workflowId: LedgerString;
1206
+ /**
1207
+ * @description Ledger effective time.
1208
+ * Required
1209
+ */
1210
+ effectiveAt: string;
1211
+ /**
1212
+ * @description The collection of events.
1213
+ * Contains:
1214
+ *
1215
+ * - ``CreatedEvent`` or ``ArchivedEvent`` in case of ACS_DELTA transaction shape
1216
+ * - ``CreatedEvent`` or ``ExercisedEvent`` in case of LEDGER_EFFECTS transaction shape
1217
+ *
1218
+ * Required
1219
+ */
1220
+ events?: components["schemas"]["Event"][];
1221
+ /**
1222
+ * Format: int64
1223
+ * @description The absolute offset. The details of this field are described in ``community/ledger-api/README.md``.
1224
+ * Required, it is a valid absolute offset (positive integer).
1225
+ */
1226
+ offset: number;
1227
+ /**
1228
+ * @description A valid synchronizer id.
1229
+ * Identifies the synchronizer that synchronized the transaction.
1230
+ * Required
1231
+ */
1232
+ synchronizerId: string;
1233
+ /**
1234
+ * @description Optional; ledger API trace context
1235
+ *
1236
+ * The trace context transported in this message corresponds to the trace context supplied
1237
+ * by the client application in a HTTP2 header of the original command submission.
1238
+ * We typically use a header to transfer this type of information. Here we use message
1239
+ * body, because it is used in gRPC streams which do not support per message headers.
1240
+ * This field will be populated with the trace context contained in the original submission.
1241
+ * If that was not provided, a unique ledger-api-server generated trace context will be used
1242
+ * instead.
1243
+ */
1244
+ traceContext?: components["schemas"]["TraceContext"];
1245
+ /**
1246
+ * @description The time at which the transaction was recorded. The record time refers to the synchronizer
1247
+ * which synchronized the transaction.
1248
+ * Required
1249
+ */
1250
+ recordTime: string;
1251
+ /**
1252
+ * @description For transaction externally signed, contains the external transaction hash
1253
+ * signed by the external party. Can be used to correlate an external submission with a committed transaction.
1254
+ * Optional
1255
+ */
1256
+ externalTransactionHash?: string;
1257
+ };
1258
+ /**
1259
+ * Event
1260
+ * @description Events in transactions can have two primary shapes:
1261
+ *
1262
+ * - ACS delta: events can be CreatedEvent or ArchivedEvent
1263
+ * - ledger effects: events can be CreatedEvent or ExercisedEvent
1264
+ *
1265
+ * In the update service the events are restricted to the events
1266
+ * visible for the parties specified in the transaction filter. Each
1267
+ * event message type below contains a ``witness_parties`` field which
1268
+ * indicates the subset of the requested parties that can see the event
1269
+ * in question.
1270
+ */
1271
+ Event: {
1272
+ ArchivedEvent: components["schemas"]["ArchivedEvent"];
1273
+ } | {
1274
+ CreatedEvent: components["schemas"]["CreatedEvent"];
1275
+ } | {
1276
+ ExercisedEvent: components["schemas"]["ExercisedEvent"];
1277
+ };
1278
+ /**
1279
+ * ArchivedEvent
1280
+ * @description Records that a contract has been archived, and choices may no longer be exercised on it.
1281
+ */
1282
+ ArchivedEvent: {
1283
+ /**
1284
+ * Format: int64
1285
+ * @description The offset of origin.
1286
+ * Offsets are managed by the participant nodes.
1287
+ * Transactions can thus NOT be assumed to have the same offsets on different participant nodes.
1288
+ * Required, it is a valid absolute offset (positive integer)
1289
+ */
1290
+ offset: number;
1291
+ /**
1292
+ * Format: int32
1293
+ * @description The position of this event in the originating transaction or reassignment.
1294
+ * Node IDs are not necessarily equal across participants,
1295
+ * as these may see different projections/parts of transactions.
1296
+ * Required, must be valid node ID (non-negative integer)
1297
+ */
1298
+ nodeId: number;
1299
+ /**
1300
+ * @description The ID of the archived contract.
1301
+ * Must be a valid LedgerString (as described in ``value.proto``).
1302
+ * Required
1303
+ */
1304
+ contractId: LedgerString;
1305
+ /**
1306
+ * @description Identifies the template that defines the choice that archived the contract.
1307
+ * This template's package-id may differ from the target contract's package-id
1308
+ * if the target contract has been upgraded or downgraded.
1309
+ *
1310
+ * The identifier uses the package-id reference format.
1311
+ *
1312
+ * Required
1313
+ */
1314
+ templateId: PackageIdString;
1315
+ /**
1316
+ * @description The parties that are notified of this event. For an ``ArchivedEvent``,
1317
+ * these are the intersection of the stakeholders of the contract in
1318
+ * question and the parties specified in the ``TransactionFilter``. The
1319
+ * stakeholders are the union of the signatories and the observers of
1320
+ * the contract.
1321
+ * Each one of its elements must be a valid PartyIdString (as described
1322
+ * in ``value.proto``).
1323
+ * Required
1324
+ */
1325
+ witnessParties?: string[];
1326
+ /**
1327
+ * @description The package name of the contract.
1328
+ * Required
1329
+ */
1330
+ packageName: string;
1331
+ /**
1332
+ * @description The interfaces implemented by the target template that have been
1333
+ * matched from the interface filter query.
1334
+ * Populated only in case interface filters with include_interface_view set.
1335
+ *
1336
+ * If defined, the identifier uses the package-id reference format.
1337
+ *
1338
+ * Optional
1339
+ */
1340
+ implementedInterfaces?: string[];
1341
+ };
1342
+ /**
1343
+ * ExercisedEvent
1344
+ * @description Records that a choice has been exercised on a target contract.
1345
+ */
1346
+ ExercisedEvent: {
1347
+ /**
1348
+ * Format: int64
1349
+ * @description The offset of origin.
1350
+ * Offsets are managed by the participant nodes.
1351
+ * Transactions can thus NOT be assumed to have the same offsets on different participant nodes.
1352
+ * Required, it is a valid absolute offset (positive integer)
1353
+ */
1354
+ offset: number;
1355
+ /**
1356
+ * Format: int32
1357
+ * @description The position of this event in the originating transaction or reassignment.
1358
+ * Node IDs are not necessarily equal across participants,
1359
+ * as these may see different projections/parts of transactions.
1360
+ * Required, must be valid node ID (non-negative integer)
1361
+ */
1362
+ nodeId: number;
1363
+ /**
1364
+ * @description The ID of the target contract.
1365
+ * Must be a valid LedgerString (as described in ``value.proto``).
1366
+ * Required
1367
+ */
1368
+ contractId: LedgerString;
1369
+ /**
1370
+ * @description Identifies the template that defines the executed choice.
1371
+ * This template's package-id may differ from the target contract's package-id
1372
+ * if the target contract has been upgraded or downgraded.
1373
+ *
1374
+ * The identifier uses the package-id reference format.
1375
+ *
1376
+ * Required
1377
+ */
1378
+ templateId: PackageIdString;
1379
+ /**
1380
+ * @description The interface where the choice is defined, if inherited.
1381
+ * If defined, the identifier uses the package-id reference format.
1382
+ *
1383
+ * Optional
1384
+ */
1385
+ interfaceId?: string;
1386
+ /**
1387
+ * @description The choice that was exercised on the target contract.
1388
+ * Must be a valid NameString (as described in ``value.proto``).
1389
+ * Required
1390
+ */
1391
+ choice: NameString;
1392
+ /**
1393
+ * @description The argument of the exercised choice.
1394
+ * Required
1395
+ */
1396
+ choiceArgument: unknown;
1397
+ /**
1398
+ * @description The parties that exercised the choice.
1399
+ * Each element must be a valid PartyIdString (as described in ``value.proto``).
1400
+ * Required
1401
+ */
1402
+ actingParties?: string[];
1403
+ /**
1404
+ * @description If true, the target contract may no longer be exercised.
1405
+ * Required
1406
+ */
1407
+ consuming: boolean;
1408
+ /**
1409
+ * @description The parties that are notified of this event. The witnesses of an exercise
1410
+ * node will depend on whether the exercise was consuming or not.
1411
+ * If consuming, the witnesses are the union of the stakeholders,
1412
+ * the actors and all informees of all the ancestors of this event this
1413
+ * participant knows about.
1414
+ * If not consuming, the witnesses are the union of the signatories,
1415
+ * the actors and all informees of all the ancestors of this event this
1416
+ * participant knows about.
1417
+ * In both cases the witnesses are limited to the querying parties, or not
1418
+ * limited in case anyParty filters are used.
1419
+ * Note that the actors might not necessarily be observers
1420
+ * and thus stakeholders. This is the case when the controllers of a
1421
+ * choice are specified using "flexible controllers", using the
1422
+ * ``choice ... controller`` syntax, and said controllers are not
1423
+ * explicitly marked as observers.
1424
+ * Each element must be a valid PartyIdString (as described in ``value.proto``).
1425
+ * Required
1426
+ */
1427
+ witnessParties?: string[];
1428
+ /**
1429
+ * Format: int32
1430
+ * @description Specifies the upper boundary of the node ids of the events in the same transaction that appeared as a result of
1431
+ * this ``ExercisedEvent``. This allows unambiguous identification of all the members of the subtree rooted at this
1432
+ * node. A full subtree can be constructed when all descendant nodes are present in the stream. If nodes are heavily
1433
+ * filtered, it is only possible to determine if a node is in a consequent subtree or not.
1434
+ * Required
1435
+ */
1436
+ lastDescendantNodeId: number;
1437
+ /**
1438
+ * @description The result of exercising the choice.
1439
+ * Required
1440
+ */
1441
+ exerciseResult: unknown;
1442
+ /**
1443
+ * @description The package name of the contract.
1444
+ * Required
1445
+ */
1446
+ packageName: string;
1447
+ /**
1448
+ * @description If the event is consuming, the interfaces implemented by the target template that have been
1449
+ * matched from the interface filter query.
1450
+ * Populated only in case interface filters with include_interface_view set.
1451
+ *
1452
+ * The identifier uses the package-id reference format.
1453
+ *
1454
+ * Optional
1455
+ */
1456
+ implementedInterfaces?: PackageIdString[];
1457
+ /**
1458
+ * @description Whether this event would be part of respective ACS_DELTA shaped stream,
1459
+ * and should therefore considered when tracking contract activeness on the client-side.
1460
+ * Required
1461
+ */
1462
+ acsDelta: boolean;
1463
+ };
1464
+ /** Either_JsCantonError_JsGetUpdateTreesResponse */
1465
+ Either_JsCantonError_JsGetUpdateTreesResponse: components["schemas"]["JsCantonError"] | components["schemas"]["JsGetUpdateTreesResponse"];
1466
+ /**
1467
+ * JsGetUpdateTreesResponse
1468
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
1469
+ */
1470
+ JsGetUpdateTreesResponse: {
1471
+ update: components["schemas"]["Update1"];
1472
+ };
1473
+ /** Update */
1474
+ Update1: {
1475
+ OffsetCheckpoint: components["schemas"]["OffsetCheckpoint3"];
1476
+ } | {
1477
+ Reassignment: components["schemas"]["Reassignment1"];
1478
+ } | {
1479
+ TransactionTree: components["schemas"]["TransactionTree"];
1480
+ };
1481
+ /**
1482
+ * OffsetCheckpoint
1483
+ * @description OffsetCheckpoints may be used to:
1484
+ *
1485
+ * - detect time out of commands.
1486
+ * - provide an offset which can be used to restart consumption.
1487
+ */
1488
+ OffsetCheckpoint3: {
1489
+ value: components["schemas"]["OffsetCheckpoint1"];
1490
+ };
1491
+ /**
1492
+ * Reassignment
1493
+ * @description Complete view of an on-ledger reassignment.
1494
+ */
1495
+ Reassignment1: {
1496
+ value: components["schemas"]["JsReassignment"];
1497
+ };
1498
+ /**
1499
+ * TransactionTree
1500
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
1501
+ * Complete view of an on-ledger transaction.
1502
+ */
1503
+ TransactionTree: {
1504
+ value: components["schemas"]["JsTransactionTree"];
1505
+ };
1506
+ /**
1507
+ * JsTransactionTree
1508
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
1509
+ * Complete view of an on-ledger transaction.
1510
+ */
1511
+ JsTransactionTree: {
1512
+ /**
1513
+ * @description Assigned by the server. Useful for correlating logs.
1514
+ * Must be a valid LedgerString (as described in ``value.proto``).
1515
+ * Required
1516
+ */
1517
+ updateId: LedgerString;
1518
+ /**
1519
+ * @description The ID of the command which resulted in this transaction. Missing for everyone except the submitting party.
1520
+ * Must be a valid LedgerString (as described in ``value.proto``).
1521
+ * Optional
1522
+ */
1523
+ commandId: LedgerString;
1524
+ /**
1525
+ * @description The workflow ID used in command submission. Only set if the ``workflow_id`` for the command was set.
1526
+ * Must be a valid LedgerString (as described in ``value.proto``).
1527
+ * Optional
1528
+ */
1529
+ workflowId: LedgerString;
1530
+ /**
1531
+ * @description Ledger effective time.
1532
+ * Required
1533
+ */
1534
+ effectiveAt?: string;
1535
+ /**
1536
+ * Format: int64
1537
+ * @description The absolute offset. The details of this field are described in ``community/ledger-api/README.md``.
1538
+ * Required, it is a valid absolute offset (positive integer).
1539
+ */
1540
+ offset: number;
1541
+ /**
1542
+ * @description Changes to the ledger that were caused by this transaction. Nodes of the transaction tree.
1543
+ * Each key must be a valid node ID (non-negative integer).
1544
+ * Required
1545
+ */
1546
+ eventsById: components["schemas"]["Map_Int_TreeEvent"];
1547
+ /**
1548
+ * @description A valid synchronizer id.
1549
+ * Identifies the synchronizer that synchronized the transaction.
1550
+ * Required
1551
+ */
1552
+ synchronizerId: string;
1553
+ /**
1554
+ * @description Optional; ledger API trace context
1555
+ *
1556
+ * The trace context transported in this message corresponds to the trace context supplied
1557
+ * by the client application in a HTTP2 header of the original command submission.
1558
+ * We typically use a header to transfer this type of information. Here we use message
1559
+ * body, because it is used in gRPC streams which do not support per message headers.
1560
+ * This field will be populated with the trace context contained in the original submission.
1561
+ * If that was not provided, a unique ledger-api-server generated trace context will be used
1562
+ * instead.
1563
+ */
1564
+ traceContext?: components["schemas"]["TraceContext"];
1565
+ /**
1566
+ * @description The time at which the transaction was recorded. The record time refers to the synchronizer
1567
+ * which synchronized the transaction.
1568
+ * Required
1569
+ */
1570
+ recordTime: string;
1571
+ };
1572
+ /** Map_Int_TreeEvent */
1573
+ Map_Int_TreeEvent: {
1574
+ [key: string]: components["schemas"]["TreeEvent"];
1575
+ };
1576
+ /**
1577
+ * TreeEvent
1578
+ * @description Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
1579
+ * Each tree event message type below contains a ``witness_parties`` field which
1580
+ * indicates the subset of the requested parties that can see the event
1581
+ * in question.
1582
+ *
1583
+ * Note that transaction trees might contain events with
1584
+ * _no_ witness parties, which were included simply because they were
1585
+ * children of events which have witnesses.
1586
+ */
1587
+ TreeEvent: {
1588
+ CreatedTreeEvent: components["schemas"]["CreatedTreeEvent"];
1589
+ } | {
1590
+ ExercisedTreeEvent: components["schemas"]["ExercisedTreeEvent"];
1591
+ };
1592
+ /** CreatedTreeEvent */
1593
+ CreatedTreeEvent: {
1594
+ value: components["schemas"]["CreatedEvent"];
1595
+ };
1596
+ /** ExercisedTreeEvent */
1597
+ ExercisedTreeEvent: {
1598
+ value: components["schemas"]["ExercisedEvent"];
1599
+ };
1600
+ };
1601
+ responses: never;
1602
+ parameters: never;
1603
+ requestBodies: never;
1604
+ headers: never;
1605
+ pathItems: never;
1606
+ }
1607
+ export type $defs = Record<string, never>;
1608
+ export type operations = Record<string, never>;
1609
+ export interface channels {
1610
+ "/v2/commands/completions": {
1611
+ /** @description Get completions stream */
1612
+ publish: {
1613
+ /** @description Get completions stream */
1614
+ message: components["schemas"]["CompletionStreamRequest"];
1615
+ };
1616
+ subscribe: {
1617
+ /** @description Get completions stream */
1618
+ message: components["schemas"]["Either_JsCantonError_CompletionStreamResponse"];
1619
+ };
1620
+ };
1621
+ "/v2/state/active-contracts": {
1622
+ /** @description Get active contracts stream */
1623
+ publish: {
1624
+ /** @description Get active contracts stream */
1625
+ message: components["schemas"]["GetActiveContractsRequest"];
1626
+ };
1627
+ subscribe: {
1628
+ /** @description Get active contracts stream */
1629
+ message: components["schemas"]["Either_JsCantonError_JsGetActiveContractsResponse"];
1630
+ };
1631
+ };
1632
+ "/v2/updates": {
1633
+ /** @description Get updates stream */
1634
+ publish: {
1635
+ /** @description Get updates stream */
1636
+ message: components["schemas"]["GetUpdatesRequest"];
1637
+ };
1638
+ subscribe: {
1639
+ /** @description Get updates stream */
1640
+ message: components["schemas"]["Either_JsCantonError_JsGetUpdatesResponse"];
1641
+ };
1642
+ };
1643
+ "/v2/updates/flats": {
1644
+ /** @description Get flat transactions update stream. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates instead. */
1645
+ publish: {
1646
+ /** @description Get flat transactions update stream. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates instead. */
1647
+ message: components["schemas"]["GetUpdatesRequest"];
1648
+ };
1649
+ subscribe: {
1650
+ /** @description Get flat transactions update stream. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates instead. */
1651
+ message: components["schemas"]["Either_JsCantonError_JsGetUpdatesResponse"];
1652
+ };
1653
+ };
1654
+ "/v2/updates/trees": {
1655
+ /** @description Get update transactions tree stream. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates instead. */
1656
+ publish: {
1657
+ /** @description Get update transactions tree stream. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates instead. */
1658
+ message: components["schemas"]["GetUpdatesRequest"];
1659
+ };
1660
+ subscribe: {
1661
+ /** @description Get update transactions tree stream. Provided for backwards compatibility, it will be removed in the Canton version 3.5.0, use v2/updates instead. */
1662
+ message: components["schemas"]["Either_JsCantonError_JsGetUpdateTreesResponse"];
1663
+ };
1664
+ };
1665
+ }