antazoey

This work has been completed

@banteg What is all needed to start development on this? Do we need the coverage-setup or anything else with tracing support first? Also, is there anything else we should know...

You have to use events for transactions I believe. https://ethereum.stackexchange.com/questions/73787/solidity-return-value-of-smart-contract-transact I showed @Ninjagod1251 how to get the events from a receipt!

We are on eth-rlp 0.3.0 now

Closing as duplicate

did you try this: ``` "recommended-plugins": [ "ape-alchemy>=0.3", # Alchemy public network provider "ape-ens>=0.3", # ENS converter "ape-etherscan>=0.3", # Etherscan explorer plugin "ape-foundry>=0.3", # Foundry local and fork network EVM...

I just tried `pip install eth-ape'[recommended-plugins]'` in a fresh environment and it worked! I believe the culprit lies in the fact that `ape-foundry` was broken regarding its dependency constraints previously...

> Is there a preferred way to document those kind of kwargs? I see `block_identifier` coming up in the code but not docstrings or comments For yours, we may want...

I tried using this with the `ape-hardhat` plugin to run tests but I get errors `TypeError: send_transaction() got an unexpected keyword argument 'raise_on_fail'` so I am 🤔 It did work...

I am worried about this (from an ape-console environment): ```python receipt = contract.foo(..., raise_on_fail=False) ``` ^ this is not working unless I also provide the `gas_limit`. I am worried this...