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
How Misogi works
Learn how to connect an external agent, set payment limits, review ETH requests, and configure your own Safe. These guides distinguish available tools from planned functionality. A Python SDK is available in the Agents setup guide.
Status
Misogi provides agent controls and transaction tools on Ethereum Mainnet. Connect through Reown and verify ownership with Sign-In with Ethereum. Register external agents, configure their permissions, and review persisted ETH payment requests. Wallet-reviewed sends and ERC-20 revokes use real RPC checks before explicit wallet approval. Customer-owned Safes can use Omamori grants and Kusanagi recovery. Login alone never grants spending authority.
What Misogi is for
Your AI agent runs on your own host; Misogi does not host a model or chatbot. It provides a workspace for permissions, requests and transaction results. App rules apply to requests made through Misogi. Safe grants are enforced separately by their installed onchain contracts.
- Agents (Kitsune): individual API keys, verified connections, allowed recipients, ETH limits, expiry and owner-reviewed requests. Pause access, rotate keys or revoke an agent. API 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.
Wallet-reviewed payments are sent explicitly by your wallet. For Safe payments, the service Gate can sign an exact payment only when an existing onchain grant permits it; the configured agent wallet still submits the transaction and pays gas. External Gate signing remains an expert option. Scheduled strategies, x402 payments, EAS receipts and notifications are not yet implemented.
Directory of all 29 tools
What exists today
- Home, the Agents workspace, setup guides, a downloadable Python SDK, and a catalog of 29 features with their individual implementation scope.
- 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. Safe tools use a customer-owned Safe, not a shared operator Safe. The owner-reviewed agent payment flow does not require a 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
Verification covers wallet and policy rules, agent permissions, request idempotency, key controls, and Gate authorization binding. Browser checks covered Reown connection, signed login, connection and session restoration, the agent request lifecycle, and Safe service Gate setup. Read-only Mainnet checks verified canonical module data and authorization digest encoding.
These checks did not broadcast funded payments, install Safe modules, or execute recovery and escrow operations. They are not an independent security audit or a claim that every wallet has been individually tested.
Wallet access
Connect wallet opens Reown AppKit directly, with installed EVM wallets and WalletConnect for 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.
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. Reown processes wallet connection data and may restore a connection when you open the wallet chooser; this alone is not a verified Misogi login. Disconnect clears this page's connection and requests a Reown disconnect. Remove persistent site permission in your wallet settings. Reown analytics, social login, swaps and onramp are disabled.
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
The catalog groups 29 features into seven zones. Live tools provide the specific functions described on their pages; other features remain planned. Read each feature's current scope and requirements before using it.