Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement getTransactionReceipt RPC #256

Closed
troggy opened this issue Apr 24, 2019 · 1 comment · Fixed by #293
Closed

Implement getTransactionReceipt RPC #256

troggy opened this issue Apr 24, 2019 · 1 comment · Fixed by #293
Assignees
Labels
bounty size-M effort of ~8h

Comments

@troggy
Copy link
Member

troggy commented Apr 24, 2019

Bounty

It is required for both web3 and ethers to observe transaction after sending (e.g. with web3.eth.sendTransaction, web3.eth.sendSignedTransaction and others).

The ultimate goal is to have sending methods to return proper PromiEvent for Web3 and proper TransactionResponse with working wait() function for Ethers. Both require getTransactionReceipt: web3, ethers. However, for websocket provider newBlockHeader subscription might also be needed (see #255, out of scope for this bounty)

Scope

  • implement getTransactionReceipt JSON RPC in leap-node. Should be compatible with Web3 and Ethers
  • verify it works at least with HTTP provider

Deliverables

  • updated leap-node
  • updated leap-core (at least typedef's will need to be changed)
  • updated integration tests using the new leap-node
  • updated docs at docs.leapdao.org

Gain for the project

  • allows to use familiar and robust approach to get/wait for status of the tx after sending

Publicly visible delivery

  • updated docs at docs.leapdao.org

Size

M
Poker: https://leapdao.slack.com/archives/CAAGW85BR/p1556110873002700

Roles

bounty gardener: @troggy / 10%
bounty worker: @troggy / 70%
bounty reviewer: @sunify / 20%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty size-M effort of ~8h
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant