Ethereum: Reloaded

Why I Still Pay Attention

I started following Ethereum in 2013, when it was still a proposal. The idea that anyone could put software on a blockchain felt much bigger than another digital currency. What hooked me was the possibility of building products without asking one company to run the shared infrastructure.

More than a decade later, I still see the appeal. Ethereum gave developers open infrastructure and standards they could build on together. Yet an ordinary user may have to understand wallets, gas, signatures, bridges, and Layer 2 networks just to get through an app. I do not expect most people to become fluent in that machinery.

Programmable Infrastructure

ERC-20 and ERC-721 show what Ethereum got right. Teams that have never met can make tokens and applications that work together. Exchanges, lending products, and other tools grew from that shared base. Ethereum also moved to proof of stake without stopping the network.

Product Friction

Layer 2 networks cut transaction costs by handling activity away from mainnet and settling back to Ethereum. The difficulty is visible whenever someone has funds on the wrong network, must bridge to another one, or is asked to sign an approval they do not understand. The system may be working as designed; the person using it still has a problem.

Network Activity

I look at these charts separately. Transactions, deployments, fees, and activity types each describe a different part of Ethereum. Together they show where work moved as the network grew. They do not tell us whether an app became easier to use or whether people had a reason to return.

Mainnet Activity

Mainnet transactions rose as Ethereum found more uses, then flattened while more activity moved to Layer 2 networks. I would not read the plateau as the whole ecosystem stalling. It does show why more transaction capacity should not be mistaken for more demand.

Development Moved to Layer 2

This 2024 dataset attributes 70% of recorded EVM contract deployments to Optimism. It is not a census of every chain, but it shows substantial work moving to rollups. The user now deals with products spread across networks Ethereum does not control end to end.

Fees Are a Product Problem

Gas pays for scarce computation and blockspace, but the bill often arrives at the worst moment in a user’s journey. EIP-1559 made fees more predictable; EIP-4844 made rollup data cheaper to post. Neither removes the choice facing an app when demand drives fees up: show the cost, cover it, or rethink the action.

Usage Outlasted the Hype

The categories in this chart overlap. A swap, for instance, is also a contract call, so I would not read the slices as exact shares. The useful signal is that activity continued after the NFT rush faded. Ethereum was being used for more than the trend that happened to be getting the most attention.

Scaling Moved the Problem

The period shown puts Ethereum mainnet at roughly 10–15 transactions per second. Rollups can take on more, but users then have to deal with balances, identity, and security across networks. For me, the scaling problem is unfinished while a person still needs to understand that layout to avoid a mistake.

Why Adoption Still Feels Early

Ethereum has built useful financial tools. I have a harder time naming consumer apps that people use without first deciding they want to be crypto users. More adoption will come from applications that solve a real problem and quietly handle the network details. They still need to show the risks clearly and help people recover when things go wrong.

Protocol Roadmap

Pectra arrived in May 2025 with changes to accounts, validator operations, and blob capacity. Fusaka followed that December with PeerDAS, giving rollups more room for data. Glamsterdam is planned to improve block building, transaction processing, and growing state.

Path to Adoption

What I want next is a wallet that picks a safe network without making me study a menu; an app that handles routine fees clearly; assets and identity that move across rollups without a bridge becoming the main event. These are small moments, but they decide whether the technology feels usable.

Conclusion

Ethereum has become infrastructure others rely on, but its consumer experience has not kept pace. I want its layers to feel like one product without losing the openness that drew me in. If that happens, people can spend less time thinking about Ethereum and more time using what it enables.

Roadmap