Learn evm expansion #208
Merged
Learn evm expansion #208
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
bohendo
commented
Jan 27, 2023
bohendo
commented
- Adds a page describing transaction traces, how to generate them, and tips on how to navigate them without getting lost.
- Adds another page with a symbolic reference for use while reading the yellow paper + mention of a more up-to-date EVM reference.
- Expands the evm opcodes page with pseudo-code for (almost) all of the opcodes & links from the table to a spot for more detailed discussions.
- Lastly, updates the readme to reflect the additions mentioned above.
montyly
reviewed
Jan 30, 2023
|
|
||
| So, you want to read the yellow paper. Before we dive in, keep in mind that the yellow paper is out of date and some in the community might refer to it as being depreciated. Check out the [BRANCHES.md](https://github.com/ethereum/yellowpaper/blob/master/BRANCHES.md) file of the [`yellowpaper` repository on github](https://github.com/ethereum/yellowpaper) to stay up-to-date on how closely this document tracks the latest version of the Ethereum protocol. At the time of writing, the yellow paper is up to date with the Berlin hardfork which occurred in April 2021. | ||
|
|
||
| For a more up-to-date reference, check out the [Ethereum Specification](https://ethereum.github.io/execution-specs/autoapi/ethereum/) which features a detailed description of each opcode *for each hardfork* in addition to reference implementations written in python. |
There was a problem hiding this comment.
We can also refer to https://github.com/crytic/building-secure-contracts/blob/master/learn_evm/eips_forks.md, to get visibility on the EIPs included for each fork
learn_evm/yellow-paper.md
Outdated
|
|
||
| That said, the yellow paper is still a rich resource for ramping up on the fundamentals of the Ethereum protocol. This document aims to provide some guidance and assistance in deciphering Ethereum's flagship specification. | ||
|
|
||
| As you review the following, keep in mind that additions and corrections are welcome and are covered by bounties from Trail of Bits. Join us in #ethereum on the [Empire Hacking Slack](https://empireslacking.herokuapp.com) to discuss Ethereum specifications and tool development. |
There was a problem hiding this comment.
I think we can remove the mention to the bounties, here and in the other section (I saw it at least in the opcode section). In practice this has low visibility, and repeating on some pages does not help
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.