Ethereum from a Full Node’s Perspective
summary
Infura describes running many Ethereum clients (geth, parity, cpp-ethereum, Trinity, Pantheon) and reports sync times like warp sync ≈ 90 minutes vs older fast-sync of minutes, while archive-state complaints claim the state tree >1 TB but blockchain size is smaller. Node count sits around 14–15k nodes; pending tx pool often hits ~80k. Work focuses on state-storage optimizations (Turbo-Geth), off-chain indexing (ETL, The Graph / EthQL), light-client server capacity and p2p discovery health metrics.
AI-written summary · about
chapters (10)
- 0:00Ethereum full nodes intro
- 2:26Centralized vs P2P data access
- 3:52User connections to Ethereum
- 7:06Challenges running nodes
- 10:59Optimizing state tree performance
- 13:48Light clients and network capacity
- 15:37Off-chain indexing limits
- 18:02Ethereum P2P network health
- 22:11User expectations in P2P
- 24:18Gas estimation issues








