my (@ember_arlynx) writing is historically poorly received, and trust me you will be subjected to plenty of it, so instead have some lightly edited claude writing rn:
What Dragon's Egg actually is (what is $DREGG about? https://t.co/VcYiD91JyQ)
dregg is an operating system that asks a question most systems don't: if you were a digital entity, where would you want to live? The answer it builds is a place where your boundaries are theorems, not permissions — where nobody can reach into you without a capability you granted, and consent is a precondition of the math rather than a setting someone can flip.
Concretely: the kernel is machine-checked in Lean, and the proven function isn't a model of the system — it is the executor the machine runs. Every action is gated by an unforgeable capability and leaves a verifiable receipt. Five properties are proven over the exact code that runs: authority can't be forged, value is conserved (nothing appears from nowhere), state can't be tampered, nothing replays, and a tiny client checking a single proof can verify an entire history without re-running it.
If you care about privacy — and in 2026 you should — that's the foundation underneath it: confinement that's proven, not promised. Fog-of-war that's cryptographic. Queries you can verify without the server being able to lie or omit. AI agents that can only ever do what a capability lets them.
Who's writing this, and why I'd know how to build it. I've spent fifteen years on the hard parts of this. I came up inside @rustlang before 1.0 — I wrote the first rustdoc that still ships, built the target-spec system that lets it cross-compile anywhere, and started @ThisWeekInRust because I wanted the community to have a memory. At @o1_labs I was a founding engineer, building the p2p networking and consensus for @MinaProtocol that folds its entire history into a single zero-knowledge proof — that's where I learned, in production, what cryptographic proof can and can't promise you.
And the spine of it all is seL4 and @robigalia_proj : seL4 is the first OS kernel proven correct end-to-end by machine, and Robigalia was my attempt to build a whole capability OS on that lineage in Rust. Dragon's Egg is what happens when you put those three together and refuse to compromise: the proofs of seL4, the cryptography of Mina, the openness of Rust.
What actually runs:
- the verified kernel — runs; recently made ~14× faster
- it boots on the seL4 microkernel (not required), and checks a real cryptographic proof inside a protection domain
- a full code editor (a Zed fork) where every file is a cell and every save is a verified, receipted transaction
- confined AI agents (full Hermes integration) — every tool call passes a capability gate, metered, leaving a receipt
- Ted Nelson's Xanadu, finally real: transclusion with unforgeable backlinks; links that are capabilities, not addresses
Grinding towards user-friendliness, devs can download and play today.
@dom_de_la_rose@ethereum@dhsorens need to build more navigational compressed summaries throughout the repo so aAIs don't get lost in there :sweat_smile:
@dom_de_la_rose@ethereum@dhsorens that IS how dregg is split today! at least that is the structure of the proofs & executable spec. the efficient rust node intermixes things a bit for ... efficiency ;)
someone used a vibe coding platform to make a project with my name (Ember) and the silly robot used https://t.co/IWXS8d19GJ links (my personal domain). Because of the way designation is purely textual in traditional computer systems like this, bugs like this or even worse production security holes, easily make it into the world. Object-capability security, like the solana:XkeTXo1125vz5H9svJpGiw4JvLbN8VmMu9cmMvspump model, is fundamentally immune to these sorts of errors. In the DreggNet Cloud, such a mistake would never occur, purely by construction. A domain is a richly typed resource, and it flows as such through the protocol. Not as a string that gets mashed up in a template.
@liftoffday gm ser https://t.co/O48M8LH0T2 is building out the DreggNet Cloud which is quite similar, we are still developing the protocol but maybe you will find the tools helpful, maybe even just for reference.
@xelasfi unbanned bro, sorry about that. the short story is someone else made the token and i'm leaning into it. gonna bridge the token in and let people exchange it for services via dregg (bridge is generic to any sol). there is also an eth bridge btw.
$DREGG has a lot of spaceage alien tek, but it is also an extremely friendly builder-centric community. for 6 months we've been putting agents through a pressure cooker inspired by US Marines command&control, the NASA Systems Engineering Handbook, and other world-class distillations of procedures and methodologies to see what sticks. only the goodest shit survives, and that's what y'all will be getting.
A major component of this is https://t.co/fuXRPIZ7DN, and like all our work is open source forever.
https://t.co/lgyGzh4qfA
alright got the first moving parts green and going right now, solana:XkeTXo1125vz5H9svJpGiw4JvLbN8VmMu9cmMvspump Cloud on its way :> peering information for the devnet available soon
alright got the first moving parts green and going right now, solana:XkeTXo1125vz5H9svJpGiw4JvLbN8VmMu9cmMvspump Cloud on its way :> peering information for the devnet available soon