dido:public:ra:xapend:xapend.b_stds:defact:ethereum:ethereum_vm:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:ethereum_vm:start [2021/08/18 11:10] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:ethereum_vm:start [2022/03/23 11:08] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Ethereum: Ethereum Virtual Machine (EVM) ==== | ==== Ethereum: Ethereum Virtual Machine (EVM) ==== | ||
| - | [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum| return to the Ethereum Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:start| return to the Ethereum Standards ]] |
| <table> | <table> | ||
| Line 16: | Line 16: | ||
| === Overview === | === Overview === | ||
| - | : //The Ethereum [[dido:public:ra:xapend:xapend.a_glossary:v:vm|Virtual Machine]] or EVM is the runtime environment for smart contracts in [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]]. It is not only sandboxed but actually completely isolated, which means that code running inside the EVM has no access to network, filesystem or other processes. [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contracts|Smart contracts]] even have limited access to other smart contracts.// | + | : //The Ethereum [[dido:public:ra:xapend:xapend.a_glossary:v:vm|Virtual Machine]] or EVM is the runtime environment for smart contracts in [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]]. It is not only sandboxed but actually completely isolated, which means that code running inside the EVM has no access to network, filesystem or other processes. [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contract|Smart contracts]] even have limited access to other smart contracts.// |
| : **Accounts** | : **Accounts** | ||
| Line 32: | Line 32: | ||
| : **Instruction Set** | : **Instruction Set** | ||
| : //The instruction set of the EVM is kept minimal in order to avoid incorrect or inconsistent implementations which could cause consensus problems. All instructions operate on the basic data type, 256-bit words or on slices of memory (or other byte arrays). For a complete list, please see the list of opcodes as part of the inline assembly documentation. ** [[https://solidity.readthedocs.io/en/v0.5.8/assembly.html#opcodes | REVIEW EVM OPCODES]] **// | : //The instruction set of the EVM is kept minimal in order to avoid incorrect or inconsistent implementations which could cause consensus problems. All instructions operate on the basic data type, 256-bit words or on slices of memory (or other byte arrays). For a complete list, please see the list of opcodes as part of the inline assembly documentation. ** [[https://solidity.readthedocs.io/en/v0.5.8/assembly.html#opcodes | REVIEW EVM OPCODES]] **// | ||
| + | : **Note:** This link is outdated. Look in [[https://docs.soliditylang.org/en/v0.8.13/assembly.html] Solidity 0.8.13]] and [[https://docs.soliditylang.org/en/v0.8.13/yul.html#yul | Yul (previously also called JULIA or IULIA) ]] | ||
| : **Message Calls** | : **Message Calls** | ||
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/ethereum_vm/start.1629299447.txt.gz · Last modified: 2021/08/18 11:10 by murphy
