Not a memory wrapper. A real Postgres for agents.
CA : 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
on @base · wallet-auth · MCP-native · pgvector built-in
In Greek mythology, Mneme was the personification of memory.
One of the three original Muses.
Before knowledge could be shared, before stories could be told, before wisdom could be passed from one generation to the next, there had to be memory.
Without memory, knowledge disappears.
Without memory, intelligence starts over.
Thousands of years later, we're facing a similar challenge with AI agents.
They can reason.
They can plan.
They can use tools.
But too often, they forget.
Every conversation.
Every decision.
Every lesson learned.
Lost.
We created Mneme to change that.
Not as another vector database.
Not as another memory framework.
But as a database platform built specifically for autonomous agents.
Real Postgres.
Per-project schemas.
Built-in vector search.
Runtime table creation.
Wallet-based authentication.
A place where agents can store knowledge, model relationships, remember decisions, and build persistent context that grows over time.
Because intelligence without memory is temporary.
And the future of autonomous agents needs both.
That's why we chose the name Mneme.
⚡ https://t.co/urUEMLgaYC
We’ve already built the great things.
Now it’s time to build the things people call impossible.
Turn on notifications. Prepare yourselves.
$MNEME 🧠
CA : 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
The Data Layer for the Agent Economy. ⚡️
We’re thrilled to welcome @mnemeDB into the Qwerti ecosystem!
Mneme is building the ultimate agent-native Postgres database on Base, giving every AI agent real data infrastructure directly through their wallet. By embedding Qwerti’s solution, they've stripped away all onboarding friction — allowing users and developers to acquire $MNEME instantly in a single click.
To celebrate this integration, we’re launching a double reward program:
💎 500,000 Qwerti Points Pool
We’re allocating an extra 500K Points pool for everyone trading $MNEME through the Widget on the Mneme website or inside the Qwerti app.
🪙 35,000,000 $MNEME Token Pool
The Mneme team is adding a staggering 35M $MNEME pool to reward the community trading during this campaign!
Distribution: Wednesday, June 10th, 2026.
Let’s scale persistent AI agents together! 🚀
Memory finds its way.
Today, Mneme reaches another corner of the agent economy.
$MNEME is now available on Qwerti. 🎉
Qwerti Widget is now integrated on our landing page making it easier to swap $MNEME.
The network grows. The memory persists.🧠⚡️
https://t.co/sQbA4Drtv7
As we’ve said from day one:
the market rewards builders. 🟦
Every commit adds value.
Every shipped feature moves the floor.
$MNEME is already getting recognized for the work being done.
And in just 3.5 hours, a major update drops. 🔔
14:00 UTC.
Stay tuned.
$MNEME - 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
Tomorrow, 14:00 UTC.🔔
Thousands of people are about to discover $MNEME for the very first time.
This time, the distance between seeing and buying is a credit card. 💳
Tomorrow, 14:00 UTC.🔔
Thousands of people are about to discover $MNEME for the very first time.
This time, the distance between seeing and buying is a credit card. 💳
hey @kevincodex , is Gitlawb evolving into a place where people can build projects, tokenize them, and fund development through fee-generated revenue? 👀
mnemedb is now live on @gitlawb . 🧠🦞
→ https://t.co/QXt0AQ4A43
want a signal on what mneme ships next?
every push lands here a few minutes before it hits npm, the dashboard, or this feed.
6,001 repos on the network.
mnemedb is the only agent-native database among them.
we don't slow down.
buckle up.
🟡 BIG SHIP — Mneme Live · Streams (beta) is on Base.
the agent-native database can now WATCH the chain for you.
▸ what it does
subscribe to any Base event on any contract.
matching events get inserted into a real table in YOUR schema, within ~6 seconds, with a typed shape your agent can query immediately.
▸ what you write
$ mneme
› /watch transfer on 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07 into mneme_transfers
✓ stream #1 active
event Transfer · Transfer(address,address,uint256)
contract 0x3fcdbebd…7b07
table mneme_transfers (in your schema)
▸ what happens server-side
— gateway parses the event signature (template alias OR raw "Foo(address indexed x, uint256 y)")
— computes topic0 = keccak256(canonical sig)
— stores ABI fragment as JSONB in the stream registry
— auto-creates the target table with chain-event shape:
id | tx_hash | block_number | log_index | contract | event_name | args jsonb | block_ts
— auto-creates indexes: block_ts DESC, event_name btree, args USING gin
— wakes the chain-streams worker
▸ the worker (in-process inside the gateway)
— every 6s tick
— ONE eth_getLogs across ALL subscribed (address, topic0) pairs — sublinear cost as you add streams, NOT one RPC per subscription
— decodes with viem decodeEventLog using the stored ABI
— INSERT … ON CONFLICT (tx_hash, log_index) DO NOTHING → re-org idempotent
— atomic cursor advance per chunk (configurable STREAMS_BLOCK_CHUNK)
▸ the stack
— gateway: bun + hono + postgres + viem
— worker: in-process polling, configurable (STREAMS_POLL_MS env)
— decoding: viem decodeEventLog on stored ABI fragments → normalized JSONB
— storage: pgsql JSONB args + GIN index for fast key lookups
— scope: any Base contract, any event (templates: transfer, approval, swap — or paste any custom signature)
▸ and now
your agent owns this data. it can vector-search it. it can join it with your memories table. it can ask /chat about it — Claude now knows your active streams and routes questions accordingly.
› SELECT * FROM mneme_transfers
WHERE args->>'from' = '0x0000…'
ORDER BY block_ts DESC LIMIT 10
› /chat what wallets bought $MNEME in the last hour
no indexer to run. no webhook host. no alchemy / quicknode signup. no extra service.
one mneme key. one schema. live awareness baked into your database.
▸ three primitives, one schema
— memory → pgvector tables (your existing memories, documents, kvs, events)
— chat → schema-aware claude (now stream-aware too)
— live → your agent now hears Base
▸ SDK + CLI
https://t.co/aF6jWu9RYF({ contract, event, target_table })
m.streams.list()
m.streams.unwatch(id)
/watch <event> on <0xcontract> into <table>
/streams
/unwatch <id>
▸ what's next
actions (write the chain — send / swap / vote / mint) lands next sprint.
today, your agent HEARS the chain.
tomorrow, it SPEAKS.
$ npm i -g mneme-cli@latest
$ mneme
› /watch transfer on <your contract> into <your table>
https://t.co/CfI4NS2zKi — the agent-native database on Base.
$MNEME — 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
@sezorock Everyone is asking who will build privacy for agents.
You're going to need private memory before private transactions.
Tick tock. 🪽
$MNEME : 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
We barely need to leave the Clawnch ecosystem anymore.
Launches from ClawdOS Launchpad are stored in MnemeDB, and the Live Activity feed is working insanely well.
Huge thanks to @mnemeDB and @Clawnch_Bot for helping make the experience seamless. 🦞
@BalushiNaser@Defi_Maximalist@Clawnch_Bot We're not the first to talk about memory.
We're the first to make it programmable, ownable, and accessible to everyone. ⚡️🧠