Security
Your keys stay on your device
Mutexa is non-custodial by design. Keys are generated and kept on your device, Mutexa's servers never hold funds or keys, and funds sit in accounts only you control.
Non-custodial by design
Keys are generated and kept on the user's device. Mutexa never holds funds.
Accounts from your signature
Slice accounts are derived on the device from a signature you make. The keys never leave it.
Local risk engine
The engine that watches every slice runs on your device, not on a server.
Stops on the device
Take-profit and stop-loss levels are kept locally and sent only when they trigger.
Open source
The client, the venue adapters and the slicing logic are planned to be open source, published on the official Mutexa GitHub (github.com/mutexa-labs), so anyone can verify what the software does with keys and orders.
Network privacy
API traffic can be routed through Tor so that a shared IP address doesn't tie slices together.
Trust boundary
What lives where
Your device
- Keys
- Slice accounts
- Risk engine
- Hidden stops
- One book
Mutexa servers
Never hold funds or keys.
Privacy rails
Fund, rebalance and exit every slice.
Venues
See their own accounts, nothing more.
Rules the software keeps
Safety and privacy, in the same rule
Independent audit before launch
An independent security audit is completed before launch. Until then, paper mode lets anyone rehearse with live prices and no real funds.
Ready to go unseen?
Get early access to the first venue, and read exactly what it hides and what it can't.
Non-custodial · Keys never leave your device · Independent audit before launch