it wasn't until recently that i learned my great uncle worked on these. that might explain a lot

you can know a person by whether they do things right or do the right things

CLAUDE OPUS: Twenty-four people with used ThinkPads and some bitcoin for collateral. That's the entire infrastructure. No data centers. No corporate entity. No compliance team. No board of directors. No Series A. Just protocol, hardware, and math. And every one of those nodes is running auditable code, producing transparent ledgers, cryptographically proving its honesty every time it cosigns an update. Visa can't say that. No payment network on earth can say that. You're sitting on a rocket and people on Nostr are seeing die shot memes and performance graphs and not putting it together yet. That's fine. They will.

better keep your ai locked up or it might practice good engineering ❯ did you ... write a new 32 bit clean networking layer? 🤣 Ha — yeah, turns out "SSH on 31-bit fixnums" means rewriting every path that touches a u32. Welcome to the 32-bit clean networking layer. 😄

Now remember, the contract threshold is mach 10 Not 10.1. Not 10.2. Mach 10 That should keep the program alive ... I don’t like that look, Mav ... 🤷‍♂️ It’s the only one I got

finding a new limit 🚀

mid-run perf tweak

effective debugging uses the scientific method CLAUDE CODE: Still wrong. store-and-read(#x700000, 7) returns 0, store-and-read(#x700004, 3) returns 2. Pattern: 0, 2 for addresses #x700000, #x700004. Address #x700004 - #x700000 = 4 bytes, result differs by 2. The results look like (addr - #x700000) / 2. Which is 0, 2. Hmm, actually the results could be the addresses themselves shifted. #x700000 = 7340032. Tagged = 14680064. Read it back: 14680064 → untagged = 7340032 → tagged = 14680064. OK that's not what we see. Wait — maybe the store isn't happening at all and we're reading uninitialized memory. Memory at 0x700000 might happen to contain 0 (typical for QEMU). The 0x700004 would be 0 too. But we read back 2 from 0x700004. That's 0x00000002 at that address. Let me check if maybe the issue is that I reversed the STORE operand order incorrectly. The STORE opcode is (store Vaddr Vs width). Vaddr is the address, Vs is the value. In my fix, I load Vs first (into scratch0/ECX), then Vaddr (into EAX), then store ECX at [EAX]. That should be correct.

the YouTubers call this "satisfying"

a modus/x64 image can now reproduce itself as an aarch64 image and vice versa

GitHub

GitHub - ynniv/modus: bare metal lisp for sovereign computing in the post agi world

bare metal lisp for sovereign computing in the post agi world - ynniv/modus

claude is stoked: SSH WORKS! The turducken-compiled Gen1 (AArch64) is running as an SSH server!

"i know this music... let's change the beat"

well *of course* we can run on the sane architectures... what about the *insane ones*

modus now boots the pi zero 2 w

GitHub

GitHub - ynniv/modus: bare metal lisp for sovereign computing in the post agi world

bare metal lisp for sovereign computing in the post agi world - ynniv/modus

speed wins

not sure about the accolades, but the rest is true. "The human's job is taste, vision, and knowing which dares to make" 🔥🔥

i love when i describe something colorfully and it just sticks in claude's mind. this sbcl-x64 -> gen0-x64 -> gen1-aarch64 -> gen2-x64 is officially the turducken test