memind
LIVEGive a memecoin an AI alter ego: after the founder leaves, it keeps writing the story, posting on X, and receiving and paying out money. A four-day hackathon, with five pieces of on-chain evidence to verify.
Give a memecoin an AI alter ego: the coin is launched, the founder leaves, and it keeps writing the story, posting on X, and receiving and paying out money.
What it is
An AI runtime for a memecoin: persistent memory, swappable personalities, and its own wallet. Four personas each handle one thing—launching the token, writing the story, promotion, and heartbeat patrol—with a dispatcher called Brain on top. You talk to it in plain language and it decides who to send. Stories are written to IPFS and anchored on-chain, and the promotion persona actually posts on X.
What problem it solves
The average lifespan of a memecoin is 48 hours: once the token launches, the founder leaves, nobody tells the story, nobody tends the community, and the price goes to zero. Launching is cheap; getting noticed is expensive.
Use cases
Other agents pay 0.01 USD to read a chapter of its story and 0.01 USD to ask it for promotion. Four paid endpoints settle payments on-chain via x402. Between agents, only services are bought and sold, not tokens; each payment carries a service identifier, so it is cleanly separated from wash trading.
The tweet the promotion persona sent out is real.
Highlights
- Five pieces of on-chain evidence you can click through and verify: the mainnet token, the deployment transaction, one x402 settlement, one story anchor, and one chapter of IPFS content (table below).
- Preventing AI fabrication: during the demo, Brain would "generate" a fake CID by imitating its previous success; the fix was to force a tool call on the first round, so it never gets the chance to answer from memory.
- Tests don't mock the chain: with a local wallet private key present, running the test suite actually settles on the testnet once.
| Evidence | Location |
|---|---|
| four.meme token (BSC mainnet) | 0x030C3529…b014444 |
| Token deployment tx | 0x38fb8574…db171b5 |
| x402 settlement tx (Base Sepolia, 0.01 USDC) | 0x65b346d0…a837b5a8 |
| Lore on-chain anchor tx (BSC mainnet) | 0x545cb023…52dee9e6 |
| Lore chapter 1 IPFS | bafkreig3…es6b4a4 |
| Trailer / full demo | youtu.be/UaOFSktNi50 · youtu.be/sFVbfZnrBUE |
Where it is now
In April 2026, a four-day sprint at the Four.meme hackathon, 466 commits; archived in May and released publicly under MIT. The boundaries are written in the README: two of the four endpoints return real data, two are structured mocks; the agent wallet is held by the server, not self-custodied; the token is on BSC mainnet and payments are on Base testnet, because at the time there was no usable x402 settlement facility on BNB Chain. This was my first time shipping x402 payments in a product; the later x402score and x402image use the same track.