Worst case, defined first

Preview the cage.
Not the key.

This scaffold hashes the limits a future separate Privy wallet would enforce. It cannot create a wallet, authorize a signer, fund an address, or send a transaction.

Sleep auto-ape readiness

Vault cannot auto-send while you sleep yet.

Missing piece for delegated Vault signing: the server authorization key is not configured. Until that lands and execution flips on, use the live Gate with your own wallet.

Back to live Gate →Operator sets PRIVY_AUTHORIZATION_PRIVATE_KEY on the Worker

Privy server SDKWired

Browser app IDConfigured

Server app IDConfigured

App IDs matchSame app

App secretConfigured

Privy server clientReady

Authorization keyAdd PKCS8 key

External security reviewNot complete

Execution flagHard off

Drop-in credential map

NEXT_PUBLIC_PRIVY_APP_ID

PRIVY_APP_ID

PRIVY_APP_SECRET

PRIVY_AUTHORIZATION_PRIVATE_KEY

Copy the same dashboard App ID into both ID fields. Keep the secret and base64 PKCS8 authorization key server-side.

Credentials alone never unlock automation. The transaction firewall, policy signer, mainnet canaries, revoke test, and external security review are all hard prerequisites.

Privy policy draft

Caps the signer cannot loosen.

HYPOTHETICAL

Owner walletOnly withdrawal destination

Per-trade capSOLDaily spend capSOLOpen positionsProfit sweep%

Allowed programs

Pump curveFresh bonding-curve ordersPumpSwapGraduated pool exitsJupiter fallbackFallback routing only

Withdraw home only

The owner wallet above is copied into the immutable withdrawal destination. No alternate address is accepted.

Valid inputs produce a local policy hash only.