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
One of the cited problems with Plasma running arbitrary EVM contracts is that there is no way to run arbitrary EVM code within the EVM without completely emulating the EVM. There is an EIP proposed for this issue in Ethereum. This is of course much simpler for x86, since it is Von Neumann architecture. The x86 VM is automatically capable of executing an arbitrary bytestream. However, there is no protection to prevent that external code from making state changes etc.
A potential solution is to allow x86 contracts to act as a hypervisor and to be a liaison between some arbitrary child code and the actual blockchain state, capable of using custom logic to determine if state changes etc should be propagated into the blockchain, or even to give the code custom data in place of real blockchain data, potentially allowing the simulation of external blockchain contracts on the Qtum blockchain with minimal expense. Another use case is to record all state changes that are made, and then to compare that the state changes made are as expected. This is a part of how Plasma could work with x86 contracts
Motivation
Rationale
Strategy
The text was updated successfully, but these errors were encountered:
Abstract
One of the cited problems with Plasma running arbitrary EVM contracts is that there is no way to run arbitrary EVM code within the EVM without completely emulating the EVM. There is an EIP proposed for this issue in Ethereum. This is of course much simpler for x86, since it is Von Neumann architecture. The x86 VM is automatically capable of executing an arbitrary bytestream. However, there is no protection to prevent that external code from making state changes etc.
A potential solution is to allow x86 contracts to act as a hypervisor and to be a liaison between some arbitrary child code and the actual blockchain state, capable of using custom logic to determine if state changes etc should be propagated into the blockchain, or even to give the code custom data in place of real blockchain data, potentially allowing the simulation of external blockchain contracts on the Qtum blockchain with minimal expense. Another use case is to record all state changes that are made, and then to compare that the state changes made are as expected. This is a part of how Plasma could work with x86 contracts
Motivation
Rationale
Strategy
The text was updated successfully, but these errors were encountered: