evm-opcodes VS Leesons-Modding-Instructions

It is very important for the smart contract developers and auditors to undertand that how solidity based smart contracts/EVM executes its fundamental tasks behind the scenes to get deep foundation of EVM. To know more about the other EVM opcodes, please visit Here and if you want to play with these opcodes in the real time playground, please visit EVM codes playground website .

Debug the transaction in Remix to get to the GAS opcode, which is what gasleft() is doing in the background. There, we will look at the remaining gas field in "Step Details". You can easily get there in several ways:

Each OPCODE has a fixed gas cost. The gas cost of a specific function within the smart contract is the sum of the gas costs of all it's OPCODES. You can find a list of all OPCODES and their associated gas costs here if interested.

And so, each instruction is given a metric that represents how intensive it is to execute, which is that instruction's gas cost, and users have to pay a fee based on how much gas in total a transaction consumes, which is the solution that the Ethereum devs (and the devs of other smart contract chains) have landed on, to address the above issue.

The EVM has a smaller instruction set of opcodes that are very tailored to Smart Contract development compared to what the JVM offers which is a wider set required for programming almost anything.

Everytging a smart contract can do is detailed here: https://github.com/crytic/evm-opcodes

For dynamic testing, I recommend building your own OS so you can write out logs, here’s a guide https://github.com/n0x-L/Leesons-Modding-Instructions Good luck