Ethereum engineering, explained for nowIndependent editorial policy

Build on Ethereum.
Know what the code does.

Practical developer guides for contracts, applications, security, nodes, and chain data—organized so each concept leads to the next.

Start with Solidity →Study security
  • Test before mainnet
  • Explain every assumption
  • Prefer maintained tools
Counter.solLearning contract
contract Counter {
  uint256 public count;

  function increment() external {
    count += 1;
  }
}
ETH / U.S. dollarRetained market reference
$2,458.48Informational ETH/USD reference
24-hour change
Not available
24-hour range
Not available
Open price graph →Convert ETH and USD →
01Deploy safely02Design events03Handle failure
84preserved developer guides
18connected technical topics
1 URLper original article slug
0 tradeseducation and code only

Choose the problem you are solving

A useful learning path starts with the system boundary, not a package name.

Compare the protocol before choosing the tooling

Ethereum and Bitcoin both replicate public state, but they make different choices about execution, consensus, issuance, fees, and application design. A direct comparison helps separate a shared blockchain term from the rule that each network actually enforces.

Compare Bitcoin and Ethereum by consensus, issuance, execution, and control →

Ethereum from execution outward

Understand where code runs, which state it can change, and what users must trust.

The EVM is the center of the developer mental model

A transaction carries signed intent. A node executes it under shared protocol rules. The EVM charges gas for work, exposes temporary memory and persistent storage, and either commits the resulting state or reverts it.

  • Trace a call before optimizing it
  • Separate protocol rules from application rules
  • Treat every external call as a trust boundary
Understand EVM execution →

Recently updated developer guides

Preserved at their original paths and rebuilt into a faster reading experience.

Browse all 84 guides →

Use tutorials as maps, not commands

Ethereum tooling changes quickly. A sound guide should help you identify the invariant underneath the current library call: who signs, what data enters the contract, which account can change state, what happens on failure, and how the result is verified.

Before copying code, check compiler compatibility, package maintenance, network selection, test coverage, and the value at risk. Production systems also need monitoring, incident response, key management, and a clear upgrade policy.

Open the security checklist →