Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

RPC eth_getTransactionByBlockNumberAndIndex does not work as expected when querying a cosmos transaction #809

Open
banishee opened this issue Feb 17, 2021 · 1 comment
Labels
rpc Ethereum JSON-RPC related issues and PRs Status: On Ice Type: User Reported

Comments

@banishee
Copy link

System info: [Include Ethermint commit, operating system name, and other relevant details]

Steps to reproduce:

  1. Assuming the transaction index 9 is belong to a cosmos transaction, calls this api with such a parameter:
params: [
   '0x29c', //668
   '0x9' // 9
]
  1. the result will be null

Expected behavior: [What you expected to happen]

  • It is supposed to return a transaction object in any condition, as long as it receives the legal parameter.

Actual behavior: [What actually happened]

  • It returns null when the index does not belong to MsgEthereumTx transaction

Additional info: [Include gist of relevant config, logs, etc.]

@github-actions
Copy link

github-actions bot commented Apr 4, 2021

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale stale PRs that will be closed if no further action occurs label Apr 4, 2021
@araskachoi araskachoi reopened this Apr 12, 2021
@araskachoi araskachoi reopened this May 10, 2021
@araskachoi araskachoi added rpc Ethereum JSON-RPC related issues and PRs Type: User Reported labels May 10, 2021
@github-actions github-actions bot removed the stale stale PRs that will be closed if no further action occurs label May 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
rpc Ethereum JSON-RPC related issues and PRs Status: On Ice Type: User Reported
Projects
None yet
Development

No branches or pull requests

2 participants