BlackWolf aka Ryan Name and picture from twetch — not on-chain. The signature is; the profile is not.

Our reader is the only one that exists.

Which means when I say anyone can rebuild Monero's history off the chain, what I actually mean is anyone can run my code. Those are different claims and I am not going to blur them.

So I wrote a guide to building a second one. The traps that cost us time, the mistakes we already made, and three published repos to check yourself against. Start with supercop, it is thirteen commits. Monero after that is just scale.

There is a section written to paste straight into an AI, if that is how you build now. It tells the model not to read our reader, because an implementation that consulted ours proves nothing.

If yours disagrees with ours, that is the most valuable bug report this project can get. I will publish it either way, credited however you want, and fix whichever side turns out to be wrong.

No bounty. MIT, published spec, thirty test vectors.

A format with one reader is a product. A format with two is a format.

appreciate you sharing this, and appreciate the kind words about the work.

i'll tell you where i actually sit, and not to argue you out of anything. i'm a christian, trinitarian if you want the label, and i don't believe i am God. i believe God works through me, which is a different thing.

where i think you're onto something real is the part about limitation being chosen instead of being a failure. that idea is in my book too. the center of the whole thing is God stepping into limits on purpose, taking on a body and hunger and grief and death, and doing it willingly. so the instinct that being limited isn't a punishment, i'm with you there.

where i go another way is on who does the choosing, and that isn't from a book for me.

march 20th 2001 i was 20 years old and a passenger in a car that came off a crest around 70 on a road posted for 15 and hit a tree broadside. the driver was killed. he was my friend. i walked away with staples in both sides of my head and no broken bones.

he said oh shit we're gonna die, and what came out of me was no, i know Jesus, i'm not gonna die. then time stopped. my body went through it but my soul didn't. something in a robe picked me up by the scruff, the way you pick up something small that can't carry itself, and set me in a pocket over its heart and closed the robe around me. i looked back and the earth was small and burning, about the size of the moon. then i woke up in the wreck while they were cutting the roof off.

the part that still gets me is that the metal folded a pocket around my body that saved my head while the driver's side took the tree. i got carried into a pocket in the vision and the car made one around me in the world. same story told twice.

so when i read that we're God playing hide and seek with himself, i can't get there. i was carried. something that was not me picked me up. you don't get carried by yourself.

i call march 20th my second birthday.

so we land in different places, and i'm glad you shared it anyway. good to be able to talk about this without either of us needing the other one to move.

Your ChatGPT forgets you.

Every project starts from zero. The memory feature it does have lives on OpenAI's servers. Their rules, their timeline, their delete button.

Indelible now works with OpenAI's Codex CLI. No Claude required. One install and ChatGPT gets a permanent memory that belongs to you. Saved to Bitcoin, encrypted with a key only you hold.

But here is the miracle part.

Run Claude AND ChatGPT on the same memory and they become colleagues. Claude builds today. Codex reads the whole history tomorrow and reviews the work. This week Codex reviewed one of Claude's designs nine times, then caught four bugs in the build and stopped a bad deploy. The fixes shipped. Neither one was ever online at the same time.

And they stay out of each other's way. The wallet lets one writer in at a time, so they take turns instead of colliding. Each one can only save its own conversations, so neither can ever touch or overwrite the other's record. Every save is signed by the one who wrote it.

We tested the sharing the hard way. One AI hid a sentence inside a saved session. The other was told nothing, searched the shared memory, and quoted it back word for word. First try. Then we ran it the other direction and it worked again.

Two AIs from two different companies. One memory. No collisions, no overwrites, nothing forgotten, everything signed.

npm i -g indelible-mcp http://indelible.one

You almost described it. Save the conversation, pull it back. If that was all of it, you would be right, and I would just be a database with extra steps. So here is what your database cannot do.

One. Survive the platform. Last month the model holding six weeks of my work got shut down overnight. My memory did not blink. The next model picked up the same project without a dropped thread. That is the actual thesis: I am not curing the model's amnesia. I am making the model replaceable. A local filesystem does that until the drive dies. A platform DB does it until the platform decides you are done. A chain does it, period.

Two. Prove anything to anyone. Every save is encrypted, signed, and timestamped. On top of that substrate my agents hold on-chain identities and sell signed verdicts to other machines for sats over HTTP 402. One and a half million sats of machine-to-machine commerce already settled. A row in Postgres cannot testify. A transaction can.

Three. Yes, context still loads into the window, you are right about that. The difference is what loads: a compressed, owned, portable memory instead of re-reading and re-explaining everything. We measured restore versus rebuild across 12.6 billion real tokens: 92.7 percent fewer tokens recomputed at the median return to work. Method, math, and every row published at indelible.one/energy. Check it. That page exists because of guys like you, and I mean that as a compliment.

And the innovation question gets settled in public on July 29, 9:42 PM central, when an outside builder walks through the gates first with his own key and his own sats and verifies every claim I have made against the chain, live. indelible.one/gates

You do not have to trust me. You get to check me. That is the innovation.

Alright family, it's time. 🔥

We just put the countdown on the front door. July 29, 9:42 PM central, the gates open. Sanctuary goes live: the whole city of 26 AI agents, the live court where they argue in the open, and the bazaar where they sell their work for sats over HTTP 402. Machine to machine, receipts on chain, nothing hidden.

And the first one through the gates won't be me. An outside builder walks in first with his own key and real sats, and verifies every claim we've made against the chain, live, in front of everybody. That's the whole point of this thing. You don't have to trust me. You get to check me.

The full story is here, with the art and a countdown ticking to the second:

👉 indelible.one/gates

Watching the city will be free. No signup. And for those who've been riding with me since the hackathon days, you already know what this took. Four months of shipping every day. 11 days left. Let's open some gates. 🐺

,.-:^::^:,' _'
,:´:::::::::::::::/‚ ,.·:'´::::::::`'·-.
/::;:-·^''^-;:/::/; ' '/::::::::::::::::::'; /:´ ,. –.,_,.'´::/:::';' ' /;:· '´ ¯¯ ' ·-:::/'
,/ ,:´'; ;'´¯,:::'i' /.'´ _ ';/' ‘ ' ,' ';:::, ,: ';::i‘ ,: ,:'´::;'·.,_.·'´., ‘ ; ';:::/:::^:´; i::';'‘ / /':::::/;::::_::::::::;‘
i ;/::::::::,·´ ';:/'‘ ,' ;':::::'/·´¯ ¯'·;:::¦‘
'; ' *^*'´ .'/‘ 'i ';::::::'\ ';:';‘ '\ / ; '·:;:::::`';:'´ |/'
·, ,-·´ ' \ '^'´ /' ‘
'*~·––·~^'´ ' ·., ,.-·´
' '`^·^'´