Mneme.
The first-party browser wallet for Ligate. Holds $LGT, signs every transaction on the chain, and ships with a one-click Attest with Mneme button inside ChatGPT, Claude, and Gemini. Memory, attested.
Mneme is the canonical browser wallet for the Ligate attestation protocol. It holds your $LGT, signs every transaction on the chain, and ships with a one-click Attest with Mneme button injected into ChatGPT, Claude, and Gemini. Every prompt becomes a verifiable on-chain receipt against themisra.proof-of-prompt/v1 without leaving the conversation.
The name comes from Mnemosyne, the Greek titaness of memory and the root of the word mnemonic. The wallet's job is to remember the keys that anchor your AI history on chain.
Install
The browser extension publishes to the Chrome, Firefox, and Edge stores at devnet launch. Until then, the install flow is a manual unpacked-extension load from the open-source repo. Walkthrough lands in the /mneme/install sub-page once the first build is signed.
Why it exists
Ligate is a sovereign rollup signing ed25519 natively. Solana-style keys, not EVM-style keys. MetaMask doesn't speak ed25519, and Phantom doesn't speak Ligate's address format. Devnet needs a wallet that is first-class on day one. Mneme is that wallet, and stays the canonical Ligate signer even after EVM auth lands in v1 and MetaMask becomes optional.
The second job is product surface. Mneme is where the Attest with Mneme button lives, the moment the user actually feels the chain. Every other product on Ligate (Themisra, Iris, Kleidon) routes attestation signing through Mneme as the default signer.
Who uses it
- → AI users who want a permanent, verifiable record of every model conversation
- → Prompt creators earning royalties on attested prompts via Themisra
- → $LGT holders staking, voting, and paying gas on Ligate
- → Kleidon end users buying Passify subscriptions, holding SkinsVault assets, minting on MintMarket
- → dApp developers wiring one wallet connector instead of three
What it ships with
1. Self-custodial keys
ed25519 keys derived from a BIP39 seed phrase. Same security model as Phantom or MetaMask: the seed never leaves the device, the extension never sees it after onboarding, recovery is on you.
2. Attest with Mneme
A content script injects an Attest with Mneme button into the supported AI chat UIs. Click it, and Mneme hashes the prompt and reply locally, opens an approval popup, and submits an attestation against themisra.proof-of-prompt/v1. The receipt anchors on Celestia in ~200ms and costs ~0.0001 LGT.
3. dApp connector
A standard window.mneme provider injected into every page. Themisra, Kleidon, Iris, and partner schemas integrate with one snippet. No bespoke per-product wallet plumbing.
4. MetaMask compatibility (v1)
When EVM auth lands in v1 of Ligate Chain (the secp256k1 lane lands as a composable authenticator in the runtime), MetaMask can sign transactions on Ligate too. Mneme stays first-class: the canonical signer for ed25519-native paths, and the better UX for the AI attestation flows that are Mneme's reason for existing.
Why ed25519, not 0x...
Every native Ligate transaction is signed with ed25519. Addresses render as lig1... (bech32m, prefix lig). EVM-shaped addresses come later as a parallel auth lane, not as the default. The full flow (what the user sees, what node RPCs see, what attestors verify) is documented in Chain architecture.
Roadmap
- v0 (Q2 2026): seed onboarding, Ligate signer, AI-tab content scripts for ChatGPT, Claude, Gemini
- v0.5 (Q3 2026): dApp connector spec, Themisra and Kleidon integrations
- v1 (Q4 2026): EVM auth lane, MetaMask interop, hardware-wallet support
- v1.5 (2027): mobile companion, biometric unlock, social recovery
Open source
Mneme's extension code lives under the ligate-io org and ships under MIT once the first audited build is tagged. Self-custody is non-negotiable: the wallet binary you install is the wallet binary you can read, build, and verify yourself.