Proxies and Upgradability - Minimal Proxy (EIP-1167) (opens on Substack in a new tab)
Examine how a minimal proxy reuses an implementation through delegation.
From bytecode and calldata to signatures, transactions, and contract architecture.
Start here
Begin with the original three-part series, then explore individual mechanisms in the archive below.
Read Part 1 on Substack (opens in a new tab)What is the EVM actually executing? Start with gas, bytecode, and the places a contract keeps its data.
Continue the original EVM internals series with a closer look at contract execution.
The third part of the original EVM internals series, continuing below Solidity’s abstractions.
Examine how a minimal proxy reuses an implementation through delegation.
What changes when the thing deploying a smart contract is another smart contract?
Follow the upgrade mechanism when the implementation holds the upgrade logic.
Explore how a transparent proxy separates administrative operations from user calls.
Compare how CREATE and CREATE2 determine the address of a new contract.
Compare batching at the contract level with batching requests to an RPC endpoint.
How do you observe native ETH transfers when there is no token Transfer event?
Explore the mechanics of following on-chain activity as it happens.
Look beneath Solidity events at the EVM’s logs and topics.
Compare a simulated call’s result with a trace of the execution behind it.
Understand the node and client behind an endpoint, and why that affects your queries.
Explore structured off-chain signing and the information an EIP-712 signature commits to.
Showing 12 of 37 articles