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
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
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
Deliverables
Gain for the project
Publicly visible delivery
Size
M
Poker: https://leapdao.slack.com/archives/CAAGW85BR/p1556110873002700
Roles
bounty gardener: @troggy / 10%
bounty worker: @troggy / 70%
bounty reviewer: @sunify / 20%
The text was updated successfully, but these errors were encountered: