@settlemint/dalp-cli 3.1.32-main.42224863695 → 3.1.32-main.42233333234

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.
@@ -7130,7 +7130,7 @@
7130
7130
  {
7131
7131
  "name": "instrumentAdmin",
7132
7132
  "in": "query",
7133
- "required": true,
7133
+ "required": false,
7134
7134
  "description": "Canton party identifier, as the party registry or a platform read spells it.",
7135
7135
  "type": "string",
7136
7136
  "enum": null,
@@ -7266,7 +7266,7 @@
7266
7266
  {
7267
7267
  "name": "instrumentAdmin",
7268
7268
  "in": "query",
7269
- "required": true,
7269
+ "required": false,
7270
7270
  "description": "Canton party identifier, as the party registry or a platform read spells it.",
7271
7271
  "type": "string",
7272
7272
  "enum": null,
@@ -7626,7 +7626,7 @@
7626
7626
  {
7627
7627
  "name": "instrumentAdmin",
7628
7628
  "in": "query",
7629
- "required": true,
7629
+ "required": false,
7630
7630
  "description": "Canton party identifier, as the party registry or a platform read spells it.",
7631
7631
  "type": "string",
7632
7632
  "enum": null,
@@ -48269,8 +48269,8 @@
48269
48269
  "method": "POST",
48270
48270
  "url": "/api/v2/system/role-sets",
48271
48271
  "summary": "Set system roles",
48272
- "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48273
- "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48272
+ "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48273
+ "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48274
48274
  "tags": [
48275
48275
  "Roles and permissions"
48276
48276
  ],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@settlemint/dalp-cli",
3
- "version": "3.1.32-main.42224863695",
3
+ "version": "3.1.32-main.42233333234",
4
4
  "private": false,
5
5
  "description": "CLI for the Digital Asset Lifecycle Platform — manage tokens, identities, compliance, and more from the command line.",
6
6
  "homepage": "https://settlemint.com",
@@ -49,14 +49,14 @@
49
49
  },
50
50
  "dependencies": {
51
51
  "@modelcontextprotocol/server": "2.0.0-alpha.4",
52
- "@settlemint/dalp-sdk": "3.1.32-main.42224863695",
52
+ "@settlemint/dalp-sdk": "3.1.32-main.42233333234",
53
53
  "incur": "0.7.1",
54
54
  "zod": "4.6.7"
55
55
  },
56
56
  "devDependencies": {
57
57
  "@arethetypeswrong/cli": "0.18.5",
58
- "@testkit/effect-bun-test": "3.1.32-main.42224863695",
59
- "@tools/typescript-config": "3.1.32-main.42224863695",
58
+ "@testkit/effect-bun-test": "3.1.32-main.42233333234",
59
+ "@tools/typescript-config": "3.1.32-main.42233333234",
60
60
  "@types/bun": "1.4.4",
61
61
  "publint": "0.3.25"
62
62
  },
@@ -7130,7 +7130,7 @@
7130
7130
  {
7131
7131
  "name": "instrumentAdmin",
7132
7132
  "in": "query",
7133
- "required": true,
7133
+ "required": false,
7134
7134
  "description": "Canton party identifier, as the party registry or a platform read spells it.",
7135
7135
  "type": "string",
7136
7136
  "enum": null,
@@ -7266,7 +7266,7 @@
7266
7266
  {
7267
7267
  "name": "instrumentAdmin",
7268
7268
  "in": "query",
7269
- "required": true,
7269
+ "required": false,
7270
7270
  "description": "Canton party identifier, as the party registry or a platform read spells it.",
7271
7271
  "type": "string",
7272
7272
  "enum": null,
@@ -7626,7 +7626,7 @@
7626
7626
  {
7627
7627
  "name": "instrumentAdmin",
7628
7628
  "in": "query",
7629
- "required": true,
7629
+ "required": false,
7630
7630
  "description": "Canton party identifier, as the party registry or a platform read spells it.",
7631
7631
  "type": "string",
7632
7632
  "enum": null,
@@ -48269,8 +48269,8 @@
48269
48269
  "method": "POST",
48270
48270
  "url": "/api/v2/system/role-sets",
48271
48271
  "summary": "Set system roles",
48272
- "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48273
- "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. When a later write fails after an earlier one was submitted, the earlier ones are not undone: a later write refused on chain answers 422 with its own transaction request, and any other later failure answers 503 PlatformWriteOutcomeUnknown, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48272
+ "description": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48273
+ "help": "Grants and revokes system roles for one participant or one wallet as one change. Name the target with exactly one of participantId, address or participantWallet. An address covers that one wallet. A participantId covers the signing address of each custody account that the participant holds in the active organization on the selected chain. When account abstraction is enabled, it also covers the smart wallet of each of those accounts. The platform answers 403 when a participantId covers no address. A participantWallet covers the sent wallet plus the wallets that a participantId for its holder would cover. When no participant holds the sent wallet in the active organization on the selected chain, a participantWallet covers that wallet alone. The platform answers 403 when more than one participant holds the sent wallet in the active organization on the selected chain. The caller needs the admin role for every role in the request; a refused role answers 403 before any transaction. The platform sends one queued write per changed wallet and direction on any executor, every grant before any revoke. The writes share one database transaction and start only after it commits, so when any write fails before the platform answers, the writes queued before it roll back and the answer is the one a failure of the first write gets. Once the platform has answered, each write settles on its own: a write that fails on chain does not undo the others, so read the held roles before another write. Resending the same change plans only what is still missing. Repeating a change that is already true queues no transaction.",
48274
48274
  "tags": [
48275
48275
  "Roles and permissions"
48276
48276
  ],