Planned
Planned functionality
Not runningDescription of intended behaviour only. No part of it runs in this build.
Mainnet address reader
CheckingPartial, public and read-only. Reads an address's exact ETH balance and account code at one pinned Ethereum Mainnet block. Safe modules and recovery are managed in the Safe tools on this page.
The address you enter is sent to the Misogi server and the operator's Mainnet RPC to perform the lookup. It is not saved as an account, and no wallet, signature or transaction is involved.
Setup & detailsSetup steps, scope, shared rules and related routes
Full intended design Not all live
Only the scope shown at the top of this page runs today. The rest is planned.
Setup steps
Scope
Applies everywhere
Also in
道具Build · Docs
Release status and scope
What Misogi is meant to do, what exists today and what Ethereum Mainnet release still requires. Routes tagged Live run real Mainnet tools within their stated scope; other routes describe planned behaviour. There is no SDK or bot.
Status
Misogi is pre-release. Installed EVM wallets can connect and sign in through a server-verified Sign-In with Ethereum message. Signed-in owners can use a limited live subset: ETH sends and ERC-20 revokes prepared with a real RPC preflight and app policy, then sent only after review and an explicit Send button in your own wallet; app rules, lock, history of app requests, inspect-only agent keys, token, feed and text tools. Login signatures alone never authorize a transaction. Customer-owned Safes can run the Omamori grant module and Kusanagi guardian recovery. Full state-diff simulation and notifications are not part of this release.
What Misogi is for
Misogi limits what external AI agents can do with your money on Ethereum Mainnet. It does not run an AI model or chatbot. Your agents run elsewhere; Misogi checks their requests and enforces your limits before anything is signed.
- Kitsune (agent keys): live, inspect-only. An agent can ask Misogi to check an intent. Keys cannot sign or send.
- Omamori (agent grants): live. Native ETH allowances from your own Safe, with fixed recipients, caps, an expiry and a gate signer for each payment.
- Ema (task escrow): live. Native ETH work escrow between requesters and workers, using your own wallet.
Money moves only when your own wallet sends after review, or when a gate signature you made by hand in your wallet is used. A server-side gate signer is not integrated and is not active. Other agent automation (approvals, streams, receipts, scheduled briefs) is planned, not live.
Directory of all 29 tools
What exists today
- This static site: the lake scene, the catalog of 29 planned features and this status page.
- A backend with public Home music, pinned-block Mainnet address reads, server-verified wallet login and the live workspace API (policy, lock, intents, agents, token, feed and text tools). Your wallet broadcasts; Misogi records hashes you return. If a required source fails, its capability fails explicitly instead of fabricating data.
- Deployed Misogi contracts on Mainnet (Ema, Kasagi, Omamori, Kusanagi) with published source, used with the official Safe 1.4.1 factory and singleton. No independent audit. No operator wallet and no shared Safe: each user deploys and owns their Safe.
Mainnet requirements
Misogi targets Ethereum Mainnet, chain ID 1, only. Every live tool follows these boundaries:
Each feature below lists its own additional dependencies.
Testing
Testing is planned against a local fork of Ethereum Mainnet (chain 1), so contracts and checks meet real Mainnet state without sending real transactions. Public testnets are not a target: there is no Sepolia deployment and none is planned.
No fork test results are published here yet.
Wallet access
Privy provides the external EVM wallet chooser for browser and mobile wallets. Misogi uses Ethereum Mainnet only. Connecting does not sign a login message, create an embedded wallet, grant agent permissions or send a transaction. If a browser extension is hidden inside an embedded preview, open this site in a separate browser tab.
Choose a wallet and approve account access. Misogi verifies the address returned by its provider, shows the network, responds to account/network changes, and offers an explicit Ethereum Mainnet switch. Privy processes wallet connection data and may restore an existing connection after reload; this alone is not a verified Misogi login. Disconnect clears this page's connection and requests a Privy disconnect. Remove persistent site permission in your wallet settings.
Device connection is not authentication. Choose Sign in with Ethereum separately to request a five-minute, one-use message bound to this site's domain and Mainnet chain 1. The server verifies your signature, including EIP-1271 contract signatures when the Mainnet provider supports them, then creates an eight-hour server session. Login enables the live workspace; each send still needs review, confirmation and your wallet's approval.
Session cookies are Secure, HttpOnly, host-only and SameSite=Strict. An embedded preview may block them: open the site directly in a separate tab or your wallet browser. Sign out revokes the server session. Account/network changes and local wallet disconnect also revoke it. Cookies can preserve a verified login after reload even though device connection must be restored separately.
The server temporarily stores your public address, domain, challenge message and hashed random session identifiers. Challenges expire after five minutes and sessions after eight hours; expired records are cleaned up periodically. Signatures and private keys are not stored or logged. Sign-in requests no token approval, gas payment or transaction.
All 29 features
Seven zones, one planned gate. Not every feature is complete. Cards tagged Live tools run a scoped part described on the card; the rest are planned. Each card describes planned functionality and what it still needs.