vault-ipc
Skill3 starsChanged 8 months agoMITView on GitHub
Unified Unix socket replacing the old two-socket model (x402-signer.sock + openmm-creds.sock).
The file
Files
Vault IPC Socket
Unified Unix socket replacing the old two-socket model (x402-signer.sock + openmm-creds.sock).
Socket
- Path:
/tmp/openmm.sock(override viaOPENMM_SOCKETenv var) - Permissions: mode
0600(owner-only) - Started by:
openmm serveafter interactive vault unlock
Message Protocol
JSON messages over the socket, dispatched by type:
{ "type": "sign_payment", "payload": {} }
→ { "signature": "0x..." }
{ "type": "get_credentials", "exchange": "mexc" }
→ { "apiKey": "...", "secret": "..." }
{ "type": "ping" }
→ { "status": "ok", "wallet": "0x...", "exchanges": ["mexc", "gateio"] }signAndWipe Pattern
Private key is decrypted inline, used once, and goes out of scope immediately. It is NEVER held in a long-lived variable.
Security Invariants
- Password typed once interactively in terminal — never passed as flag or env var
- Socket file = proof of authentication (exists → vault is unlocked)
- Stale socket cleaned up on startup, deleted on shutdown
- MCP server connects via socket — does NOT hold vault data in its own memory
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

