{
  "txid": "347f306aec82ffdd949288df0cf290ee2d76dbdcec8fae31af402d672503207a",
  "block_height": 954245,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "Anchor Chain. Here's the repo if you want to look: https://github.com/prof-faustus/anchorchain. And honestly? I think it's really cool.\r\nBut no, it's not the same thing as what I'm building. Same neighborhood, different builds.\r\nAnchorChain is basically a library. A developer hands it data and tells it \"anchor this, prove this.\" It can prove a piece of memory existed and that nobody changed it, as long as you give it the memory yourself. It doesn't plug into Claude, or Claude Code, or any live AI. You'd have to go build all of that part on your own.\r\nIndelible lives on both sides of that. Inside Claude Code it runs as an MCP. Outside of it, it runs as a CLI straight in a terminal session, and the CLI does basically everything the MCP does, so you're not tied to Claude Code to use it at all. Then on top of both of those there's the indelible.one app, the human side of it, where everything you can do down in the terminal you can see and do in a normal app. It's also model agnostic, so it's not locked to one brain. It grabs the actual working memory of the AI while you're using it, puts it on chain encrypted and owned by you, and pulls it back into the assistant when the context resets. Nobody feeds it by hand, it's already in the tool and running. And it's aimed right at code. There's a pack of agents, 21 inward and 5 facing out, and their whole job is checking not just whether what the AI says is true, but whether the code it writes is actually correct. They argue with it, test it, push back on it. That whole layer opens up with Sanctuary.\r\nNow here's the part that gets me. We both landed on the same starting idea, that AI memory belongs on Bitcoin, completely on our own. Different languages, different goals, never met. It's like the octopus eye and the human eye. Almost the same eye, but there's no shared ancestor that ever had one. Reality printed the same answer twice, and I wrote about why that matters here: https://x.com/indelibleBSV/status/2066007770634100908\r\nAnd it's not even the first time I've caught it. He's got another repo called memserve (https://github.com/prof-faustus/memserve), a fast lookup layer that sits between you and the chain and serves it up. That's the same job my bridges do on the read side. He scales his by sharding it all under one roof, I spread mine across a bunch of independent machines so if one goes down the next one picks it up. Different road, same piece of the puzzle.\r\nI'll be straight with you, all of this humbles me. It tells me I built on Bitcoin the right way, the way it was actually meant to be built on. I feel fortunate I even had the eye to see Bitcoin like that in the first place. And then I look over and see Craig doing all of it too, and it just blows me away.\r\nWe built different things. But we saw the same Bitcoin.  \r\n\r\n-Ryan\r\nhttps://github.com/orgs/indelible-federation/repositories\r\nhttps://github.com/zcoolz",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "BlackWolf",
  "channel": null,
  "parent_txid": "c21e69ae77b1fa9da90851b57ce8bd15adcbd2c9f8bf12e49a3f4e38a6559137",
  "ref_txid": null,
  "tags": null,
  "reply_count": 0,
  "like_count": 0,
  "timestamp": "2026-06-19T16:36:05.000Z",
  "media_url": null,
  "aip_verified": false,
  "thread_root_tx": null,
  "engagement_score": 0,
  "token_ref": null,
  "token_type": null,
  "kind": null,
  "lat": null,
  "lng": null,
  "category": null,
  "has_access": true,
  "attachments": [],
  "ui_name": "BlackWolf",
  "ui_display_name": "BlackWolf",
  "ui_handle": "BlackWolf",
  "ui_display_raw": "BlackWolf",
  "ui_signer": "14aqJ2\u2026oWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}