Ethereum for Resource Limited Devices
summary
Roadmap reports a working cross-compiled C++ client built with Docker and bash scripts, first successful cross-built binary in November and an ongoing grant-funded C++ client implementation. Resource numbers: an LES light client yields a ~25MB binary, ~50MB chain data, ~12% CPU and 162MB RAM high-watermark with nine minutes behind sync on Raspberry Pi 3. A Raspberry Pi Model A (700MHz, 256MB) runs a full client but barely keeps pace. Whisper development restarts and Raiden is noted as applicable.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:47Speaker background
- 1:48Defining constraints
- 2:44Examples of devices
- 3:28Why use Ethereum
- 4:55Historical context
- 6:17Modern hardware specs
- 7:25Low-cost computing
- 8:24IoT market growth
- 9:12Project Adept
- 9:47Technological progression
- 10:15Ethereum integration
- 11:06Why C++ matters
- 11:45Performance factors
- 13:31Project status and specs
- 17:09Future outlook
related talks
35mLight Clients Aren't Dead
43mScaling & Interoperability Panel
37mInteroperability via the Rainbow Bridge
25mExpanding the Web 3.0 to Low-level Devices: Scaling Access
40mLeveraging Octez
17mIBC Gets Ready to Land on Ethereum
27mEasy as a pi: EdgeX on Raspberry Pi for Automotive IoT
34mAn Introduction to EdgeX Foundry