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
I'm getting the following error while querying a recent transaction on mainnet:
Request:
$ curl -X GET -H 'accept: application/json' http://192.168.211.86:26657/tx?hash=0x19E4AE06F30B2991EB8A5302BB9ED4AD2AC35163FC92F3CCED6C3ACBC6428B96&prove=false
Response:
{"jsonrpc":"2.0","id":-1,"error":{"code":-32603,"message":"Internal error","data":"tx (19E4AE06F30B2991EB8A5302BB9ED4AD2AC35163FC92F3CCED6C3ACBC6428B96) not found"}}
The response is the same when prove=true. I can see the transaction on this explorer, so the transaction exists: https://celenium.io/tx/19e4ae06f30b2991eb8a5302bb9ed4ad2ac35163fc92f3cced6c3acbc6428b96?tab=messages. I also tried the communty endpoints provided here and most of them return responses.
Is there a configuration I could be missing on my node. The node has statesync set to false, fastsync set to true and indexing set to kv. I can provide additional information if needed
Version
2.3.1
Steps to Reproduce
Start celestia-app node
After syncing to head, run $ curl -X GET -H 'accept: application/json' http://<ip-address:port>/tx?hash=0x19E4AE06F30B2991EB8A5302BB9ED4AD2AC35163FC92F3CCED6C3ACBC6428B96&prove=false.
Optionally try with prove=false.
The error can be reproduced with the following community RPC endpoints
rpc.celestia.nodestake.top
rpc.lunaroasis.net
celestia.rpc.stakin-nodes.com
The text was updated successfully, but these errors were encountered:
Summary of Bug
I'm getting the following error while querying a recent transaction on mainnet:
Request:
Response:
The response is the same when
prove=true
. I can see the transaction on this explorer, so the transaction exists: https://celenium.io/tx/19e4ae06f30b2991eb8a5302bb9ed4ad2ac35163fc92f3cced6c3acbc6428b96?tab=messages. I also tried the communty endpoints provided here and most of them return responses.Is there a configuration I could be missing on my node. The node has
statesync
set to false,fastsync
set to true andindexing
set tokv
. I can provide additional information if neededVersion
2.3.1
Steps to Reproduce
celestia-app
node$ curl -X GET -H 'accept: application/json' http://<ip-address:port>/tx?hash=0x19E4AE06F30B2991EB8A5302BB9ED4AD2AC35163FC92F3CCED6C3ACBC6428B96&prove=false
.Optionally try with
prove=false
.The error can be reproduced with the following community RPC endpoints
The text was updated successfully, but these errors were encountered: