Software engineering leader For fun: Ethereum Historian, https://xitter.cf/t.co/vlxDYhca9w Ex @strato_net, @ETCCooperative, @ethereumfndn, @EA

Vancouver, British Columbia
Joined April 2013
Early Days of Ethereum is teaching me something new every day, even though I am more than a decade into my own journey. I'll start dropping each of those @ethereum learnings onto a forever-tweet-thread here as they come, as well as on the website. 🧵 earlydaysofeth.org
25
18
7
164
150,986
Bob Summerwill retweeted
Omarchy Mobile update ⚡📱 The camera app was a big step. Since then, the project has gone from one phone to a family of Pixels, thanks to the community 🙌 Device support - Pixel Fold (felix): first light! It boots our mainline kernel to a console on the cover screen, with UFS storage enabled behind our storage guard. Huge thanks to @boozedog. - Pixel 6 / 6 Pro (oriole, raven): the build tools now build and flash Tensor G1 phones. The Pixel 6 has its device descriptor from a real retail phone, and Mesa now recognizes the Mali-G78 GPU. Thanks to @robotosaith and @bilacc, with the GPU and Pixel 6 Pro kernel work in review. - Pixel 4 (flame): our first Snapdragon phone, now with a safe, read-only first-light probe that runs from RAM. Thanks to @wirelessjoe. - One shared boot setup now serves every phone, so adding a new device mostly means writing its config file. Big wins on the Pixel 7 Pro - 🔋 Charging is on by default now, protected by a battery temperature guard. And when you plug in, the battery actually says "Charging." - 👆 Fingerprint unlock survives sleep. We found and fixed a bug where sleep left the sensor stuck. - 🐧 Our first Linux kernel patch went upstream. The battery fix was sent to the Linux kernel mailing list and got a Reviewed-by within hours. - 🤖 The AI Agent shortcut has been added, and first-run setup now asks which AI agents you want. Nothing proprietary is preinstalled, and you choose what goes on your phone. Up next: we're testing Wi-Fi through repeated sleep/wake cycles right now, which is the next step toward the phone sleeping on its own when the screen is off for real battery life. Got a Pixel? Device ports are open and contributors are welcome. Thank you to everyone who's sent a PR 🧡 github.com/derekross/omarchy…
15
13
1
175
4,954
Bob Summerwill retweeted
Omandroid has a new name: Omarchy Mobile 📱 It was never Android. It's native Omarchy (Arch Linux ARM, Hyprland, Omarchy's own packages) on a mainline Linux kernel, right on a Pixel 7 Pro. No Android underneath. New repos (old links redirect): github.com/derekross/omarchy… github.com/derekross/linux-o… Hardware: display at 120 Hz, GPU, touch, Wi-Fi, Bluetooth audio, battery, haptics, torch, sensors and auto-rotate, GPS, NFC (read/write tags) and fingerprint unlock (opt-in) all work. Speakers work but are still quiet. Ultrawide camera works; main and front are in progress. The modem now boots and talks to the phone; calls, SMS and data need a SIM, that's next. Sleep is in progress. The last two days in software: • swipeable home screens with ~50 built-in widgets, from @simonschubert's Omalauncher • "Create with AI": describe a widget, Omarchy's default agent builds it • editable quick settings • one app per screen • mirror the phone's screen to your laptop over USB And an installer! I'm super happy to annonce this. It can all be done with a few commands. GUI/website later. Build the root image on your laptop, then tools/install-phone asks for your user name, password and Wi-Fi, checks the phone, and writes only slot B and userdata. Stock Android stays on slot A as your way back. First boot sets everything up, and tools/phone-provision pulls the phone-specific firmware from your own Pixel factory image (no Google files redistributed). The first clean install with it is happening on my phone as I write this. Steps are in the README. Fair warning: this is EXPERIMENTAL! Unlocking the bootloader wipes the phone, expect rough edges, Pixel 7 Pro only for now. Pixel 6 and 8a ports are starting via contributors. Addtional contributors welcome 🤙
46
63
14
578
26,888
Bob Summerwill retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
921
7,703
1,443
60,231
3,127,065
Bob Summerwill retweeted
Linux on the M6 Mac Mini, Day 5 - success! Omarchy is installed on the Mac Mini's hard drive. It boots, it runs. Still bringing up accessories, including Ethernet and GPU, so my work's not done, but 5 days from the macOS About screen to the Omarchy About screen isn't bad!
111
52
17
1,219
88,476
I never use Windows myself but was just setting up a fresh ThinkPad X1 and here's what the installer says, with no option to skip or any real info. Or Retry button.
2
2
423
Oh wonderful. Did the "use my phone from my PC" prior step vs skip. Back/here, but now without even a back button!
64
Bob Summerwill retweeted
This is a great visualization. Look at the shape: a ring of well-connected nodes in the middle, with work fanning out and aggregating through layers until the core only has to handle a single result. That’s a mandala. I’ve spent years on this question. In 2018 I wrote a piece that was eventually reposted on CoinGeek, “Bitcoin: A (decentralized) complex social network,” that started from the claim that Bitcoin’s miners form “a small-world near-complete network.” I wanted to know if it held up, so I turned to network theory, specifically Fernando Vega-Redondo’s Complex Social Networks. What I found changed how I think about decentralization. In network analysis, “the edges, or links, are more important than the number of nodes in a network.” What gives a network reach and resilience is how its nodes are connected, not how many there are. Now apply that to Bitcoin. A miner only gets paid if the rest of the network builds on their block, so as a miner, you have a clear incentive to be highly-connected to the other miners in the network. Every miner is pushed toward connecting directly to every other miner. Merchants are pushed the same way: to stop double-spends, they broadcast to the best-connected nodes. Nobody designs the topology. The incentives produce it. The result is a core that’s close to fully connected, where any miner is about one hop from any other, with everyone else arranged in layers around it. That’s a small-world network, and it’s what makes the design so innovative. Raising capacity doesn’t make the core more fragile, because the economics keep it tightly connected. Every other layer only has to verify what it touches. So Ethereum’s new thesis, “scalability increases with decentralization,” is right, provided you measure decentralization by connectivity rather than node count. That’s the insight Bitcoin’s design was built on. None of this is new. Satoshi wrote it down, again and again, before most of today’s crypto industry existed. November 2008, before Bitcoin had even launched: “Visa processed 37 billion transactions in FY2008, or an average of 100 million transactions per day. That many transactions would take 100GB of bandwidth.” Running nodes, he said, “would be left more and more to specialists with server farms of specialized hardware.” 2009, in an email to Martti Malmi: “The existing Visa credit card network processes about 15 million Internet purchases per day worldwide. Bitcoin can already scale much larger than that with existing hardware for a fraction of the cost. It never really hits a scale ceiling.” July 2010, on BitcoinTalk: “The current system where every user is a network node is not the intended configuration for large scale. That would be like every Usenet user runs their own NNTP server. The design supports letting users just be users. The more burden it is to run a node, the fewer nodes there will be. Those few nodes will be big server farms.” A well-connected core of specialists, with users at the edge who simply use it. That’s the mandala, described before the first block was mined. Here’s where things stand 17 years later: - Visa: about 705 million transactions a day (257.5B in FY2025), or roughly 8,000 per second on average. - Ethereum L1: a record of 25.9 transactions per second in Q2 2026, about 2.2 million a day. Ethereum’s base layer still hasn’t reached the 15 million daily online purchases Satoshi used as his benchmark in 2009. Visa as a whole handles about 300 times more. Meanwhile, in 2018 Vitalik called 128MB blocks “an insanely stupid idea.” Since then, BSV has mined a block of nearly 4GB, and Teranode averaged over 1 million transactions per second across a two-week test. That’s more than 100 times Visa’s average. Think about how much time, money and talent the industry spent trying to solve a problem whose answer was already in the original design. Much of that effort went into avoiding the plan rather than building it. But we’re not here to dunk. Seeing the brightest people in crypto arrive back at the same shape is a good sign. Good engineering converges. BSV has spent years running this architecture in production: Teranode at the core, overlays in the middle, SPV wallets at the edge. We’ve already paid for the hard lessons about what breaks at scale, and we're happy to compare notes. The answer was there in 2009. All any of us had to do was build it. 🔗 My 2020 deep dive: coingeek.com/bitcoin-a-decen…
I made a visualization of EIP-8288 aka "recursive mempool aggregation," my new favorite EIP of all time because it perfectly encapsulates the thesis of the "cryptographic world computer" -- a system whose scalability *increases*, not decreases, with the level of decentralization. In a previous tweet I explained how EIP-8288 achieved this seemingly impossible feat, but one gif is worth a thousand words. Essentially, EIP-8288 leverages Ethereum's decentralized mempool as a parallel ZK proving cluster. Clients send signatures and proofs to the mempool, which over multiple rounds progressively aggregate them into fewer and fewer proofs, until the block builder finally aggregates them into one SINGLE proof. This design accomplishes five things at once: - The more nodes we add to the decentralized mempool, the more signatures/proofs Ethereum can process as a whole. This is obvious if you look at the animation and imagine more nodes in the mempool ring, which would "fan out" to more signatures/proofs. - By aggregating over multiple rounds (aka "recursive aggregation"), the bandwidth consumed by proofs remains constant for each node even as the network processes more proofs. As a result, the network stays decentralized even as capacity increases. - By aggregating proofs before one final aggregation by the builder, as opposed to requiring the builder to aggregate everything, the network can process more proofs without increasing hardware requirements for the builder. - By aggregating everything to a single block-level proof, validators can verify thousands of signatures/proofs by checking just one aggregated proof. Hardware requirements for validators can therefore stay low, keeping the network decentralized. - By aggregating not just native signatures but also STARKs, Ethereum can support any signature scheme by wrapping them in STARKs. So once again, this is how Ethereum will: - scale to process tens of thousands of PQ and private transactions per second - charge a tiny amount of gas to validate each txn, even though the original signature/proof may be huge (up to hundreds of KBs in size) - all while decentralizing even MORE. You are not bullish enough.
5
17
6
74
2,542
Bob Summerwill retweeted
so is this useful at all? not really. but we can now confirm with certainty that the executable people downloaded matches satoshi's published source code exactly 😄 some other archeological fun facts: - satoshi used windows xp with mingw - he upgraded binutils halfway through the project - he shipped a debug build, but turned on max optimization for one file: the hashing used for mining - the exe everyone calls v0.1.0 is actually v0.1.1 and was compiled two days after satoshi announced v0.1. the original launch-day binary seems to be lost github.com/t4t5/bitcoin-0.1-…
36
45
9
670
43,262
Bob Summerwill retweeted
i rebuilt satoshi's 2009 bitcoin.exe byte for byte! afaik nobody has been able to perfectly recreate the executable published in 2009 from source, because we didn't know the exact build environment that was used. using opus 5.5, i reverse-engineered satoshi's build machine from the binary. it now outputs an exe with the exact same sha256 as the 2009 release!
100
129
40
2,201
292,895
Bob Summerwill retweeted
DeepSeek V4.1 Flash updated to 1017 in OpenCode Go and Free No changes needed on your end
468
673
377
12,742
666,263
three stories about times that i FUMBLED THE BAG (maybe you can relate) 1. Steve Jobs used my song to open a press conference. 2. I made a jingle for AirBnB when they were pre-funding in 2008. 3. I made (and lost) $2.4 million selling my songs as NFTs.
30
29
6
159
7,587
Bob Summerwill retweeted
for a long time it felt like the world was fully optimized against you you go to buy something, you get a bunch of ads and upsells and micro optimizations to get you to spend more you go to consume some specific content and the algo puts in things that are hard to ignore and designed to get you to spend more time agents are the first time i've felt like maybe things can go in a different direction. send your robot into that mess and it can ignore it all and do your task i'm not naive, this is going to be an insane battle with entrenched interests doing their best to fight it but there's a small chance that in the end we can finally be free of this (until the next new problem)
127
70
21
1,707
72,700
Bob Summerwill retweeted
deGoogle track will return at Cypherpunk Congress. @BobSummerwill will update his FOSS story for all of you. Crafted by years of anti-Big Tech personal journey. Listen to people. Understand why self-sovereign way is hard. But try it one app at a time.
Ethereum Cypherpunk Congress highlights: @BobSummerwill showed his ongoing escape. Expect free & open-source software, degoogling, practical software stack & @GrapheneOS watch: youtube.com/watch?v=AOri8sxx… event: congress.web3privacy.info
3
1
24
1,099
Bob Summerwill retweeted
"[Linux] is *NOT* some kind of "social warrior" project, never has been, and never will be." — Linus lore.kernel.org/linux-media/…
115
289
45
5,002
376,653
Bob Summerwill retweeted
People's choice! Thousands want to explore privacy, decentralisation of power & digital rights 🇮🇳 Cypherpunk Congress is a festival: ☑️ 100 speakers from @kurtopsahl to @VitalikButerin ☑️ 80 organisations from @brave to @SFLCin ☑️ visitors from 50 countries 🌏 Celebrate it congress.web3privacy.info
4
5
2
24
1,846
Bob Summerwill retweeted
Chinese bride gifts her partner a flagship GPU at wedding — he breaks down in tears She handed him an ASUS ROG Astral RTX 5090 that costs around $12,000
1,789
6,770
2,743
88,516
12,027,437
Incredible
Turns out the future does have flying cars
4
695
Bob Summerwill retweeted
Turns out the future does have flying cars
48,101
100,229
32,688
834,387
78,572,384
Bitcoin isn’t one chain. It’s the idea. True peer-to-peer electronic cash that is fungible, scales, and does everything. Doesn’t matter who delivers it. Just that the promise gets fulfilled. @Vladcostea @BobSummerwill
2
8
20
757