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
While testing some contracts in Remix (which uses ethereumjs-vm) I encountered a problem with delegatecall to a contract that call's another contract. It seems as of present it throws.
The flow is as follows:
[Contract A] -> delegatecall -> [Contract B] -> call -> [Contract C] (to cause state change in C)
It seems throw out of the box after delegate call. I can confirm the same code works on testnet/mainnet with no problems. I cannot share that code under Company policy. However, if needed I can provide sample code later on (with working contexts shifted).
Thanks!
The text was updated successfully, but these errors were encountered:
Would very much assume that such a common pattern as described in the issue is at least meanwhile part of the official test suite, also the likely related issues referenced by @axic are both closed in the meantime.
Beyond, no activity since end of 2017, will close. Feel free to reopen if necessary.
While testing some contracts in Remix (which uses ethereumjs-vm) I encountered a problem with
delegatecall
to a contract thatcall
's another contract. It seems as of present it throws.The flow is as follows:
[Contract A] -> delegatecall -> [Contract B] -> call -> [Contract C] (to cause state change in C)
It seems throw out of the box after delegate call. I can confirm the same code works on testnet/mainnet with no problems. I cannot share that code under Company policy. However, if needed I can provide sample code later on (with working contexts shifted).
Thanks!
The text was updated successfully, but these errors were encountered: