This kanban board shows our team’s progress across bug reports, feature requests and incident reports.

Backlog

Next up

In Progress

In Review

Done

Track Our Progress

Currently by my reading of the docs, i’m able to update a DIDDoc with VMs of type:<ul><li><code>Ed25519VerificationKey2020</code></li><li><code>EcdsaSecp256k1VerificationKey2019</code></li><li><code>RsaVerificationKey2018</code></li></ul>(source) <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://docs.cheqd.io/product/advanced/sdk/did-module#supported-key-types">https://docs.cheqd.io/product/advanced/sdk/did-module#supported-key-types</a> Although the source code seems to indicate:<ul><li><code>JsonWebKey2020</code> (key types ECDSA, Ed25519 &amp; RSA are seemingly supported)</li><li><code>Ed25519VerificationKey2020</code></li><li><code>Ed25519VerificationKey2018</code></li></ul>(source) <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/cheqd/cheqd-node/blob/2089162a071d1a741696a256457d656fa9457968/x/did/types/diddoc_verification_method.go#L17">https://github.com/cheqd/cheqd-node/blob/2089162a071d1a741696a256457d656fa9457968/x/did/types/diddoc_verification_method.go#L17</a>It would be nice if it was also possible to push <code>Multikey</code> VM types. Anecdotally, i’ve seen this VM grow in popularity over the years, as it is able to represent a huge range of key types with a single VM type, and is also compact. Similar properties to JsonWebKey2020, but arguably more compact and could be overtaking it in popularity.The support for the VM could be done in the same way as JsonWebKey2020 - limited scope to ed25519, ecdsa &amp; rsa key type support.Supporting multikey VMs in cheqd DID Docs may improve interoperability in systems which prefer Multikey to it’s alternatives (e.g. JsonWebKey2020)

Multikey VerificationMethod support

George Mulhearn

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>

Credo

ACA-Py

Compress AnonCreds status lists

cheqd Product Team

UX/UI Issue: Low/ModeratePriority: Low/ModerateWe 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?ExampleWhat 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.<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932eb9b01cff301a318544a/019aeee4-9908-7fae-97c7-35cb62ed2c08/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932eb9b01cff301a318544a/019aeee4-9908-7fae-97c7-35cb62ed2c08/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=da8d9d4bdcc80294b0197cfc127a2971e97b822f3fd338f0d4179b61dc09720a" data-featurebase-content-filename="image.png">

To Do / To Fix

cheqd Studio

Staging: Studio: Credential Identification - UX

Matthew Arnold

Revocation registries have limited size to a relatively small amount of entries. It would be fantastic to bump the size, and improve the efficiency of how these are stored and indexed on ledger

cheqd Network

Improve revocation registry size

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?

Studio: Staging: Session timer

Please create documentation around how multiple resources can be batched together into a single transaction / block. Currently, there is no clear way to achieve this. A diagram showing the logic would be very helpful

Improve / Understand batching logic

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.

Abnormal gas fee request

User

Bug: SeverePriority: HighThis 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.<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932ef9707b23bceadb1cab6/019aeef7-14d9-77a0-92d9-e2a7257f698f/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932ef9707b23bceadb1cab6/019aeef7-14d9-77a0-92d9-e2a7257f698f/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=df8ed96291e087ec65ca05033d1213e75d2353d1009c6dd52e2f4128188c442e" data-featurebase-content-filename="image.png"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932ef9707b23bceadb1cab6/019aeef6-c6d6-7a7f-aef9-17c65ac88469/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932ef9707b23bceadb1cab6/019aeef6-c6d6-7a7f-aef9-17c65ac88469/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=8085a8f1046ab029bd186f29e3e48cc496b93bb0821e761d8188c5f0b9ea021d" data-featurebase-content-filename="image.png"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932ef9707b23bceadb1cab6/019aeef3-d962-74cf-b0e1-7fcb89cc42bd/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932ef9707b23bceadb1cab6/019aeef3-d962-74cf-b0e1-7fcb89cc42bd/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=774794cbdd277cbb1db5d90197a2c39fc2460d687bcaa795fe3cefa98940e451" data-featurebase-content-filename="image.png"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932ef9707b23bceadb1cab6/019aeef4-61ab-7c2a-ba88-7cc8e1d77081/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932ef9707b23bceadb1cab6/019aeef4-61ab-7c2a-ba88-7cc8e1d77081/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=e8e6aeb2e157ba8098e3922ede2f2ab3bc6a45ec545acdea471915b2ac10c450" data-featurebase-content-filename="image.png">

Completed

Studio: Staging: Verification of Suspended Credential

