Closed amorfc closed 1 year ago
Proposal vote endpoint: the reason for the error you get is that you are querying over a proposal which voting period has expired. here is an ex. on active proposal:
Seems proposal votes list not empty: maybe it's for the same reason as the previous case.
Depositor query by address
Proposal deposits endpoint:
there is only an issue with the amount here.
Proposal deposits endpoint:
there is only an issue with the amount here.
İ fixed that amount issue but did not push yet, also there is a new structure for this implementation which is complex a bit that why i need another point of view to be sure. 🙏
İ fixed that amount issue but did not push yet, also there is a new structure for this implementation which is complex a bit that why i need another point of view to be sure. 🙏
😎
Fixed
[x] Same with depositor query by address
"error": "Upstream error: status: Unknown, message: \"invalid Bech32 prefix; expected osmo, got osmovaloper\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"x-cosmos-block-height\": \"8746898\"} }"
[x] Proposal votes list empty. Grpc endpoints can cause this issue.
[x] Proposal vote endpoint
"error": "Upstream error: status: InvalidArgument, message: \"voter: axelar1etg9lerahhgvu34rq2jmwmcm7w7ztpmyxrfz6c not found for proposal: 41\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"x-cosmos-block-height\": \"6529144\"} }"
[x] Proposal deposits endpoint return
"error": "Upstream error: status: Unknown, message: \"transport error\", details: [], metadata: MetadataMap { headers: {} }"
even request goes throug v1&v1beta versions.[x] #72 "error": "Upstream error: status: Unknown, message: \"invalid Bech32 prefix; expected osmo, got osmovaloper\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"x-cosmos-block-height\": \"8745857\"} }" }```