Trust model
LaunchLab combines onchain custody and accounting with offchain market data and user-signed trade instructions.
| Component | Current responsibility | Trust requirement |
|---|---|---|
| Root wallet | Controls the smart account | User protects the root authority |
| Session key | Places allowed bets | Policy must keep its scope narrow |
| Trade relayer | Selects valid fills and submits allowed action batches | Relayer and quote service must be correct |
| Result signer | Chooses the settlement outcome | Signer must report the correct result |
| Vault | Holds USDG, shares gains and losses, reserves claims | Contract code and accounting must be correct |
| Administrator | Configures and upgrades the vault | Role must be secured and governed |
| Guardian | Can pause selected operation | Role must be available during an incident |
Onchain checks
The contract checks user trade signatures and nonce use, applies stake and payout limits, limits fills to the configured executor, reserves accepted liabilities, enforces session call scope, and accounts for settlement and withdrawals.
Offchain or trusted facts
Market history, live price ingestion, quote generation, and result selection happen outside the vault. The contract does not currently verify the final price or store a price proof with the result.
There is no onchain maximum result delay. If the result signer stops, settlement and locked funds can wait until an authorized action resolves the bet.
Operational safeguards
Before you commit funds, verify that the active release publishes its contract source and addresses, role governance, signer monitoring, incident procedures, recovery tools, and fee and cancellation policy.