Skip to content
All library documents

Deploying and Settling Template-Based Outcome Markets

Article Hyperliquid docs
Read the original

Summary

This documentation explains how authorized deployers create and manage template-based outcome markets on Hyperliquid. Validators approve templates that define market wording, side names, and typed keywords; deployers instantiate those templates with validated values. The guide covers activation, standalone YES/NO outcomes, multi-outcome questions, adding outcomes later, and the rules for settling outcomes and questions. Deployments have no gas charge, but deployers face active-market and daily limits.

It also details fee scaling: the selected scale determines the user’s fee relative to the base outcome trading rate and how the fee is divided between deployer and protocol. Other operational constraints include staking duration, permanent deactivation, restrictions on settlement fractions, and permissions for sub-deployers. The text is a protocol reference rather than a trading strategy or performance analysis. It describes mechanics and limits, but gives no evidence about market quality, liquidity, pricing efficiency, or profitability; those require separate assessment.

Key ideas

  • Outcome markets must be instantiated from validator-approved templates with typed keyword values.
  • Deployers can create standalone outcomes or questions, with limits on active outcomes and daily deployments.
  • The fee scale sets user fees and divides the fee between deployer and protocol.
  • Question outcomes have specific association and sequential settlement rules, including an automatically settled fallback.
  • Activation, deactivation, and delegated actions are constrained by staking, permanence, and permission rules.

Tags

CryptoExecutionRisk management

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.