Plant chage error

Internal error: You passed an empty string for 'flow_data[subscription_update_confirm][items][0][price]'. We assume empty values are an attempt to unset a parameter; however 'flow_data[subscription_update_confirm][items][0][price]' cannot be unset. You should remove 'flow_data[subscription_update_confirm][items][0][price]' from your request or supply a non-empty value.

cannot change card and plan

Plan changes and credit card changes are not possible.

Abnormal gas fee request

Error creating DID Internal error: Error: Error: Broadcasting transaction failed with code 1 (codespace: undefined). Log: insufficient fee: need at least 213962289640, got 50000000000 Encountered this error during did creation in Cheqd Studio Dashboard.

Studio: Staging: Verification of Suspended Credential

Bug: Severe Priority: High This is too much of a major bug. Unfortunately, the result from verifying a suspended credential is returned as still being valid. This is extremely misleading. And in addition, a revoked credential in my list comes back as valid when I verify. Using the features of our own platform, revocation appears to not to be working.

Studio: Staging: Manage Credentials - Status Mismatch

Bug: Low Priority: Low While managing credentials, the Status field dos not include suspended. Also, what if I have custom status as defined within my Status List that do not conform to this selection criteria? Which brings into question, should we have a way to see all custom types? I could have hundreds of thousands of credentials for products in my supply chain inventory right now. I could also have a good number of Status list custom statuses which are accounted for in this filter.

Staging: Studio: Credential Identification - UX

UX/UI Issue: Low/Moderate Priority: Low/Moderate We need to come up with a better way to identify which credentials are which in this list. If I need to delete one or more of 131072 indices how do I know what I am deleting? Example What if I am closing a department of 100 staff and moving them to a different department or something, how do I know who is who? We need to name the credentials, or be able to click them and have a modal, or some sort of search which will pull data from fields.

Studio: Staging: StatusList Message Status Size Definition Mismatch

Bug Impact: High Priority: High The ‘revocation’ action in my status list does not match how I configured it in Status messages. This might be a misunderstanding from my side, I have not created any credentials yet. I would assume that how I configure my list actions and messages would be reflected in the actions for the selected status list If it should match, then this is definitely broken.

Studio: Staging: Session timer

I have been soft logged out twice while trying to review this page section, the second time while filling out my last ticket. Can we please check the session timer again?

Unable to update Cheqd did with DIDComm V1 Service endpoint on Credo

1) Using Credo v0.5.14-0.5.17 create a cheqd did, with or without an existing DIDDoc. 2) Then immediately after successful creation, add a DIDCommV1 Service endpoint to the DIDDoc of the created did. 3) And then update the cheqd did with the newly updated DIDDoc. Step 3 should result in the following error: 'unknownError: failed to execute message; message index: 0: there should be at least one valid signature by did:cheqd:testnet:52ae96fb-66cd-4945-9914-39b7ff638243 (old version): invalid signature detected' With the did referenced in the error message being the did that was created in step 1.

account/create

Hi, I get the following error while calling the “account/create” endpoint for getting a token so that my client can use the API endpoints of cheqd studio. Maybe the error: "Internal Error: Cannot read properties of undefined (reading 'kid')" is a bug? See the attached picture to replicate the error. Regards, Sid

Cheqd Rust Resolver - Crates.io deployment failing

From Glenn (CEO @ Affinidi) One of your engineers (https://github.com/DaevMithran) submitted a PR to integrate Cheqd into our DID Resolver - thank you! Unfortunately we can’t push this to release because the Cheqd code is being sourced from the OWF git repo which hasn’t been published on crates.io and crates.io is failing it because it is pedantic on package names etc. I had a Quick Look at the OWF repo code https://github.com/openwallet-foundation/vcx/tree/main/did_core/did_methods/did_cheqd It is old, out of date and needs some love 😊 I am going to hold the Cheqd implementation as it is breaking our own CICD toolchain (and it is pulling in a rather large git repo). Do you have a preference on the following solutions: Pull the Cheqd DID implementation out of OWF and you publish a standalone Rust Library of the Cheqd resolver. Affinidi can then integrate with this cleanly If you have dev documentation on the gRPC details of resolving Cheqd DID’s, I can whip up a did-cheqd native crate for you (similar to the other DID-methods in the eco-system).

Ensure Credo and React Native can use the latest cosmjs libraries

We got a security report because the cheqd SDK in Credo depends on two versions of cosmjs libraries. One using recent cosmjs versions for ESM, and one using outdated cosmjs libraries which depends on a really old version of axios with critical vulnerabilities. I want to open this bug report to track the progress of using the latest cosmjs libraries in Credo. I think we will have to update Credo to use ESM, and thus also all projects and libraries depending on Credo, since cosmjs now only supports ESM. I want to check whether we see other approaches besides Credo updating to ESM (I’ll try to prioritize it, but it will take a while to do this).

cheqd studio language

Language > need to replace American English with British > e.g. decentralized decentralised, and also use more commercial terms. Please contact the marketing team once the product is ready to be scaled, we will help polish the wordings.

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.

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

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

Credo: Community reported bug

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

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

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