@dfns/sdk 0.7.12-rc.1 → 0.7.13-rc.0

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.
@@ -1,27 +1,45 @@
1
1
  export type CreateCantonValidatorBody = {
2
+ /** Nickname for this validator. */
2
3
  name?: string | undefined;
3
4
  kind: "Shared";
4
5
  } | {
6
+ /** Nickname for this validator. */
5
7
  name?: string | undefined;
6
8
  kind: "Custom";
9
+ /** Configuration to reach your validator Signing API. We will call the validator External Signing API at the url (and using the credentials) defined below ; for instance `$URL/api/validator/v0/admin/external-party/topology/generate`. See the underlying calls details [here](https://docs.dev.sync.global/app_dev/validator_api/index.html#validator-api-external-signing). */
7
10
  validator: {
11
+ /** URL to reach the API at this address. The calls will be originating from our IP addresses (see [Dfns Environments](https://docs.dfns.co/api-reference/environments)) */
8
12
  url: string;
13
+ /** How Dfns will authenticate into your validator/ledger. You should have setup authentication already (see details [here](https://docs.dev.sync.global/validator_operator/validator_helm.html#helm-validator-auth)), you can reuse the same Application details. See examples in this endpoint payload examples above. */
9
14
  oauth2: {
15
+ /** your OAuth2 tenant domain. Provided by your auth provider. */
10
16
  domain: string;
17
+ /** token endpoint from your authorization provider. We will call this endpoint on your tenant domain (i.e.: `<domain>/<token path>`) */
18
+ tokenPath?: string | undefined;
19
+ /** the audience your configured on your auth provider. It is suggested to start with `https://canton.network.global`. */
20
+ audience: string;
21
+ /** The client id from your auth provider for this application. */
11
22
  clientId: string;
23
+ /** The client secret from your auth provider for this application. */
12
24
  clientSecret: string;
13
- audience: string;
14
- tokenPath?: string | undefined;
15
25
  };
16
26
  };
27
+ /** Configuration to reach your validator Ledger JSON API. We will call endpoints such as `/v2/state/ledger-end`, `/v2/state/active-contracts`, `/v2/parties/participant-id`, `/v2/interactive-submission/prepare`, `/v2/interactive-submission/execute`, `/v2/commands/completions`. See the underlying details [here](https://docs.dev.sync.global/app_dev/ledger_api/index.html). */
17
28
  ledger: {
29
+ /** URL to reach the API at this address. The calls will be originating from our IP addresses (see [Dfns Environments](https://docs.dfns.co/api-reference/environments)) */
18
30
  url: string;
31
+ /** How Dfns will authenticate into your validator/ledger. You should have setup authentication already (see details [here](https://docs.dev.sync.global/validator_operator/validator_helm.html#helm-validator-auth)), you can reuse the same Application details. See examples in this endpoint payload examples above. */
19
32
  oauth2: {
33
+ /** your OAuth2 tenant domain. Provided by your auth provider. */
20
34
  domain: string;
35
+ /** token endpoint from your authorization provider. We will call this endpoint on your tenant domain (i.e.: `<domain>/<token path>`) */
36
+ tokenPath?: string | undefined;
37
+ /** the audience your configured on your auth provider. It is suggested to start with `https://canton.network.global`. */
38
+ audience: string;
39
+ /** The client id from your auth provider for this application. */
21
40
  clientId: string;
41
+ /** The client secret from your auth provider for this application. */
22
42
  clientSecret: string;
23
- audience: string;
24
- tokenPath?: string | undefined;
25
43
  };
26
44
  };
27
45
  };
@@ -29,9 +47,7 @@ export type CreateCantonValidatorParams = {
29
47
  network: "canton" | "canton-devnet" | "canton-testnet";
30
48
  };
