Proviso/Accounts & routes
Account not linkedConnect account
WORKSPACE / 06 / ACCOUNTS & ROUTES

Your accounts. Connected by intent.

One ownership model, distinct execution permissions, and funding routes you control.

Ownership stays with you.

The design keeps trading funds in your own venue accounts. Proviso’s access is limited to approved trading and swap permissions, with revocation in your hands.

No account connected
01 / HYPERLIQUID
HL

Trading account

Perpetuals + spot

Disconnected
Key type
Per-user trade-only agent
Main key
Never held by Proviso
Exit orders
Reduce-only
Price boundary
Within 2% of mark
Agent lifecycle
Versioned name + expiry
Orders and stopsNo withdrawal authority

Hyperliquid agent keys are not natively scoped to a thesis. Proviso’s enclave policy must enforce those limits. Empty-account re-funding requires a fresh key.

02 / ROBINHOOD CHAIN
RH

Commitments & swaps

On-chain records + Stock Token routes

Disconnected
Key type
Signed swap-key policy
Allowed target
ProvisoSwapAdapter only
Approval
Exact amount, same user operation
Pool access
User-signed allow-list
Caps
Per-transaction, per-day, expiry
Allow-listed swapsNo transfers or Permit2

The adapter design checks oracle freshness, slippage bounds, fixed pool keys, and audited hooks. Integration assumptions require verification before launch.

Between accounts, an explicit route.

Prepare a direction and amount. A real quote must disclose fees, timing, and refund behavior.

FUNDING ROUTE PLANNER
ROBINHOOD CHAINUSDG
PUBLIC RELAYER
HYPERLIQUIDUSDC
Expected receivedQuote required

Failed routes are designed to refund to the source account. No transfer is initiated here.

Revoke from the source.

Live permissions must remain revocable from the user’s account. The application should show key version, expiry, approval status, and rotation requirements once connected.

Security model