AINMEM - P2P Memory

Demo

About

Don't sell your old phones. Make them your family's server. We replace our phones every year or two. Each time, we move everything over, the new phone fills up again, and the old one goes into a drawer or gets sold. Everything on it is left behind: years of photos, and call recordings no one will ever search again. Paying for cloud storage doesn't solve it. You pay every month to archive files you still can't find. AINMEM turns that old phone into your family's home server. Plug it in and leave it on. It connects peer-to-peer with the phones your family uses today. No cloud account, no upload, and nothing to move to a new phone. Each person taps "Allow sharing" on a folder, and files stream straight from the device that holds them. When a device is turned off, its files leave the network with it. A family agent then searches every phone at once, old and new, and organizes what it finds into a shared family workspace. It runs on your own devices, so nothing is sent to an outside AI. Here's what that looks like. Five years ago, my grandmother taught me her kimchi over the phone. I never learned it, and the call stayed on her old phone in a drawer. I plugged that phone back in and asked our family agent how Grandma made her kimchi. It found the call and turned it into a recipe with a shopping list. Other families wanted her kimchi too. So Grandma put a price on it. Anyone outside the family can open it with x402, 1 USDC on Base, paid straight to her wallet, while the recipe is served from her old phone. No platform in between. Her old phone is the server. Her memories. Her device. Her price. That's what sovereign means. AINMEM continues our Relational Agent project, built on the idea that the relationship, not the individual, is the basic unit of an agent. Today, a family's drawer of old phones. Next, any group that wants to share without a server in the middle.

How it's made

AINMEM is built from two products that work together: AINDrive, a peer-to-peer file network that turns any phone into a node, and AINMEM, a family workspace with an on-device agent that sits on top of it. x402 adds payments. 1. AINDrive: every phone is a node AINDrive runs on iOS, Android, Desktop and Web. Any phone, including an old one left plugged in at home, becomes a node in a private family network. When a user taps "Allow sharing" on a folder, the device announces it to family peers over a direct device-to-device connection, using Willow Protocol. There is no central server and no cloud copy. Files are never uploaded; they are streamed from the owning device when someone opens them, and they are available only while that device is online. This is how an old phone in a drawer becomes a family server: plug it in, leave it on, and everything on it is reachable again from the phones the family uses today. 2. AINMEM: the family workspace AINMEM connects AINDrive folders from every family device into one Notion-style workspace. Pages link to files where they live instead of storing copies, and are grouped by who shared them and by type (calls, recipes, photos, documents, even bitcoin private key!). The "Family folders" indicator shows which family devices are online right now. 3. The family agent Inside AINMEM, the family agent runs on Gemma model 4 E2B fully on-device and never calls an outside AI service. It transcribes call recordings, builds a local RAG index over every family device's shared folders, and answers requests like "How did Grandma make her kimchi?" It returns structured results, such as a recipe page with a shopping list, and marks anything the source never said, like amounts Grandma didn't mention, instead of inventing it. The agent itself works offline; fetching a file from another device still requires that device to be online. 4. x402 payments An owner can put a price on any file in AINMEM. When someone outside the family opens it, the owner's device responds with HTTP 402 Payment Required. The buyer pays 1 USDC on Base from MetaMask, the payment settles to the owner's wallet, and the file is then streamed directly from the owner's device. Notable / hacky - An old phone as a paywalled server: x402 is usually used to put APIs on servers behind a payment. Here it guards a file on a personal phone. - Storage is deliberately not in the cloud or on-chain. Only the payment touches the chain; the file never leaves the owner's device. - Cross-device search without a central index, running on an on-device model. - The agent flags what the source didn't say, so family knowledge is organized without being made up.