31
49
  export type CreateCantonValidatorResponse = {
32
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
33
50
  id: string;
34
- /** e.g. 'or-30tnh-itmjs-s235s5ontr3r23h2' */
35
51
  orgId: string;
36
52
  network: "Canton" | "CantonDevnet" | "CantonTestnet";
37
53
  name?: string | undefined;
@@ -44,13 +60,10 @@ export type CreateCantonValidatorRequest = CreateCantonValidatorParams & {
44
60
  };
45
61
  export type DeleteCantonValidatorParams = {
46
62
  network: "canton" | "canton-devnet" | "canton-testnet";
47
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
48
63
  validatorId: string;
49
64
  };
50
65
  export type DeleteCantonValidatorResponse = {
51
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
52
66
  id: string;
53
- /** e.g. 'or-30tnh-itmjs-s235s5ontr3r23h2' */
54
67
  orgId: string;
55
68
  network: "Canton" | "CantonDevnet" | "CantonTestnet";
56
69
  name?: string | undefined;
@@ -61,13 +74,10 @@ export type DeleteCantonValidatorResponse = {
61
74
  export type DeleteCantonValidatorRequest = DeleteCantonValidatorParams;
62
75
  export type GetCantonValidatorParams = {
63
76
  network: "canton" | "canton-devnet" | "canton-testnet";
64
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
65
77
  validatorId: string;
66
78
  };
67
79
  export type GetCantonValidatorResponse = {
68
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
69
80
  id: string;
70
- /** e.g. 'or-30tnh-itmjs-s235s5ontr3r23h2' */
71
81
  orgId: string;
72
82
  network: "Canton" | "CantonDevnet" | "CantonTestnet";
73
83
  name?: string | undefined;
@@ -125,9 +135,7 @@ export type ListCantonValidatorsQuery = {
125
135
  };
126
136
  export type ListCantonValidatorsResponse = {
127
137
  items: {
128
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
129
138
  id: string;
130
- /** e.g. 'or-30tnh-itmjs-s235s5ontr3r23h2' */
131
139
  orgId: string;
132
140
  network: "Canton" | "CantonDevnet" | "CantonTestnet";
133
141
  name?: string | undefined;
@@ -142,8 +150,11 @@ export type ListCantonValidatorsRequest = ListCantonValidatorsParams & {
142
150
  };
143
151
  export type ReadContractBody = {
144
152
  kind: "Evm";
153
+ /** Network used for the wallet. */
145
154
  network: "Adi" | "AdiTestnet" | "ArbitrumOne" | "ArbitrumGoerli" | "ArbitrumSepolia" | "AvalancheC" | "AvalancheCFuji" | "Base" | "BaseGoerli" | "BaseSepolia" | "Bob" | "BobSepolia" | "Bsc" | "BscTestnet" | "Berachain" | "BerachainBArtio" | "BerachainBepolia" | "Celo" | "CeloAlfajores" | "Codex" | "CodexSepolia" | "Ethereum" | "EthereumGoerli" | "EthereumSepolia" | "EthereumHolesky" | "EthereumHoodi" | "FantomOpera" | "FantomTestnet" | "FlareC" | "FlareCCoston2" | "Ink" | "InkSepolia" | "Optimism" | "OptimismGoerli" | "OptimismSepolia" | "Plume" | "PlumeSepolia" | "Polygon" | "PolygonAmoy" | "PolygonMumbai" | "Race" | "RaceSepolia" | "Sonic" | "SonicTestnet" | "Tsc" | "TscTestnet1";
155
+ /** Address of the contract to call */
146
156
  contract: string;
157
+ /** Encoded hex string indicating which function in the smart contract to call with which parameters. For more information, see the [encodeFunctionData ethersJS documentation](https://docs.ethers.org/v6/api/abi/#Interface-encodeFunctionData) */
147
158
  data: string;
148
159
  };
149
160
  export type ReadContractResponse = {
@@ -154,37 +165,49 @@ export type ReadContractRequest = {
154
165
  body: ReadContractBody;
155
166
  };
156
167
  export type UpdateCantonValidatorBody = {
168
+ /** Nickname for this validator. */
157
169
  name?: string | undefined;
158
170
  validator?: {
171
+ /** URL to reach the API at this address. The calls will be originating from our IP addresses (see [Dfns Environments](https://docs.dfns.co/api-reference/environments)) */
159
172
  url: string;
173
+ /** How Dfns will authenticate into your validator/ledger. You should have setup authentication already (see details [here](https://docs.dev.sync.global/validator_operator/validator_helm.html#helm-validator-auth)), you can reuse the same Application details. See examples in this endpoint payload examples above. */
160
174
  oauth2: {
175
+ /** your OAuth2 tenant domain. Provided by your auth provider. */
161
176
  domain: string;
177
+ /** token endpoint from your authorization provider. We will call this endpoint on your tenant domain (i.e.: `<domain>/<token path>`) */
178
+ tokenPath?: string | undefined;
179
+ /** the audience your configured on your auth provider. It is suggested to start with `https://canton.network.global`. */
180
+ audience: string;
181
+ /** The client id from your auth provider for this application. */
162
182
  clientId: string;
183
+ /** The client secret from your auth provider for this application. */
163
184
  clientSecret: string;
164
- audience: string;
165
- tokenPath?: string | undefined;
166
185
  };
167
186
  } | undefined;
168
187
  ledger?: {
188
+ /** URL to reach the API at this address. The calls will be originating from our IP addresses (see [Dfns Environments](https://docs.dfns.co/api-reference/environments)) */
169
189
  url: string;
190
+ /** How Dfns will authenticate into your validator/ledger. You should have setup authentication already (see details [here](https://docs.dev.sync.global/validator_operator/validator_helm.html#helm-validator-auth)), you can reuse the same Application details. See examples in this endpoint payload examples above. */
170
191
  oauth2: {
192
+ /** your OAuth2 tenant domain. Provided by your auth provider. */
171
193
  domain: string;
194
+ /** token endpoint from your authorization provider. We will call this endpoint on your tenant domain (i.e.: `<domain>/<token path>`) */
195
+ tokenPath?: string | undefined;
196
+ /** the audience your configured on your auth provider. It is suggested to start with `https://canton.network.global`. */
197
+ audience: string;
198
+ /** The client id from your auth provider for this application. */
172
199
  clientId: string;
200
+ /** The client secret from your auth provider for this application. */
173
201
  clientSecret: string;
174
- audience: string;
175
- tokenPath?: string | undefined;
176
202
  };
177
203
  } | undefined;
178
204
  };
179
205
  export type UpdateCantonValidatorParams = {
180
206
  network: "canton" | "canton-devnet" | "canton-testnet";
181
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
182
207
  validatorId: string;
183
208
  };
184
209
  export type UpdateCantonValidatorResponse = {
185
- /** e.g. 'cv-7jeof-m584r-p35ucm37ko3cqgts' */
186
210
  id: string;
187
- /** e.g. 'or-30tnh-itmjs-s235s5ontr3r23h2' */
188
211
  orgId: string;
189
212
  network: "Canton" | "CantonDevnet" | "CantonTestnet";
190
213
  name?: string | undefined;