Backlog

Next up

In Progress

Done

Main Roadmap

<pre><code class="language-typescript">isDIDArray: (value: Validatable) =&gt; {
		const res = new DIDArrayValidator().validate((value as string[]).map((v) =&gt; (v.includes('#') ? v.split('#')[0] : v)));
		if (!res.valid) {
			throw new Error(res.error);
		}
		return true;
	},</code></pre>Am I write to consider this a fix for checking the authentication property for the update did api endpoint validator in Cheqd Studio? <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/cheqd/studio/blob/140dcea007da52f0fc4aea1eb6f2ca65aef0327c/src/controllers/api/did.ts#L131">https://github.com/cheqd/studio/blob/140dcea007da52f0fc4aea1eb6f2ca65aef0327c/src/controllers/api/did.ts#L131</a> I am attempting to update the authentication but its failing during validation unless I make the above change.

To do / to fix

Low Priority

cheqd Studio

Cheqd Studio Update DID

Luke Nispel

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 <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/cheqd/studio/issues/694">https://github.com/cheqd/studio/issues/694</a>

Missing validator Dep

An Anonymous User

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: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:fdd80fdc-8756-491d-838d-ccd705b2776a/resources/c95a79db-fb74-4b00-a114-faa8ac12d629">https://resolver.cheqd.net/1.0/identifiers/did:cheqd:mainnet:fdd80fdc-8756-491d-838d-ccd705b2776a/resources/c95a79db-fb74-4b00-a114-faa8ac12d629</a>

Internal Review

Credo

ACA-Py

Compress AnonCreds status lists

cheqd/Creds Product Team

Opened on behalf of Timo / Animo Bug raised in GitHub:<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/cheqd/sdk/issues/436">https://github.com/cheqd/sdk/issues/436</a>DID Spec mentions:<blockquote>The value of the serviceEndpoint property MUST be a <a target="_blank" rel="nofollow" class="link" href="https://infra.spec.whatwg.org/#string">string</a>, a <a target="_blank" rel="nofollow" class="link" href="https://infra.spec.whatwg.org/#string">map</a>, or a <a target="_blank" rel="nofollow" class="link" href="https://infra.spec.whatwg.org/#ordered-set">set</a> composed of one or more <a target="_blank" rel="nofollow" class="link" href="https://infra.spec.whatwg.org/#string">strings</a> and/or <a target="_blank" rel="nofollow" class="link" href="https://infra.spec.whatwg.org/#string">maps</a>.</blockquote><h3 style="text-align: start">How can we reproduce this bug?</h3><ol><li>Update a did document, where there is a service having <code>serviceEndpoint</code> that is a string.</li></ol>(I think it also applies to creating a did doc).<h3 style="text-align: start">Environment</h3>Not applicable<h3 style="text-align: start">Bug prevalence</h3>No response<h3 style="text-align: start">Which browser/client application did you encounter the bug in? (if applicable)</h3>No response<h3 style="text-align: start">Relevant log output</h3>

SDK expects serviceEndpoint to be an Array of Strings

Fraser Edwards

<pre><code>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 </code></pre>We suddenly got this error when submitting a status list to cheqd mainnet for did <code>did:cheqd:mainnet:c3a49697-6282-4fda-a0d9-c81d2f76e9fe</code> and revocation registry definition <code>did:cheqd:mainnet:c3a49697-6282-4fda-a0d9-c81d2f76e9fe/resources/9ed8e025-2697-477c-a49a-3ec8da44de3e</code>

Unknown error writing to Cheqd mainnet

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.

High Priority

Credo Fee Handling

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 &gt;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&gt;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&gt;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 &gt;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&gt;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&gt;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 &gt;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&gt;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&gt;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 &gt; Any idea how to fix it? thank you

Completed

Node validator problem

Roberto Griggio

Credo: Community reported bug

Raised on behalf of Timo from AnimoOn 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