From Glenn (CEO @ Affinidi)One of your engineers (<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/DaevMithran">https://github.com/DaevMithran</a>) 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 <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://crates.io">crates.io</a> and <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://crates.io">crates.io</a> is failing it because it is pedantic on package names etc. I had a Quick Look at the OWF repo code <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/openwallet-foundation/vcx/tree/main/did_core/did_methods/did_cheqd">https://github.com/openwallet-foundation/vcx/tree/main/did_core/did_methods/did_cheqd</a> 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: <ol><li>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</li><li>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).</li></ol>

DID Resolver

Cheqd Rust Resolver - Crates.io deployment failing

Fraser Edwards

I wanted to reach out about an operational challenge we’re experiencing with <code>cheqd/did-resolver</code> and <code>cheqd/did-registrar</code> that a fallback mechanism could solve.The Problem: We’re running into issues with testnet accessibility. When your testnet nodes are behind the firewall (blocking p2p connections), our self-hosted node can’t join the network, which breaks our applications that are configured to use our local endpoints.Current Manual Workaround:<ol><li>Testnet nodes go behind firewall → our node can’t sync</li><li>We manually update deployments to point at official endpoints (<code>grpc.cheqd.network:443</code>, <code>https://rpc.cheqd.network</code>)</li><li>When firewall is removed → our node can rejoin the network</li><li>We manually update deployments back to our local endpoints</li></ol>This creates a lot of operational overhead and requires manual intervention every time network accessibility changes.Proposed Solution: Could you add automatic fallback functionality to both projects? Something like:<ul><li>did-resolver: Try our gRPC endpoint first, if connection fails (<code>5xx</code>, or <code>Connection Refused</code>) → automatically fall back to <code>grpc.cheqd.network:443</code></li><li>did-registrar: Try our RPC endpoint first, if connection fails (<code>5xx</code>, or <code>Connection Refused</code>) → automatically fall back to <code>https://rpc.cheqd.network</code></li></ul>The Flow We’re Envisioning:<ol><li>Try primary endpoint (our node)</li><li>On connection error → switch to official endpoints</li><li>When primary comes back online → switch back automatically</li></ol>This would eliminate the need for manual deployment updates every time testnet accessibility changes and make our infrastructure much more resilient to network-level issues.

DID Registrar

Fallback Endpoints for DID Resolver / DID Registrar

<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.

Cheqd Studio Update DID

Luke Nispel

Bug: LowPriority: LowWhile 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.<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932edd964bd4dc1b9844503/019aeeeb-f7b8-7be0-ae30-2421952fcac3/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932edd964bd4dc1b9844503/019aeeeb-f7b8-7be0-ae30-2421952fcac3/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=438feea84f69b56923d5340cb06f506b3f3a9143338edbe132cf06dd3a7dd803" data-featurebase-content-filename="image.png">

Studio: Staging: Manage Credentials - Status Mismatch

Bug Impact: HighPriority: 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 listIf it should match, then this is definitely broken. <img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932e57f9d3644c71f630aae/019aeecd-0065-7cf9-9fe6-019f9ddc9c31/b64u-aW1hZ2UucG5n.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932e57f9d3644c71f630aae/019aeecd-0065-7cf9-9fe6-019f9ddc9c31/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=f895343b9dcc8d638353a87fc3f765506008ececf9e6e8b7ec9d019188f97951" data-featurebase-content-filename="image.png"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/6932e57f9d3644c71f630aae/019aeecc-7e9e-7d16-9ac1-7b63b4c012d2/b64u-U2NyZWVuc2hvdCAyMDI1LTEyLTA1IDEzNTE1OS5wbmc.png" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/6932e57f9d3644c71f630aae/019aeecc-7e9e-7d16-9ac1-7b63b4c012d2/b64u-U2NyZWVuc2hvdCAyMDI1LTEyLTA1IDEzNTE1OS5wbmc.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=bb2d0b19060654410e912f5f5faa82f406233e8fece7dba0a74a145b565beda2" data-featurebase-content-filename="Screenshot 2025-12-05 135159.png">

Studio: Staging: StatusList Message Status Size Definition Mismatch

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.

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

James Clark

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 <img data-width="100%" data-align="left" data-featurebase-content-key="67ff201042ee2fbfa416d563/post/68ebdc7a64c0ad476a5c40a5/0199d955-167e-7dd1-9d93-67dfad8c33ae/b64u-U2NyZWVuc2hvdCAyMDI1LTEwLTEyIDE4NDgyOS5qcGc.jpeg" data-featurebase-content-filename="Screenshot 2025-10-12 184829.jpg" src="https://67ff201042ee2fbfa416d563.featurebase-attachments.com/c/post/68ebdc7a64c0ad476a5c40a5/0199d955-167e-7dd1-9d93-67dfad8c33ae/b64u-U2NyZWVuc2hvdCAyMDI1LTEwLTEyIDE4NDgyOS5qcGc.jpeg?X-Amz-Expires=3600&amp;X-Amz-Date=20260215T020000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260215%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=62aff0609a3695cb02a36fa83284c4547a0d9cd30f89042d2e4e5e5edf200d08">

account/create

sid030sid

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).

Ensure Credo and React Native can use the latest cosmjs libraries

Timo Glastra

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

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.