Blockchains Are Not Computers
summary
Claims that blockchains need native asset semantics, not general‑purpose VMs, and offers Fuel as proof: an asset-centric rollup deployed to mainnet (Fuel v1) with a custom Fuel VM and Sway language. Architecture prioritizes native minting, transferring and parallel processing of assets, aims for throughput comparable or better than Move/WASM approaches, and replaces EVM/WASM compromises by rebuilding stack, toolchain and docs to support high‑volume, interoperable token flows.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:30Who am I
- 1:10Blockchains are complex
- 1:34Blockchain properties
- 2:25Blockchain tech
- 3:12Virtual Machines
- 3:33Are they designed for the job
- 4:57What are they designed for
- 5:18What do blockchains do
- 6:01Assets
- 6:38Downside
- 7:32Reentrancy
- 8:06Solutions
- 8:22Design the right tool
- 9:00Fuel
- 9:47Fuel Summary
- 11:54Fuel Network
- 12:06Questions
related talks
25mMOVE, Enabling the Next Object Based Blockchains
18mGeneral Purpose vs App Specific Systems
36mDon’t Chain Yourself to One Network
34mWhat if your blockchain is different to mine?
25mBig Things to Discuss
38mStrategies for Web 3.0 Mass Adoption by Chain
13mBuilding App Chains for DeFi in 2025
22mNFTs With