Skip to content
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

Perfect the Ethereum Virtual Machine #1

Open
masonforest opened this issue Apr 4, 2018 · 2 comments
Open

Perfect the Ethereum Virtual Machine #1

masonforest opened this issue Apr 4, 2018 · 2 comments

Comments

@masonforest
Copy link
Member

masonforest commented Apr 4, 2018

Title

  OIP: 1001
  Title: Complete EVM
  Author: Mason Fischer <mason@kissr.co>
  Status: Draft
  Type: Standard
  Layer: Virtual Machine
  Created: 2018-04-04

Abstract

Before consensus can be reached we'll need a perfect replica of the Ethereum Virtual Machine. All Ethereum common tests should output the correct output state and gas left after each run.

Specification

The Ethereum Virtual Machine is formally specified in the Ethereum Yellow Paper

Implementation

Currently the majority of the Ethereum common tests are passing. The following tests produce incorrect output state or gas left after execution:

  • System Operations

    • CallToPrecompiledContract
    • callcodeToNameRegistrator0
    • callcodeToReturn1
    • createNameRegistratorValueTooHigh

Issue : exthereum/evm#34

@masonforest masonforest changed the title Pass remaining system_operations tests Complete EVM to match Geth and Parity Apr 4, 2018
@masonforest masonforest changed the title Complete EVM to match Geth and Parity Perfect the Ethereum Virtual Machine Apr 4, 2018
@hayesgm
Copy link

hayesgm commented Apr 5, 2018

Question: is the EVM fully specified in the Yellow Paper? I feel one of the areas we're lacking still is in some EIP's which haven't been back-ported into the Yellow Paper, or in gaps of the Yellow Paper.

@masonforest
Copy link
Member Author

I think they got all the Byzantium changes merged in to the Yellow Paper. If not though the common tests should be fully up to date and we can work off of those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants