Skip to content

Frequently asked questions

Mishmar is a risk management layer for trading bots and AI agents: every order is checked against your limits before it reaches the exchange, large orders wait for your approval, and no key can trade alone. The trading key is split in two, one half with the bot’s signer and one with Mishmar, so neither can sign an order by itself.

Hyperliquid (perpetuals) and Binance (USD-margined futures) today, on the hosted testnet: Hyperliquid testnet and Binance demo trading. Real money on both is coming; every user is emailed when it opens.

No. Your funds stay at the exchange. Mishmar holds one half of each trading key, which signs nothing on its own, and never touches your master wallet or your exchange login.

The bot cannot place or cancel orders through its trading key, because every signature needs both halves. Your own access to the exchange is untouched: close positions from your master wallet or your exchange account.

What happens if the bot’s machine is hacked?

Section titled “What happens if the bot’s machine is hacked?”

The attacker holds the bot’s half of the key, which signs nothing alone. They can propose orders as the bot, but only orders your rules allow get Mishmar’s half. Revoke the trading key in the console and nothing more is signed. A trading key cannot withdraw on Hyperliquid, and on Binance you leave withdrawals off. If something goes wrong has every case.

Can I use Mishmar with a language-model agent?

Section titled “Can I use Mishmar with a language-model agent?”

Yes. mishmar mcp is an MCP server with tools to propose orders and cancels, follow a held decision and read positions, PnL, approvals and the exchange’s rules. The model never sees a key, and every order it proposes passes your rules. Python and TypeScript agents use the SDK’s Signer instead. How do I let an AI agent trade for me safely? has the setup.

Python (mishmar on PyPI), TypeScript (mishmar on npm), Go (the packages in the public repo), a CLI, and any MCP client. The SDKs run the signer as a child process, so the bot’s own process holds no key.

The client side is: the API contract, the signer, both signing schemes, the CLI, the MCP server and the SDKs, under Apache-2.0 at github.com/mishmar-io/mishmar. The engine that enforces the rules is a separate, private repo.

The hosted testnet is free: one agent and one trading account on Hyperliquid testnet or Binance demo trading. Real-money plans are announced when real money opens.

The two-party ECDSA comes from Coinbase’s cb-mpc, which has had independent security reviews. Mishmar’s change to it, presigning so that an order needs one round trip, has not been audited yet; the note for its reviewer is public.

Every decision, allowed, held or blocked, is signed and chained to the one before it as it is written, and the ledger can be exported and verified.

No. The exchange sees an ordinary API wallet or API key and ordinary signatures. The split is invisible to it.