
DeepProve: a cryptographic receipt for every AI inference. now open source. Halo: autonomous coordination engine for the toughest conditions. @LagrangeFndn $LA
Los Angeles
Joined May 2022
- Tweets3.7K
- Following226
- Followers94.4K
- Likes2.5K
Pinned Tweet
3 seconds of thrust.
Then you glide.
Somewhere above you: a drone.
Pursuit is a free browser game. Find it on radar, fly into it, get on the leaderboard. Post your T+ time.
pursuit.lagrange.dev/?utm_so…
A month on, players have thrown nearly 8,000 attacks at the swarm, more than triple the one month mark. 67% of the people who start a mission finish it.
How are players slowing the swarm: 84% jamming, 12% spoofing, 4% shooting. Most missions never shoot down a single drone.
What did you reach for first?
holdtheswarm.lagrange.dev
The full version, including the Eurocrypt paper: xitter.cf/lagrangedev/status/211…
A model gets retrained on a Tuesday and every proof about it has to start over. @chbpap, our chief scientist, walks through the Eurocrypt 2026 paper on proofs that update instead.
Every model launch arrives with a number. Almost none of them arrive with a way for you to produce that number yourself. That seems to be a continued product decision.
A reporter asked an AI agent to find him cheap eggs. It bought them. $31.43, including a $3 priority fee the agent added on its own, for one carton he never told it to buy.
Now work out who pays when it is your card.
lagrange.dev/blog/your-ai-ju…
the fix for more drones isn’t smarter drones. it’s drones that know less about each other. finally, a place where being out of the loop pays off.
No meeting ever got faster when more people joined. Add one person and you add every conversation they are now in: six people make 15, fifty make 1200.
Episode 9: why a swarm scales when every drone knows less.
Episode 8, if you missed it: the highest level of self-driving you can buy still needs your full attention.
xitter.cf/lagrangedev/status/210…
The paper, by Weijie Wang, Charalampos Papamanthou, Shravan Srinivasan and Dimitrios Papadopoulos: eprint.iacr.org/2024/1566
If you're at AUSA this week, here are six questions that will tell you more about any autonomy vendor than the booth demo.
1. Your convoy runs one manned leader and up to ten followers. What do the ten do when the leader is gone?
2. When one vehicle drops out, who picks up its task, and how long does that take?
3. What happens when the column gets split by an obstacle? And when it closes back up?
4. How do you know every vehicle is working from the same picture right now?
5. How does your system tell "destroyed" from "masked by terrain" on a degraded net?
6. What stops something joining the column that shouldn't be there?
Ask them in order. Fifteen minutes of answers beats any demo loop. Send it to whoever is walking the floor.
And ask us the same six: [email protected]
The long version, one failure mode at a time:
lagrange.dev/blog/your-drone…
An empty Waymo was the first vehicle to stop for a school bus with its arms out. Four other cars went past. Then it asked a remote assistant in Michigan whether the bus had its signals on, he said no, and it drove past the arms too.
The word autonomous never told you there was a man in Michigan. It does not tell you who is on the other end of a drone either.
lagrange.dev/blog/your-drone…
LAGRANGE retweeted
ronaldo reportedly won't come to his own farewell without a drone show. a thousand drones about to do a siuu. and for once it'll be a team effort.
Your car says self-driving in the ads and still wants your hands on the wheel. The safety regulator says it out loud: the highest level you can buy needs your full attention.
Episode 8: what autonomous actually means, and the one test that settles it.
Episode 7, if you missed it: a pilot can fly one drone, and that is not a figure of speech. It is the regulation.
xitter.cf/lagrangedev/status/210…
Every trust mechanism in software comes down to one question. Who made the record.
A log is made by the system, afterwards, and it says what the system decided to write. An audit is made by a person, later, out of those logs. A proof is made by the computation, while it runs.
Nobody writes it. Nobody can edit it. That is the whole difference.
The second one, from last week: a signed log will tell you the right model ran, and so will a signed log from a system that quietly ran a cheaper one.
xitter.cf/lagrangedev/status/210…
A signed log will tell you the right model ran. So will a signed log from a system that quietly ran a cheaper one and typed the expensive name into the file.
A proof cannot do that. Change the model, change the input, change one number in the output, and it stops verifying. There is no version of it that is wrong and still passes.
A claim can be honest and wrong. A proof cannot be wrong.



