Clearer error on contract execution error during call()
Open
Good First Issue
priority: p2 normal
- Dominant language
- Python
- Stars
- 5.5k
- Forks
- 1.7k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 2
Description
### What was wrong?
When a contract error happens during a call, usually we let the eth-abi exception raise through. This makes users think that web3.py is broken. eg~ https://github.com/ethereum/web3.py/issues/185
### How can it be fixed?
After checking that there is code at the contract address, raise a `ContractError` indicating that something went wrong in the execution of the contract, so it didn't return any value at all.
Contributor guide
Assessment
This issue has not been assessed yet.