Liquid staking gives you a tradeable token representing your staked position. How liquid staking tokens work, why the peg is an arbitrage outcome rather than a guarantee, and what stacks on top of ordinary staking risk.

On Ethereum, the validator proposing a block usually doesn't build it. How the mev-boost auction works, why blind signing holds the market together, where the relay trust sits, and what enshrining PBS would change.

Ethereum's rhyming roadmap names get recited as eras. They're six parallel workstreams — including one the popular phrase skips entirely. What each track is for, what's shipped, and what's still theoretical.

Ethereum's roadmap is a research agenda published as a diagram, not a schedule. How the six parallel tracks work, how changes actually reach mainnet through forks, and what would reorder the priorities.

EIP-1559 replaced Ethereum's blind fee auction with a protocol-computed base fee that gets burned, plus a small tip to the proposer. How the mechanism works, why the burn exists, and what it didn't fix.

ERC-4337 lets smart contracts act as Ethereum accounts — recovery, passkeys, sponsored gas — without changing the protocol. How UserOperations, bundlers, and paymasters actually work.

An EIP is a design document — the unit of change for Ethereum. How the process actually works, why a 'Final' EIP isn't a deployed one, and who really decides what ships.

A precompile is a function built directly into Ethereum's client software, exposed at a fixed address as if it were a contract. Why they exist, what lives at those addresses, and why adding one takes years.

EVM compatibility is the most common claim in crypto and the least standardized. It spans bytecode, source, and interface levels — and it quietly decays every time Ethereum upgrades. What the claim covers, and where it breaks.

EVM equivalence means conforming to Ethereum's execution specification exactly — bytecode, gas costs, precompiles, edge cases — not just running Solidity. What the claim actually requires, why it's so expensive for ZK-rollups, and where the taxonomy is heading.

Validity proofs prove a state transition is correct before it's accepted; fraud proofs let anyone prove it was wrong afterwards. How the two mechanisms behind ZK and optimistic rollups differ, and where each one's trust assumptions live.

Recursive proving is a zero-knowledge proof that verifies other proofs instead of a raw computation — the mechanism that lets rollups compress thousands of transactions into one cheap-to-check proof.