Will Binns
@wbnns
Founder @mruspace • ran bitcoin.org, led teams @coinbase • editor of Mastering Bitcoin & Mastering Ethereum • software that outlives its makers
Knowing exactly where you lose is how you know where you win
Spare processors kept switched off beat us if they barely age while they wait. If they do age, we do up to 60% more work
0
0
5
We spend a lot of time on what a machine should do when its parts fail
This is the harder question -- what it should do when its own update is wrong, and nobody is coming
Yesterday's FAA ground stop across all US airports may have started with an update. The cause isn't confirmed, but two of the three accounts of the outage so far point to one.
Backups don't help when the same bad update reaches every copy at once. In Mru Field a new version comes in one copy at a time, and the old ver
1
1
4
The best upgrade respects the work that's already there
Mru Field works with the code you trust, not instead of it
0
1
3
Yesterday's nationwide FAA ground stop was the right call... when planes can wait safely on the ground, stopping is the safe choice
But hard to reach systems -- machines at sea, on the ice or in orbit -- don't get that option
We make software that keeps them working through a failure instead of stopping for it
0
1
8
Most upgrades start with new hardware
This one fits on what's already in the box, from the seafloor to orbit, and leaves 99% of the processor for the real work
0
0
2
A buoy on a fading battery faces the same choice: what to keep running, and in what order
Getting that right is how a machine stays useful to the very end, on Earth or past Pluto
0
0
2
We tried hard to make our own idea look bad
Worst case we found: 11% more useful work. Best case: 68%. The simulator is open, so anyone can try their own numbers
Still early. The goal is software that keeps machines running for millennia
A simulator is only as good as its guesses. So we tested ours against the numbers we're least sure of: how fast parts wear out, how often radiation flips a bit, how often failures come together.
Across all of them, our approach did 1.11 to 1.68 times the useful work of standard triple voting, with no repairs.

0
1
6
A sensor on the seafloor lives the same way between its once-a-year visits
Mru helps it know what to do until the ship comes back
0
0
3
Tests tell you it worked the times you tried. Proofs tell you it works the times you didn't think to try
For a machine nobody can reach, we want both
1
0
1
A volcano station matters most on the day it's hardest to reach
We build software that helps it check its own work, so the people relying on it know which numbers to act on
0
0
1
Some of the best engineering on Earth is a small team in California keeping a 49-year-old probe working
We want every machine we send out to carry a little of that team with it
Voyager still has a team on Earth, 49 years after launch. When something breaks, they diagnose it and send a fix.
Our simulator showed something hopeful: a team doesn't need to answer fast. A fix in one day or in six months kept the mission just as healthy. What counts is that someone is there.
We build software that
1
0
4
We build software for machines that will outlive everyone who built them
So we write it like a letter to someone we'll never meet: plain, open, and easy to follow
0
1
7
Voyager 1, the farthest thing humans have ever built, is about to reach one light-day from Earth. Sirius is over 3,000 light-days away
Fly there yourself and you'll see why we build for centuries
0
1
9
Early days of a thousand-year job -- say exactly what your software will do, then do it in outer space
3/3 so far
0
0
1
