You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Height param on wasm/contracts/<address>/store REST endpoint doesn't work on private full nodes, but works on lcd.terra.dev and gRPC endpoint. However, the header x-cosmos-block-height: <height> works on both private full nodes and on the public endpoint. For consistency's sake, it would be better to support the height param on the private full nodes too.
To Reproduce localhost:1317/terra/wasm/v1beta1/contracts/terra1jxazgm67et0ce260kvrpfv50acuushpjsz2y0p/store?height=6162743&query_msg=eyJwb29sIjoge319 produces a response with total_share: 590548093388 (among other things). localhost:1317/terra/wasm/v1beta1/contracts/terra1jxazgm67et0ce260kvrpfv50acuushpjsz2y0p/store?height=5138774&query_msg=eyJwb29sIjoge319 (notice the different height), also produces a response with total_share: 590548093388, which doesn't make sense because there is a height difference of almost a million.
The same queries to the lcd.terra.dev endpoint produces different total_share amounts.
Context & versions
Tested on private full node versions 0.5.13 and 0.5.14
(if applicable) suggested solution
Add the height param to all of the queries in the public build of Terra
The text was updated successfully, but these errors were encountered:
@YunSuk-Yeo this shouldn't matter. The data is there, node is returning the data just fine using cosmos height header @Zygimantass has mentioned. The problem is that height GET parameter is not taken into the account as it's never parsed. Eg. setting height in query string to "asdf" is not returning bad formatting error either.
Describe the bug
Height param on
wasm/contracts/<address>/store
REST endpoint doesn't work on private full nodes, but works on lcd.terra.dev and gRPC endpoint. However, the headerx-cosmos-block-height: <height>
works on both private full nodes and on the public endpoint. For consistency's sake, it would be better to support the height param on the private full nodes too.To Reproduce
localhost:1317/terra/wasm/v1beta1/contracts/terra1jxazgm67et0ce260kvrpfv50acuushpjsz2y0p/store?height=6162743&query_msg=eyJwb29sIjoge319
produces a response withtotal_share: 590548093388
(among other things).localhost:1317/terra/wasm/v1beta1/contracts/terra1jxazgm67et0ce260kvrpfv50acuushpjsz2y0p/store?height=5138774&query_msg=eyJwb29sIjoge319
(notice the different height), also produces a response withtotal_share: 590548093388
, which doesn't make sense because there is a height difference of almost a million.The same queries to the
lcd.terra.dev
endpoint produces different total_share amounts.Context & versions
Tested on private full node versions 0.5.13 and 0.5.14
(if applicable) suggested solution
Add the height param to all of the queries in the public build of Terra
The text was updated successfully, but these errors were encountered: