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

Misleading simplification in the transation chapter #1155

Open
radeksvarz opened this issue Nov 9, 2022 · 0 comments
Open

Misleading simplification in the transation chapter #1155

radeksvarz opened this issue Nov 9, 2022 · 0 comments

Comments

@radeksvarz
Copy link

https://github.com/ethereumbook/ethereumbook/blob/develop/06transactions.asciidoc#transmitting-value-to-eoas-and-contracts

If the destination address (to) is a contract, then the EVM will execute the contract and will attempt to call the function named in the data payload of your transaction. If there is no data in your transaction, the EVM will call a fallback function ...

This simplification leads to the understanding that such contract's flow and checks are assured by EVM, while it is rather implemented by higher languages (Solidity, ...).

Minimal proxies are the examples, where such statement is not valid.

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

1 participant