The EVM Enforcer is a computation verification engine that allows on-chain enforcement of off-chain EVM execution.

Anyone who solved some off-chain execution can register a result with the Enforcer contract. A challenge period starts during which challengers can open disputes over the presented results. Disputes are delegated to the Verifier contract where solver and challenger play an interactive execution verification game. If the challenger wins, the execution results are deleted and the solver looses a bond. If the solver is able to defend the execution results throughout the challenge period, the result is accepted.

• What is the relationship to solEVM? The EVM enforcer is built on Andreas Olofsson's solEVM. Thank you Andreas 👏 !
• How is this different than Truebit? Truebit's interactive computation verification game uses a WebAssembly VM. We allow to run EVM bytecode.
• What do you use this for? We use this to enforce the correctness of transaction in Plasma Leap.

You are very welcome to contribute by:

• Picking beginner-friendly issues from the backlog.
• Joining the Discord channel to ask questions.
• Participating in the bi-weekly hangouts.

Please make sure to read the contribution guidelines.

You can run the tests like this:

yarn
yarn test

tools/deploy.js - is a little deployment helper script.

Additionally to the deployment variables you also have to provide the network (the network name in truffle-config). If the RPC provider does not support signing, you have to supply either privKey|PRIV_KEY or mnemonic|MNEMONIC as environment variables to this script.

You can run it like this:

network=geth verifierTimeout=1800 taskPeriod=43200 challengePeriod=21600 bondAmount=10000000000000000 maxExecutionDepth=10 ./tools/deploy.js

The runtime contract is EVMRuntime.sol. The contract is designed with extensibility in mind. The most basic contract which makes use of it is EthereumRuntime.sol, the contract has an execute function which is used to run code.

Other contracts which makes use of the EVMRuntime are:

• Verifier.sol

It also exists a corresponding runtime implementation on the JS side. You can take a look at the on-chain Verifier unit test on how it's used.

The off-chain Interpreter mimics the on-chain Stepper and together with the Merkelizer, creates a Merkle Root of the individual execution steps (before and after each opcode) given code, data and other runtime properties.

For the curious, you can checkout the on-chain Verifier.

The design decision that the EVMRuntime.sol will be the base 'class' for contracts needing a runtime environment is final, though the whole interface design is not final yet.

It is planned that the struct EVM will hold a pointer to memory where users can point to their custom data / structure, this property gives the most flexibility for developers working with the EVMRuntime without hitting contract size-, maximal stack depth or other limitations.

There are no blocks, so BLOCKHASH will always return 0. The only blockchain related parameters that can be set are those in the context object.