Proviso
Open workspace
05 / SELF-CUSTODY

Your accounts.
Limited keys.

The owner’s main key stays with the owner. Proviso’s permission model separates trading authority from ownership, with a different permission boundary for each venue.

THESIS TRADING / PROVISO
YOUMAIN KEY
HLTrade-onlyNo withdrawals
RHSwap-onlySigned policy
01 / WHAT ACCESS MEANS

Two permissions.
Distinct boundaries.

CAPABILITYHyperliquid agentRobinhood swap key
Place supported ordersAllowed, signer checksAllow-listed swaps only
Stops and targetsReduce-only exitsPolicy-specific swap flow
Withdraw / transferNot permittedNot permitted
Arbitrary routerNot applicableNot permitted
Token approvalsNo owner key accessExact amount to adapter only
Change allowed poolsNot applicableNew main-key signature
Key expiryVersioned agent with expiryPolicy expiry
RevokeOwner-controlledOwner-controlled
02 / TRUST BOUNDARIES

Keep the authority
where it belongs.

DEVICE

Owner control

Main key, canonicalization, random salts, signature, and encrypted recovery export.

ISOLATED SERVICES

Scoped execution

The evaluator decrypts rules inside an isolated enclave. The signer holds per-user agent keys and enforces confirmed limits.

ON-CHAIN POLICY

Explicit restrictions

The swap adapter constrains pools, approval amounts, output recipient, price bounds, freshness, caps, and expiry.

03 / LIFECYCLE & RESIDUAL RISK

A key has a life.
And a limit.

Rotate after re-funding.

The permission lifecycle calls for a fresh agent after an empty Hyperliquid account is re-funded. Unique names and versions prevent accidental reuse after agent pruning.

Fix the route.

A swap key can approve the exact input amount to ProvisoSwapAdapter and call it in the same user operation. No Universal Router, Permit2, unrestricted transfer, or arbitrary approval is intended.

Constrain the reference.

The swap design requires a fresh oracle reference, a price-banded minimum output, and fixed pool keys. Oracle multipliers must be applied once, with explicit per-feed handling.

Trade-only still carries risk.

A key unable to withdraw can still lose funds through trades. Signer controls, enclave claims, permission modules, and contracts all need implementation tests and review before being trusted.

Inspect the account model.

See connection requirements, permissions, key lifecycle, and funding-route behavior.

Accounts & routes