Skip to main content
In version 1, launching creates the canonical Tulip market for one exact Hugging Face model revision. Tulip first commits the creator-bound launch, then reveals it after one block. The reveal atomically performs model registration, credit deployment, pool initialization, liquidity creation, and permanent locking.
Version 1 accepts Hugging Face model identities. Future protocol versions may introduce additional identity namespaces, but a launch must always represent a real pinned model rather than a generic project token.
A launch is permanent. The credit supply cannot be increased, the canonical pool cannot be replaced, and the locked principal cannot be withdrawn.

​
Launching before service

You do not need an active inference provider to launch a market. The market can trade while the model is unserved, allowing demand to form before a provider takes on the cost and operational work of deploying an endpoint. Make the model identity and metadata complete enough for providers to evaluate the opportunity. Trading activity does not guarantee that a provider will enter, and inference remains unavailable until an eligible offer becomes active.

​
Prepare the model identity

Collect:
  • Version 1 Hugging Face repository in owner/repository form.
  • Exact 40-character commit SHA.
  • Supported inference task.
  • Credit name and symbol.
  • Metadata commitment.
Verify that the repository license permits your intended use. Tulip registration does not grant model rights.

​
Choose market economics

You select:
  • An enabled curve preset.
  • The initial native LP fee within current factory bounds.
  • The model creator’s inference settlement share.
The launch supply, starting price, terminal range, tick spacing, and LP fee distribution are defined by the selected preset. The launcher supplies no USDG. Launch a model market Import a pinned Hugging Face revision and review its credit identity before launch.

​
Launch

1

Review the preview

In Tulip, open Launch a market, choose the model identity and production preset, then review token ordering, tick bounds, starting price, supply, and fee distribution.
2

Protect the launch

Confirm the commitment transaction. It binds the hidden launch salt and full market configuration to your creator wallet so another account cannot copy the pending launch and capture its rights.
3

Reveal the atomic launch

After the commitment is confirmed in a prior block, confirm the reveal transaction before the displayed deadline. Tulip reports any duplicate ModelID, expired commitment, disabled preset, or out-of-bounds fee.
4

Verify the records

Open the completed transaction in Blockscout and confirm the ModelLaunched, MarketLaunched, PositionLocked, CanonicalMarketBound, and active listing events.
5

Configure the market

Publish complete metadata and decide whether you will operate a provider or let independent providers enter first.

​
After launch

The market creator may:
  • Update the model metadata commitment.
  • Schedule a pool LP-fee change within current protocol bounds; activation requires the one-hour safety delay.
  • Collect its configured share when anyone calls fee collection on the locker.
  • Register a provider offer like any other operator.
The creator cannot withdraw the locked liquidity, mint more credits, prevent provider entry, or change another provider’s tariff.