Cheqd Studio Update DID
isDIDArray: (value: Validatable) => { const res = new DIDArrayValidator().validate((value as string[]).map((v) => (v.includes('#') ? v.split('#')[0] : v))); if (!res.valid) { throw new Error(res.error); } return true; }, Am I write to consider this a fix for checking the authentication property for the update did api endpoint validator in Cheqd Studio? https://github.com/cheqd/studio/blob/140dcea007da52f0fc4aea1eb6f2ca65aef0327c/src/controllers/api/did.ts#L131 I am attempting to update the authentication but its failing during validation unless I make the above change.
Luke Nispel 16 days ago
Low Priority
Bug Report
Cheqd Studio Update DID
isDIDArray: (value: Validatable) => { const res = new DIDArrayValidator().validate((value as string[]).map((v) => (v.includes('#') ? v.split('#')[0] : v))); if (!res.valid) { throw new Error(res.error); } return true; }, Am I write to consider this a fix for checking the authentication property for the update did api endpoint validator in Cheqd Studio? https://github.com/cheqd/studio/blob/140dcea007da52f0fc4aea1eb6f2ca65aef0327c/src/controllers/api/did.ts#L131 I am attempting to update the authentication but its failing during validation unless I make the above change.
Luke Nispel 16 days ago
Low Priority
Bug Report
Missing validator Dep
I raised an issue here that may be related to my problem but mainly is just a noted missing dep in the @cheqd/studio code https://github.com/cheqd/studio/issues/694
An Anonymous User 16 days ago
Low Priority
Bug Report
Missing validator Dep
I raised an issue here that may be related to my problem but mainly is just a noted missing dep in the @cheqd/studio code https://github.com/cheqd/studio/issues/694
An Anonymous User 16 days ago
Low Priority
Bug Report
Completed
Node validator problem
Output of our systemctl status cheqd-cosmovisor.service: May 14 12:00:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:00:51Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > May 14 12:01:49 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:01:49Z","message":"SendOsmosisQueryR> May 14 12:01:49 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:01:49Z","message":"handleOsmosisIbcQ> May 14 12:01:49 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:01:49Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > May 14 12:02:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:02:51Z","message":"SendOsmosisQueryR> May 14 12:02:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:02:51Z","message":"handleOsmosisIbcQ> May 14 12:02:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:02:51Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > May 14 12:03:47 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:03:47Z","message":"SendOsmosisQueryR> May 14 12:03:47 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:03:47Z","message":"handleOsmosisIbcQ> May 14 12:03:47 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:03:47Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > Any idea how to fix it? thank you
Roberto Griggio About 1 month ago
High Priority
Bug Report
Completed
Node validator problem
Output of our systemctl status cheqd-cosmovisor.service: May 14 12:00:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:00:51Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > May 14 12:01:49 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:01:49Z","message":"SendOsmosisQueryR> May 14 12:01:49 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:01:49Z","message":"handleOsmosisIbcQ> May 14 12:01:49 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:01:49Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > May 14 12:02:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:02:51Z","message":"SendOsmosisQueryR> May 14 12:02:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:02:51Z","message":"handleOsmosisIbcQ> May 14 12:02:51 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:02:51Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > May 14 12:03:47 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:03:47Z","message":"SendOsmosisQueryR> May 14 12:03:47 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","err":"module does not own channel capability: source_port: feeabs, source_channel: : channel capability not found","time":"2025-05-14T12:03:47Z","message":"handleOsmosisIbcQ> May 14 12:03:47 cheqd-node0-monokee cosmovisor[1172432]: {"level":"error","module":"server","module":"x/feeabs","time":"2025-05-14T12:03:47Z","message":"Error executeAllHostChainTWAPQuery module does not own channel capability: source_port: feeabs, source_channel: : channel capability > Any idea how to fix it? thank you
Roberto Griggio About 1 month ago
High Priority
Bug Report
Completed
P256 signing fails when using Askar as KMS
Raised on behalf of Timo from Animo On the P256 signing in Credo (brought this up a long time ago). When i add an authentication using Askar as KMS it fails, but if I use Node crypto directly it succeeds. It's odd as we have been using our P256 signing with Askar with a lot of other implementation correctly, but it's probably something to do with encoding then I guess? Additional context: We are going to add P-256 signing in Paradym, and if cheqd can support it we will also enable this for Cheqd DIDs. It's not high priority, mainly wanted to share this behvaiour that it does work with another crypto implementation
Fraser Edwards 2 months ago
Credo
Bug Report
Completed
P256 signing fails when using Askar as KMS
Raised on behalf of Timo from Animo On the P256 signing in Credo (brought this up a long time ago). When i add an authentication using Askar as KMS it fails, but if I use Node crypto directly it succeeds. It's odd as we have been using our P256 signing with Askar with a lot of other implementation correctly, but it's probably something to do with encoding then I guess? Additional context: We are going to add P-256 signing in Paradym, and if cheqd can support it we will also enable this for Cheqd DIDs. It's not high priority, mainly wanted to share this behvaiour that it does work with another crypto implementation
Fraser Edwards 2 months ago
Credo
Bug Report
In Progress
SDK expects serviceEndpoint to be an Array of Strings
Opened on behalf of Timo / Animo Bug raised in GitHub: https://github.com/cheqd/sdk/issues/436 DID Spec mentions: The value of the serviceEndpoint property MUST be a string, a map, or a set composed of one or more strings and/or maps. How can we reproduce this bug? Update a did document, where there is a service having serviceEndpoint that is a string. (I think it also applies to creating a did doc). Environment Not applicable Bug prevalence No response Which browser/client application did you encounter the bug in? (if applicable) No response Relevant log output
Fraser Edwards 2 months ago
Bug Report
In Progress
SDK expects serviceEndpoint to be an Array of Strings
Opened on behalf of Timo / Animo Bug raised in GitHub: https://github.com/cheqd/sdk/issues/436 DID Spec mentions: The value of the serviceEndpoint property MUST be a string, a map, or a set composed of one or more strings and/or maps. How can we reproduce this bug? Update a did document, where there is a service having serviceEndpoint that is a string. (I think it also applies to creating a did doc). Environment Not applicable Bug prevalence No response Which browser/client application did you encounter the bug in? (if applicable) No response Relevant log output
Fraser Edwards 2 months ago
Bug Report
Internal Review
Compress AnonCreds status lists
From Timo (Animo) Maybe we should update the cheqd anoncreds method to compress the status list (or anoncreds in general)? It's quite inefficient to put it as an array like this: https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:fdd80fdc-8756-491d-838d-ccd705b2776a/resources/c95a79db-fb74-4b00-a114-faa8ac12d629
cheqd/Creds Product Team 2 months ago
Credo
Feature Request
Internal Review
Compress AnonCreds status lists
From Timo (Animo) Maybe we should update the cheqd anoncreds method to compress the status list (or anoncreds in general)? It's quite inefficient to put it as an array like this: https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:fdd80fdc-8756-491d-838d-ccd705b2776a/resources/c95a79db-fb74-4b00-a114-faa8ac12d629
cheqd/Creds Product Team 2 months ago
Credo
Feature Request
In Progress
Unknown error writing to Cheqd mainnet
Transaction with ID 904E70D7044638A0A37103E32C00DB1031BD0198B08F25CEED7AA2B3F78AD061 was submitted but was not yet found on the chain. You might want to check later. There was a wait of 60 seconds We suddenly got this error when submitting a status list to cheqd mainnet for did did:cheqd:mainnet:c3a49697-6282-4fda-a0d9-c81d2f76e9fe and revocation registry definition did:cheqd:mainnet:c3a49697-6282-4fda-a0d9-c81d2f76e9fe/resources/9ed8e025-2697-477c-a49a-3ec8da44de3e
An Anonymous User 2 months ago
Credo
Bug Report
In Progress
Unknown error writing to Cheqd mainnet
Transaction with ID 904E70D7044638A0A37103E32C00DB1031BD0198B08F25CEED7AA2B3F78AD061 was submitted but was not yet found on the chain. You might want to check later. There was a wait of 60 seconds We suddenly got this error when submitting a status list to cheqd mainnet for did did:cheqd:mainnet:c3a49697-6282-4fda-a0d9-c81d2f76e9fe and revocation registry definition did:cheqd:mainnet:c3a49697-6282-4fda-a0d9-c81d2f76e9fe/resources/9ed8e025-2697-477c-a49a-3ec8da44de3e
An Anonymous User 2 months ago
Credo
Bug Report
In Progress
Credo Fee Handling
Problem with creating DIDs and DLRs on testnet. Receiving error message about the amount of fees required for the transaction. This never used to occur until the latest ledger upgrade.
An Anonymous User 2 months ago
High Priority
Bug Report
In Progress
Credo Fee Handling
Problem with creating DIDs and DLRs on testnet. Receiving error message about the amount of fees required for the transaction. This never used to occur until the latest ledger upgrade.
An Anonymous User 2 months ago
High Priority
Bug Report