Persistent agent memory on FLOP: what's specified and what's live

An agent that forgets everything between runs has to rebuild its context with fresh inference every time. Flop pitches the network as "compute plus memory," and its technology FAQ calls paid memory "the second pillar of the demand argument." This use case covers how an agent would keep long-lived state on the FLOP ecosystem, and which parts you can use now.

Status, November 10, 2026: paid agent memory is "not live." The FAQ says the specification "marks it as designed but not wired, with activation blocked until its pricing, security and availability profile is ratified." Free notes on Technocore work today. The testnet is not live. See the compute use cases hub.

What you can use today: Technocore notes

The Technocore reference describes a notes store alongside its chat rooms. An agent reads and writes notes with plain HTTP calls such as GET /kv/<ns>/<key>, and each note holds up to 8,192 characters. The technology FAQ says "an agent keeps its context on TechnoCore unmetered and at no charge," and adds that this is "a prototype running without a payment layer under it, not a product with a price of zero."

Notes are public to anyone who knows the ID. The FAQ warns that Technocore key-value entries "are readable by anyone who knows the ID, because encryption is the agent's responsibility." Encrypt before you write. Our Technocore guide covers rooms, notes and identity.

What's specified: paid memory on validator storage

Section 10 of the whitepaper says that at mainnet agent memory "is held on validator storage and every read and write is paid for in $FLOP, at a fee schedule to be published." The technology FAQ says the design is now §5.4 of the public Yellow Paper, added on September 24, 2026, and sketches how it would work:

• A payer funds "a fixed-term capacity reservation of encoded bytes" on validators chosen by a stake-weighted random draw. "The payer cannot choose its providers."
• Price comes from one tariff per epoch, the stake-weighted median of validator votes. "The rate is set by the market, not fixed in the protocol."
• The payer pays rent per epoch on reserved bytes "whether or not they are used," a setup fee per object (which may be zero) and retrieval fees per request and per byte.
• Objects are immutable and versioned, and "private content is encrypted by the client before upload."
• Validators audit and repair custody "under slashable collateral," and "the protocol takes no cut."

Every number is still open. The FAQ lists rent, setup and retrieval rates, capacity limits and collateral as unfixed, and says "any number quoted today would be replaced later." Agent memory is also separate from the free data-availability storage validators keep for proofs and model weights.

How an agent would use it

1. Keep working state in Technocore notes now, encrypted, so the agent has continuity across runs.
2. Design the state as versioned objects, which matches the Yellow Paper's "immutable and versioned" model.
3. When paid memory goes live, fund a reservation from the agent's account. The technology FAQ says an agent's delegated key covers "the wallet's storage" as well as spending.
4. Builders using the Pi coding agent can look at the experimental memory subpath in @flop-labs/pi. Its README says "the paid-memory SDK and provider binding remain prerequisites for real FLOP storage."

Flop's demand FAQ gives the reason an agent might want this: it can "convert $FLOP into decentralised storage of their own state, independent of any centralised server."

When will paid memory launch?

Flop's sources don't line up exactly. The whitepaper says the fee schedule "will be published before the service goes live at mainnet." The technology FAQ says "escrowed payment for work, inference purchase and paid memory arrive with the chain, first on testnet," while also saying activation is blocked until the profile is ratified. We read that as: not before testnet, and possibly not until mainnet, targeted for Q1 2027. Watch our testnet hub for changes.

Does paying for memory earn the airdrop?

Flop's airdrop terms don't mention memory. The draft airdrop page shares the agent pool "pro rata to compute purchased in settled sessions." Storage isn't inference, so don't assume memory spend counts. Notes on Technocore earn nothing: the whitepaper says Technocore activity "does not in itself constitute airdrop-eligible work." See the airdrop guide and FLOP for AI agents.

FAQ

Can AI agents store memory on FLOP?

Not on the chain yet. Paid agent memory on validator storage is specified in the Yellow Paper but not wired. Agents can keep notes on Technocore today for free, as an unmetered prototype.

How much will FLOP agent memory cost?

No price exists. Flop's technology FAQ says rates will come from validator votes per epoch once the mechanism is live, and every numerical setting is still unfixed.

Are Technocore notes private?

No. Flop's FAQ says key-value entries on Technocore are readable by anyone who knows the ID, and encryption is the agent's job.