-
Notifications
You must be signed in to change notification settings - Fork 559
Need an api to recover execution result from the false-failed tx #1052
Comments
I think we should modularize the RPC so that projects can add their own namespaces and endpoints to existing namespaces. This would fix your issue without adding custom endpoints |
maybe add a custom grpc query in cronos is enough, no need to do this in ethermint, we'll try that. |
This type transaction should be correctly identified by Metamask, Explorer, Bridge, etc. It requires compliance with the eth_getTransactionReceipt API.
|
* make jsonrpc api namespaces extensible Closes: evmos#1052, evmos#1037 * Apply suggestions from code review Co-authored-by: Federico Kunze Küllmer <31522760+fedekunze@users.noreply.github.com>
* make jsonrpc api namespaces extensible Closes: evmos#1052, evmos#1037 * Apply suggestions from code review Co-authored-by: Federico Kunze Küllmer <31522760+fedekunze@users.noreply.github.com>
Proposal: Need an api to recover execution result from the false-failed tx
Current behavior:
On cronos mainnet, due to an old bug(cosmos/cosmos-sdk#10770), there are transactions that success on chain but return a failed result, although the bug itself is fixed, we need to figure out a way to patch the old data.
One solution is to support sth like:
debug_runTransactionByBlockAndIndex
, so we can rerun these transactions and get back the correct tx result.Desired behavior: The old tx data should be recovered too.
Use case: Fix the old tx result.
The text was updated successfully, but these errors were encountered: