-
Notifications
You must be signed in to change notification settings - Fork 454
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
Ability to perform call from contract #235
Comments
I like a lot idea of having
revm/crates/revm/src/models.rs Lines 238 to 242 in 88c72a7
|
Perfect! I can start implementing that 🙂 |
I realised something. We can also have individual feature flags for the features and bundle then together in a feature flag What do you prefer? |
At hardhat we support the ability to call contracts from another contract when developing your own smart contract. So far we've been using
ethereumjs
, which supports this behaviour.We're rewriting part of our stack in Rust and using
revm
to do so. However,revm
strictly adheres toEIP-3607
to "Reject transactions from senders with deployed code": https://github.com/bluealloy/revm/blob/main/crates/revm/src/evm_impl.rs#L90In development, the security concern does not apply, so it would be nice to still be allowed to call contracts from a contract address. Is this something that you'd be willing to accept a PR for? If so, do you have a preference for how it should be implemented?
One option would be to use a
dev
feature flag that would disable that check.The text was updated successfully, but these errors were encountered: