How Forgora remembers, when it forgets, and why nobody can bring a memory back.

Forgora is a chat with an AI that keeps a memory of you: your name, your work, your people, your plans. That memory is encrypted under a key that belongs to your wallet, and the key is only released while the wallet holds at least 50,000 $FORGORA.

Sell below that line and a 24-hour clock starts. Buy back before it runs out and nothing is lost. Let it run out and the key is destroyed: the memory can never be read again, by anyone, and a public Forgotten counter goes up by one.

Why a coin, and why forgetting

• The big chat apps keep a memory of you for as long as they like. Deleting it is a support ticket, not something you can check.
• AI tokens sell credits nobody needs a coin to use. The coin has no job inside the product, so there is no reason to hold it.
• The memory a chat builds of you is the most valuable thing in it. Yet you never own it and can never lose it, so it means nothing to you.
• And most launches are taken by insiders in the first block. So the first holders are the wallets that sell to everyone else.

Forgora makes the memory the product and the coin the key. Hold, and it remembers. Leave, and the key is destroyed.

Compared with chat apps

NoteStatus: pre-launch. The app opens at launch, $FORGORA has not launched, and no contract of ours is deployed. Every counter on the site reads zero for that reason.

1. 1

   Sign in

   with your wallet: a signature, never a transaction.

2. 2

   Balance

   Forgora reads your $FORGORA balance on Robinhood Chain, plus any cold wallet you linked by signature.

3. 3

   Tier

   your balance sets your tier: memory on or off, messages a day, pictures.

4. 4

   Unwrap

   at or above the line, the key service unwraps your memory key for this session (30 minutes).

5. 5

   Chat

   the AI reads your memory, answers, and writes new memories, all encrypted with your key.

How a memory is locked

Every wallet with memory gets its own data key. It encrypts every memory and every saved chat, and the key service unwraps it only while your balance sits at or above your tier's line, at the latest block.

Layer 1 · Your words

messages, facts, plans, the pictures you send

Layer 2 · Your data key

random and 256-bit, one per wallet; it lives in memory for 30 minutes a session, never on disk

Layer 3 · Ciphertext

all the memory store ever holds

Layer 4 · Key service

unwraps your key only above the line, and destroys it when a grace period runs out

Forgetting is the destruction of the wrapped data key. Without it the ciphertext is random noise; the ciphertext is deleted next, so the storage is freed as well.

What it remembers

• Facts you tell it: your name, your work, your people
• Preferences: how you like answers, what to skip
• Ongoing threads: projects, plans, drafts in progress
• A short running summary of past chats

You stay in control

• Read every memory on one page
• Edit or delete any single one
• Download your chat history at any time
• Press Forget now: the same destruction, done on purpose

Two hard limits, on every tier

• Nothing sexual involving anyone under 18, in any form.
• No sexual pictures of a real, identifiable person.

Everything else is an open, direct conversation. A refused request costs nothing and uses no daily message.

Selling never wipes you on the spot. You get a full day to change your mind: buy back above the line and the clock stops, memory intact.

1. 1

   Rember

   At or above the line. The key unwraps at every sign-in and the memory keeps growing.

2. 2

   Grace

   Below the line. A 24-hour clock runs, and the memory still reads fine.

3. 3

   Forgor

   The clock reached zero. The wrapped key is destroyed, then the ciphertext. Nothing to restore.

A wallet that never held enough has no memory at all: it is a Guest, and every chat starts from zero.

What counts as holding

The balance is read at sign-in and every 30 minutes after. A watcher on the token's transfers starts or stops a clock within about a minute of any move.

A seller's 24 hours

1. 1

   The clock starts

   within about a minute of the balance falling below the line. The app shows the time left, and an optional notice goes to an address the holder set.

2. 2

   Buy back

   above the line before zero: the clock stops, the status returns to Rember, and the public count of saves goes up by one.

3. 3

   Or let it go

   download the chat history first if you want a copy, or do nothing.

4. 4

   Zero

   the wrapped key is destroyed, the ciphertext is deleted, and the Forgotten counter goes up by one, with the memory's age and nothing else.

5. 5

   Next sign-in

   an empty memory. Buying back now starts a new memory from zero; the old one cannot return.

NoteOn the landing page 24 seconds stand in for 24 hours so the clock can be tried. In the app the clock is 24 hours, the same for every tier.

When the clock reaches zero the wrapped key goes first, then the ciphertext. What is left cannot be read by anyone, so there is nothing to restore and nothing to sell.

Key handling, step by step

1. 1

   First sign-in above the line

   the API asks the key service for a new data key; it comes back wrapped, and only the wrap is stored next to the wallet.

2. 2

   Every later session

   the API proves the balance at the latest block and asks for an unwrap; the data key lives in memory for 30 minutes and is never written to disk.

3. 3

   Below the line

   the watcher opens a grace record: the wallet, its line and the deadline.

4. 4

   Deadline passed, still below

   the shredder tells the key service to destroy the wrap, deletes the ciphertext, and records the forgetting.

5. 5

   Forget now

   the same destruction, at once, when the holder asks for it.

The public counter

In phase 1 the Forgotten counter and the count of saves come from our own log. From phase 2 a small contract on Robinhood Chain receives an event for every forgetting and every save, so the counter becomes a count of public events that anyone can read, not a number we print.

event Forgotten(bytes32 keyIdHash, uint32 ageDays)event Saved(bytes32 keyIdHash, uint32 ageDays)

keyIdHash is the hash of a random key id: it links to no wallet. The counter carries ages and times only, never a wallet, a name or a word of content.

NoteDownload what you want to keep. Forgetting is permanent by design.

Memory needs the coin. The lines are set in tokens, not dollars, so anyone can check them at any block.

• Every tier with memory gets the 24-hour grace period before forgetting.
• Keeper and Vault can link up to 3 cold wallets, each proven by its own signature.
• Vault adds agents that work with your memory (writer, planner, coach) and Memory API grants: one app reads your memory until a date you choose.
• Spark has no free pictures; picture packs cover them.

With and without the coin

What a tier costs at different FDVs (MODEL)

The lines are set in tokens, not dollars, so they can be checked on chain at any block. From phase 2 holders can vote to move them once a quarter.

What $FORGORA will never do

• Pay holders anything: it is a key, not a share
• Buy memory without holding: memory is never sold
• Open somebody else's memory
• Bring a forgotten memory back
• Move the tier lines without a public holder vote

Why holders stay

Day 1

it knows your name

Day 30

it knows your projects and how you write

Day 120

it knows the people in your life and your plans

Selling below the line for a day costs all of that, and it cannot be bought back.

Each trade of $FORGORA pays the launchpad's 1% fee. 70% of it reaches Forgora's fee recipient: 0.7% of volume, with no extra tax on anyone.

fee to Forgora  = volume × 1% launchpad fee × 70% = 0.7% of volumecreator tax     = none, on any tradeMemory Fund     = 50% of the fee = 0.35% of volumemessages paid   = Memory Fund ÷ $0.002 per private message (ASSUMED)holders served  = messages paid ÷ 15 messages a day each

The weekly split, in public

The fund at three volumes (MODEL)

MODEL: $0.002 per private message, the memory read included (ASSUMED), and $0.039 per private picture (the picture model's list price). The real costs are published once the app runs.

Where else money comes from

Guest credits

$0.01 a message and $0.05 a picture, still with no memory (MODEL)

Picture packs

20 pictures for $0.80 for Spark holders, who get none free (MODEL)

Memory API

live for Vault: a holder grants one app read access until a date; in phase 4 partner apps pay per read

Agents with memory

live for Vault (writer, planner, coach); in phase 4 published agents are priced per run

Guest credits and phase 4 revenue go to the Memory Fund first, then to the same split. There are no data sales: a partner app only sees what a holder granted, and only while that holder stays above the line.

NoteMemory itself is never sold: it is only for holders, so the coin keeps its job.

Before launch the dev wallet and the time-lock are published. One minute after launch the receipt fills itself from the chain: the creation transaction, the dev buy, every wallet that bought in the first 60 seconds, and any group of them funded from one source.

Supply

1,000,000,000 $FORGORA, fixed, no mint

Launchpad

Pons, fair launch

Quote token

ETH

Sold on the curve

about 71.4%

Pool at graduation

about 20.4%, at 4.2 ETH raised

Locked at graduation

about 8.2%

Presale / team share

none / none

Tax

none

Fee to Forgora

0.7% of volume

Curve, pool and lock shares were measured on a live launch of the same launchpad in October 2026.

The dev buy

• At most 2% of supply, bought on the curve like anyone else.
• From one wallet, published on the receipt page before launch.
• Sent to a public time-lock for 90 days.
• No other wallet of ours buys in the first hour.
• The creation transaction buys for the dev wallet only. No list of wallets, no bundle.

What the receipt shows

Dev wallet

published before launch

Creation tx

fills at launch

Dev buy

at most 2% of supply, from that one wallet

Time-lock

90 days, address published before launch

First 60 seconds

every buyer, fills at launch

Cluster check

wallets funded from one source, fills at launch

Launch day

1. 1

   T−60 min

   the receipt page shows the dev wallet and the time-lock.

2. 2

   T−30 min

   a final check of the app, the counter and the receipt indexer.

3. 3

   T−0

   launch on the Pons launchpad; the creation transaction carries the dev buy only.

4. 4

   T+1 min

   the receipt fills with the creation transaction and the first buyers.

5. 5

   T+2 min

   the contract address goes out on our official channels, linking the receipt.

6. 6

   T+60 min

   a first-hour recap: every buyer, and any group funded from one source.

7. 7

   T+24 h

   a day-one note: chats, memories alive, the receipt.

Why people buy

• Memory needs the coin: the Spark line turns it on
• Every day above the line makes the memory harder to give up
• A seller who changes their mind inside the grace period buys back
• The Forgotten counter is a public story, told every day

Why supply shrinks

• 20% of the fee buys $FORGORA every week and burns it, in public
• The launchpad locks about 8.2% of supply at graduation
• Coins above the line are coins people choose to keep

Eight parts, one job between them: keep a memory readable while its wallet holds, and make its destruction certain when the clock runs out.

Web app

the landing page, the chat, the memory page and the receipt

API

sign-in, tiers, chat, credits and the memory itself

Key service

holds the key that wraps every data key; unwraps only above the line; destroys

Watcher

reads $FORGORA transfers and starts or stops grace clocks within about a minute

Balance sweeper

rechecks every active wallet every 30 minutes

Shredder

destroys wrapped keys at clock zero, then deletes the ciphertext

Private inference

endpoints that keep no request logs; sealed hardware in phase 3

Receipt indexer

builds the launch receipt and the Forgotten counter from public data

On chain

$FORGORA

the launchpad's standard token: 1,000,000,000, fixed, no tax, no mint

Dev time-lock

a vesting wallet with a 90-day cliff that holds the dev buy; its address is on the receipt before launch

Forget registry

phase 2: a small contract the key service writes to whenever a key is destroyed or a memory is saved

Phase 1: what is trusted now

• The key service runs on our own servers
• One data key per wallet, memories encrypted at rest
• Keys destroyed on schedule, every one logged
• Private inference endpoints that keep no request logs
• The honest gap: you trust our key service

Phase 3: sealed

• The key service runs sealed in confidential-computing hardware
• Its code is fixed and attested; the app shows the attestation
• Inference sealed in the same kind of hardware
• Nobody at Forgora can read or restore a memory, by design

Security and privacy

• Content and titles are ciphertext at rest
• Data keys are never written to disk; sessions expire
• No analytics on chat pages, no ad pixels anywhere
• The public counter carries ages and times, nothing else
• Sign-in is a wallet signature: no email, no password
• Rate limits per wallet and per connection on every endpoint

The app's API

GET    /api/auth/nonce        the sign-in message (sign-in with Ethereum)POST   /api/auth/verify       verify the signature, start a sessionGET    /api/me                tier, line, balance, statePOST   /api/chat              send a message (streamed)POST   /api/picture           draw a pictureGET    /api/memory            list memoriesPATCH  /api/memory/:id        edit one memoryDELETE /api/memory/:id        delete one memoryPOST   /api/memory/forget     destroy everything now (signed)GET    /api/history/export    download every memory and chatPOST   /api/links             link a cold wallet (its signature)POST   /api/credits           credit new payments nowPOST   /api/grants            a Memory API grant (Vault, signed)GET    /api/v1/memory         a granted app reads the memoryGET    /api/forgotten         public counter and the latestGET    /api/receipt           public launch receipt

A memory grows with every conversation, so the app measures it in public terms that never touch what it says.

Levels count kept memories, never what they say.

Rember streak

Days in a row above the line. A grace period that ends in a rebuy keeps it alive.

Saved by a rebuy

A seller who buys back inside the grace period saves the memory, and the public count adds one.

Forgotten wall

A live list of forgettings and saves: ages and times only, no wallet, no content.

Share cards

Streak, level and tier on a card the owner chooses to share. Nothing from the memory is printed.

Share cards

• Rember card: the streak, the level, the tier and the lime F.
• Saved card: “I bought back to keep 63 days of memory.”
• Forgor card, for the brave: “I let it forget me.”
• A card shows only the numbers its owner chooses to share; nothing from the memory is ever printed.

Gaming it, and why it fails

Phase 1 · weeks 1-3 · now

• Landing page, docs, launch receipt
• Wallet sign-in, chat, memory by tier
• Envelope encryption, grace clocks, the shredder
• Memory page: read, edit, delete, forget now, export
• Guest credits in ETH and USDG, credited from the chain
• Pictures, linked cold wallets, share cards
• Agents and Memory API grants for Vault
• Launch on the Pons launchpad

Phase 2 · months 1-2

• Forget events on Robinhood Chain: the counter becomes public data
• Holder vote on the tier lines, once a quarter
• Grace-clock alerts that reach you with the app closed

Phase 3 · months 3-4

• Key service sealed in confidential-computing hardware
• Attestation shown for every session
• Sealed inference
• An independent review of the key service, published in full

Phase 4 · months 6-12

• Partner apps on the Memory API, priced per read
• Published agents with memory, priced per run
• Memory that follows a wallet across partner apps

Launch is planned for the end of week 3 (ASSUMED).

Assumptions, open for correction

• Tier lines of 50,000 / 500,000 / 5,000,000 $FORGORA.
• A grace period of 24 hours, the same for every tier.
• $0.002 as the average cost of a private message, $0.039 of a private picture.
• Guest prices of $0.01 a message and $0.05 a picture.
• A fee split of 50 / 20 / 20 / 10.
• ETH as the quote token on the Pons launchpad.
• A dev buy of at most 2%, locked for 90 days.
• A session key lifetime of 30 minutes.
• No free pictures for Spark (packs only).
• Up to 3 linked cold wallets from Keeper up.
• The forget registry in phase 2, not at launch.

What we watch

Daily active chatters

1,000

Memories alive

2,500

Saved by a rebuy / forgotten

above 0.2

Messages per holder per day

15

Memory Fund cover

fund / inference cost ≥ 1

Guest to holder

5%

Targets for the first 30 days.

What we ignore

• Wallet counts: cheap to fake
• Follower counts
• The price on any given day
• Guest messages on their own

• In phase 1 our key service holds the keys: you trust us until phase 3 seals it in hardware.
• If volume is thin, inference can cost more than the fee brings in.
• The tier lines are a first guess and may move by holder vote.
• Forgetting is permanent: a careless sell costs a memory after 24 hours.
• The launchpad's owner keeps a timelocked power over fee routing that we do not control.
• $FORGORA can lose all of its value.

What is strong

• A coin with a job you would notice if you lost it
• Forgetting you can check, not a policy page
• No extra tax, and half of the fee pays for the AI
• A launch with a public receipt from the first minute

Can Forgora read my memory?

In phase 1 the key service runs on our own servers, so you trust it: memories are ciphertext at rest, a data key lives in memory for 30 minutes a session, and inference keeps no request logs. In phase 3 the key service moves into sealed hardware whose code is fixed and attested, so nobody at Forgora can read a memory by design rather than by promise.

What happens if I sell by mistake?

A 24-hour clock starts within about a minute. Buy back above the line before it reaches zero and the memory is saved, with nothing lost.

Can a forgotten memory come back?

No. The wrapped key is destroyed first, then the ciphertext, so nothing is left to restore, by anyone, including us. Buying back afterwards starts a new memory from zero.

Do my coins have to sit in the wallet I chat with?

No. Keeper and Vault holders can link up to 3 cold wallets, each proven by its own signature, and their balances count toward the line. Tokens inside a liquidity position, on an exchange account or lent out do not count.

Does $FORGORA pay holders anything?

No. $FORGORA is the key to your memory: it turns memory on and sets your daily limits. It pays nothing to anyone for holding it.

Why are the lines set in tokens and not dollars?

So anyone can check them at any block, whatever the price does. Holders can vote to move them once a quarter from phase 2.

What will it not talk about?

Nothing sexual involving anyone under 18, in any form. No sexual pictures of a real, identifiable person. Everything else is an open, direct conversation. A refused request costs nothing and uses no daily message.

What does the landing page remember about me?

Only what you do on it, in this browser tab: the sections you read and anything you typed into the sample chat. It runs the app's rules on a sample balance, and nothing leaves your browser.