Bytecode Tuesday

On this week we're going to implement functions that can be called by any ethereum account or smart contract. Is important to understand how function call work under the hood to be able to write better and safer smart contract, optimize, and integrate with any tooling available today. Additionally, this way we can prepare for future updates where EVM get's improved. We are...

This week, we're diving into a recent (Dencun update) and powerful EVM feature: Transient Storage.Why Do We Need Transient Storage?We already know the three main data regions in the EVM: the stack witch is super fast but only lasts for the current instruction, the memory that resets after each all a...

This week, we cover something even more fundamental: the three data regions of the EVM. Let’s recall them from the last post:Stack for last-in, first-out temporary values,Memory for intra-transaction data (a byte array that resets every call), andStorage slots for persistent st...

This week, we're going a level deeper: Opcodes.What is an Opcode?An opcode (short for operation code) is a single instruction that tells the EVM what to do. Think of it like a Lego block: each opcode does one very specific thing...

Today we’re tracing the two distinct journeys your contract takes: one when you deploy it, and another each time it’s called.1. Writing and CompilingYou start with a .sol or .vy file in Solidity or Vyper, defining functions, state variables and control flow in human-readable form. When...