HOOZ

Operations

The runbook: deploying the Sorter, launch day, environment variables, monitoring and manual interventions.

The runbook for whoever operates HOOZ.

Site environment

VariablePublicMeaning
NEXT_PUBLIC_PRIVY_APP_IDyesPrivy app id, wallet login only
NEXT_PUBLIC_X_URL, NEXT_PUBLIC_X_HANDLEyesthe X account in the header
NEXT_PUBLIC_HOOZ_SORTERyesSorter address; empty means Launch soon
NEXT_PUBLIC_WHOZ_TOKENyes$WHOZ address; empty means Launch soon
NEXT_PUBLIC_ROBINHOOD_RPCyesoptional RPC override
ONECLICK_JWTnoNEAR Intents partner key
RELAYER_URLnocourier URL for the fallback road

From empty to live

  1. Fund a deployer with ETH on Robinhood Chain.
  2. Deploy the Sorter and PonsMarket, verify on Blockscout.
  3. Set NEXT_PUBLIC_HOOZ_SORTER and redeploy. Deliveries still go straight to users until the token exists.
  4. Launch $WHOZ on Pons, then setToken and lockToken. See Token.
  5. Set NEXT_PUBLIC_WHOZ_TOKEN, redeploy. New orders now pay envelopes.
  6. Start the courier with HOOZ_SORTER so it sweeps envelopes as ETH lands.

Monitoring

  • The Ledger shows rail availability and Sorter totals.
  • The courier's GET /health returns the tick count and open orders.
  • Watch the courier's gas balance on both chains.

Manual interventions

SymptomAction
direct rail closed for hoursset RELAYER_URL so orders ride the fallback
envelope holds ETH, no sweepcall sweep(beneficiary, 0) from any wallet
Sorter pausedETH waits in envelopes; users can still withdraw
wrong token set before locksetToken again, then lockToken