Skip to main content
Permissionless Listing allows Builders to bring additional isolated-margin perpetual markets to Orderly without following the standard manual listing path. The goal is to expand market coverage while applying a stricter risk model to those markets than to the standard Orderly market set.

For Builders: What You Need Before Listing

Permissionless Listing is for Builders who want to offer additional perpetual markets to their users. If you list a market this way, you take responsibility for how that market is supported, presented, and risk-managed in your Builder experience. Before you can take a market live through Permissionless Listing, you should be in the same ready-to-launch state expected of any Builder on Orderly:
  • Complete the standard Builder onboarding flow so your Builder profile, admin account, and operating setup are in place.
  • Make sure you understand the Builder economics and operational responsibilities described in Builders and the Builder Staking Program.
  • Be ready to support the market you list with dedicated risk controls and liquidity.

Listing Requirements and Responsibilities

Before listing a market, Builders must understand the following conditions:
  • Builder readiness: Permissionless Listing is for Builders that are already set up to operate on Orderly.
  • Liquidity management: Builders are responsible for supporting the markets they list with sufficient liquidity and a stable market-making setup.
  • Risk ownership: A listed market requires the Builder to be ready for market-specific risk handling and user communication.
  • Stricter risk model: Permissionless Listing markets are isolated-margin perpetual futures and should be treated with tighter market-specific controls than the standard market set.
In practice, completing a listing means the Builder is ready to support that market responsibly: the Builder account is already set up, the market has liquidity support in place, and the Builder is prepared to explain any market-specific handling on the frontend.

Frontend Display and User Communication

When a Builder lists a market permissionlessly, the frontend should make it clear that the market is not part of the standard default market set.
  • Frontend-specific visibility: Availability can vary by frontend, because frontends can choose which supported markets to surface.
  • Distinct presentation: Trading surfaces should distinguish these markets from the standard market set in a way that is clear to users.
  • Builder context: Traders should be able to tell that the market is being surfaced through a specific Builder experience rather than as part of the default market list.

Trading and Risk Considerations

After a permissionlessly listed market goes live, Builders should make the market’s handling clear to users:
FeatureRestriction
Margin modePermissionlessly listed markets are Isolated Margin only perpetual futures. Standard Orderly markets can generally support both Cross Margin and Isolated Margin.
Market handlingBuilders should expect tighter market-specific controls than on the standard market set.
Liquidity supportMarket quality depends on the Builder’s liquidity and market-making support.
User communicationAny market-specific trading constraints, warnings, or display differences should be made clear on the frontend before users trade.
For traders, the key point is that these markets may not behave exactly like the standard Orderly market set. Standard Orderly markets can generally support both Cross Margin and Isolated Margin, but permissionlessly listed markets are an Isolated Margin-only exception. Before trading, users should rely on the frontend’s market-specific information, disclosures, and trading controls.