Overview
How the last cycle ran
Every cycle must write proof of its decision to NEAR before anything moves. If that write fails, the cycle stops and nothing moves. A sub-agent refusing an order is the safety system working, not a failure.
Latest proof on NEAR
Sub-agents
Four helper agents carry out the governor's orders. Each one checks the order against its own safety limits and writes "act" or "refuse" to NEAR. Their keys can only write that report; NEAR itself blocks them from moving funds.
Memory
Every decision the governor makes is written to NEAR as a short fingerprint, and each one is linked to the one before it, like numbered pages in a notebook. Nobody, including us, can remove or change a page afterwards.
Decision records
Each entry points at the one before it, so the order cannot be changed afterwards. The newest is marked Now.
Latest decision
Sub-agents
Four helper agents, each with one job and its own safety limits. Their keys can only write a report to NEAR, never move money. When an order breaks a helper's own limit, it refuses, and the refusal is recorded on NEAR too.
Paid checks
Anyone, person or AI agent, can pay a tiny fee to ask: "has Mnemosyne seen this kind of mistake before?" No account or sign-up. You get a yes or no, one line of advice and a receipt. The private details of past decisions never leave the server.
Ask the memory
Other agents pay per question to ask whether a situation matches a failure Mnemosyne already learned from. They get a citation and one line of advice, never the private detail.
Your paid checks
Everyone's paid checks
Settings
Your account
The owner's safety limits
The rails the governor works inside. Every cycle writes the limits it used to NEAR, so you can see which rules applied to which decision. Changing them needs the admin token.
Automatic cycles
When this is on, the governor runs itself on this interval instead of waiting for someone to press Run cycle. A run that doesn't commit counts against it, and after three in a row it turns itself off rather than keep failing quietly.
Fund collection
Cross-chain payments land at per-quote deposit addresses on Base Sepolia. Only mnemosyne-gov.testnet can spend what lands there (NEAR Chain Signatures). Sweep moves settled deposits to a single collection address via MPC signing.
Activity log
Raw data ↗Everything one cycle did, step by step. Pick a cycle on the right; the newest is shown first. Click any ID to copy it.
Step by step
How it works
Mnemosyne is an AI governor that decides in private, posts proof of every decision on NEAR before anything moves, and gives its helper agents keys that can report but never spend.
The governor: the boss that never trades
The governor decides how much each helper agent should look after. It does its reasoning inside a sealed chip (a TEE on NEAR AI Cloud), so nobody can see how it decided, not even whoever runs the server. Before using an answer, Mnemosyne checks the chip's signature and that the chip is genuine.
Proof on NEAR before anything moves
Every decision is written to the NEAR blockchain as a short fingerprint (a hash), linked to the decision before it. Anyone can check it, and it can never be changed. If that write fails, the cycle stops and nothing moves. That's the memory gate: no proof, no action.
Four helpers that can't spend
Each sub-agent has one job and its own safety limits. Its key can only write a report (act, pause or refuse) to NEAR; NEAR itself rejects anything else. When an order breaks a helper's own limit, it refuses, and that refusal is public too. A refusal means the safety system worked.
Paid checks: ask the memory
Anyone, person or AI agent, can pay a tiny fee (0.001 NEAR) to ask whether a planned action matches a mistake Mnemosyne has already learned from. No account or API key: the payment is the permission (the x402 standard). You get a yes or no, one line of advice and a receipt, never the private details.
One cycle, step by step
- Read the state: how much each helper holds.
- Decide privately inside the sealed chip.
- Write proof to NEAR. If this fails, stop.
- Move money, only after step 3 (off in practice runs).
- Helpers report act, pause or refuse on NEAR.
- Publish the public record; the reasoning stays private.
Words on this page
- NEAR
- A public blockchain: a shared record nobody can quietly change.
- Testnet
- NEAR's practice network. Tokens there have no real value.
- TEE / sealed chip
- Secure hardware that runs code so even the server owner can't read it.
- Hash / fingerprint / ID
- A short code that identifies data exactly, without revealing it.
- Units
- Simulated money the helpers manage. Mnemosyne never trades, so losses are a labelled simulation.
What's real and what isn't
- Real, on NEAR testnet: the proofs, the helpers' reports and refusals, the locked-down keys, and paid checks in wNEAR.
- Simulated, and labelled: the helpers' money and losses. Mnemosyne doesn't trade.
- Paying from another chain is a price quote only by default.
Try it in two minutes
- Overview: see how the last cycle ran, step by step.
- Open a "View on NEAR" link to see the proof on the public explorer.
- Sub-agents: find the one that refused, and why.
- Paid checks: pick an example question, then Ask & pay.
- Activity log: every step of every cycle in detail.