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
Back in the day, the EVM was meant to be totally separate from the blockchain code, something that could be run outside of ethereum, at least, that's how the EVM project was designed. However, the EVM itself is tightly-coupled with Ethereum (e.g. with opcodes related to getting block hashes, etc), and slowly but surely, we started to couple our EVM implementation with "hooks" into the Blockchain project so we had the necessary data available (e.g. AccountInterface). It now looks like trying to keep the two projects separate may be causing more confusion as the concepts themselves are tightly coupled. As such, this issue is to consider (and if so, implement) merging the EVM and Blockchain umbrella sub-apps. This would reduce a number of weird boundaries that produce... sub-optimal code.
The text was updated successfully, but these errors were encountered:
Back in the day, the EVM was meant to be totally separate from the blockchain code, something that could be run outside of ethereum, at least, that's how the EVM project was designed. However, the EVM itself is tightly-coupled with Ethereum (e.g. with opcodes related to getting block hashes, etc), and slowly but surely, we started to couple our EVM implementation with "hooks" into the Blockchain project so we had the necessary data available (e.g.
AccountInterface
). It now looks like trying to keep the two projects separate may be causing more confusion as the concepts themselves are tightly coupled. As such, this issue is to consider (and if so, implement) merging the EVM and Blockchain umbrella sub-apps. This would reduce a number of weird boundaries that produce... sub-optimal code.The text was updated successfully, but these errors were encountered: