In Review
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.
User 20 days ago
Bug Reports
In Review
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.
User 20 days ago
Bug Reports
In Progress
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.
User 29 days ago
Bug Reports
In Progress
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.
User 29 days ago
Bug Reports
Completed
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
Completed
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
Completed
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
Completed
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
Completed
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
Completed
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.
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
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?
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
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?
Matthew Arnold 2 months ago
cheqd Studio
Bug Reports
Completed
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.
James Clark 3 months ago
Credo
Bug Reports
Completed
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.
James Clark 3 months ago
Credo
Bug Reports
Completed
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
sid030sid 4 months ago
cheqd Studio
Bug Reports
Completed
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
sid030sid 4 months ago
cheqd Studio
Bug Reports
Completed
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).
Fraser Edwards 4 months ago
DID Resolver
Bug Reports
Completed
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).
Fraser Edwards 4 months ago
DID Resolver
Bug Reports
Completed
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).
Timo Glastra 4 months ago
Credo
Bug Reports
Completed
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).
Timo Glastra 4 months ago
Credo
Bug Reports
Backlog
Multikey VerificationMethod support
Currently by my reading of the docs, i’m able to update a DIDDoc with VMs of type: Ed25519VerificationKey2020 EcdsaSecp256k1VerificationKey2019 RsaVerificationKey2018 (source) https://docs.cheqd.io/product/advanced/sdk/did-module#supported-key-types Although the source code seems to indicate: JsonWebKey2020 (key types ECDSA, Ed25519 & RSA are seemingly supported) Ed25519VerificationKey2020 Ed25519VerificationKey2018 (source) https://github.com/cheqd/cheqd-node/blob/2089162a071d1a741696a256457d656fa9457968/x/did/types/diddoc_verification_method.go#L17 It would be nice if it was also possible to push Multikey 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 & 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)
George Mulhearn 4 months ago
Feature Requests
Backlog
Multikey VerificationMethod support
Currently by my reading of the docs, i’m able to update a DIDDoc with VMs of type: Ed25519VerificationKey2020 EcdsaSecp256k1VerificationKey2019 RsaVerificationKey2018 (source) https://docs.cheqd.io/product/advanced/sdk/did-module#supported-key-types Although the source code seems to indicate: JsonWebKey2020 (key types ECDSA, Ed25519 & RSA are seemingly supported) Ed25519VerificationKey2020 Ed25519VerificationKey2018 (source) https://github.com/cheqd/cheqd-node/blob/2089162a071d1a741696a256457d656fa9457968/x/did/types/diddoc_verification_method.go#L17 It would be nice if it was also possible to push Multikey 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 & 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)
George Mulhearn 4 months ago
Feature Requests
Rejected
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.
Teresa 5 months ago
cheqd Studio
Bug Reports
Rejected
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.
Teresa 5 months ago
cheqd Studio
Bug Reports
Improve / Understand batching logic
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
cheqd Product Team 6 months ago
cheqd Network
Feature Requests
Improve / Understand batching logic
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
cheqd Product Team 6 months ago
cheqd Network
Feature Requests
Improve revocation registry size
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 Product Team 6 months ago
cheqd Network
Feature Requests
Improve revocation registry size
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 Product Team 6 months ago
cheqd Network
Feature Requests
Completed
Fallback Endpoints for DID Resolver / DID Registrar
I wanted to reach out about an operational challenge we’re experiencing with cheqd/did-resolver and cheqd/did-registrar 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: Testnet nodes go behind firewall → our node can’t sync We manually update deployments to point at official endpoints (grpc.cheqd.network:443, https://rpc.cheqd.network) When firewall is removed → our node can rejoin the network We manually update deployments back to our local endpoints 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: did-resolver: Try our gRPC endpoint first, if connection fails (5xx, or Connection Refused) → automatically fall back to grpc.cheqd.network:443 did-registrar: Try our RPC endpoint first, if connection fails (5xx, or Connection Refused) → automatically fall back to https://rpc.cheqd.network The Flow We’re Envisioning: Try primary endpoint (our node) On connection error → switch to official endpoints When primary comes back online → switch back automatically 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.
cheqd Product Team 6 months ago
DID Registrar
Feature Requests
Completed
Fallback Endpoints for DID Resolver / DID Registrar
I wanted to reach out about an operational challenge we’re experiencing with cheqd/did-resolver and cheqd/did-registrar 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: Testnet nodes go behind firewall → our node can’t sync We manually update deployments to point at official endpoints (grpc.cheqd.network:443, https://rpc.cheqd.network) When firewall is removed → our node can rejoin the network We manually update deployments back to our local endpoints 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: did-resolver: Try our gRPC endpoint first, if connection fails (5xx, or Connection Refused) → automatically fall back to grpc.cheqd.network:443 did-registrar: Try our RPC endpoint first, if connection fails (5xx, or Connection Refused) → automatically fall back to https://rpc.cheqd.network The Flow We’re Envisioning: Try primary endpoint (our node) On connection error → switch to official endpoints When primary comes back online → switch back automatically 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.
cheqd Product Team 6 months ago
DID Registrar
Feature Requests
Completed
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 8 months ago
cheqd Studio
Bug Reports
Completed
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 8 months ago
cheqd Studio
Bug Reports
Completed
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 8 months ago
cheqd Studio
Bug Reports
Completed
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 8 months ago
cheqd Studio
Bug Reports
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 9 months ago
Bug Reports
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 9 months ago
Bug Reports