# Lans Docs | One token. Many markets. A guide to launching one token across multiple markets, and understanding the rules behind each market. ## What is Lans? One launch can give several asset communities a market for the same token. Lans is a multi-market launchpad designed for **Zero, the LayerZero blockchain**. A creator launches one token into one to five markets, with a different quote asset in each market. A project can give its intended communities a market in an asset they use. Buyers choose an accepted local asset on Zero, while every market trades the same launched token. One token page brings together the markets, reserves, activity and launch record. For creators, start with [choosing the markets](#one-token-multiple-markets) and [preparing a launch](#preparing-a-launch). For buyers and sellers, read [buying and selling](#buying-and-selling) alongside [liquidity and reserves](#liquidity-and-reserves). **The product model and MVP scope are defined.** Contract design, fees, supply limits and the approved quote list remain to be finalized before launch. ## One token, multiple markets Choose markets for the people and assets the launch is intended to serve. A **quote asset** is the asset spent to buy a token, or received when selling it. In `X/Q1`, X is the launched token and Q1 is the quote. Choosing Q1, Q2 and Q3 creates `X/Q1`, `X/Q2` and `X/Q3`. Each market has its own reserves. All three trade the same X token. **One token, separate markets** - Token X has one global supply. - X / Q1 holds its current X inventory and its own Q1 quote reserve. - X / Q2 holds its current X inventory and its own Q2 quote reserve. - X / Q3 holds its current X inventory and its own Q3 quote reserve. The same X token trades against each selected quote. Each market holds its own reserves. Q1, Q2 and Q3 are examples, not an approved asset list. ### Why more than one market? A buyer holding accepted local Q2 can use X/Q2 rather than first exchanging that quote for Q1. A buyer holding local Q1 can use X/Q1. Both receive X. The **basket** is the creator’s selection of these markets. Additional markets are useful when they give an intended community a practical way to trade. Inclusion of a quote does not imply endorsement by its issuer or community. ### Choosing the markets One market is a valid launch. In the MVP, additional markets divide the same launch inventory into equal starting allocations. Market count alone does not create quote liquidity or buyer demand. - Identify which communities are expected to use each quote. - Check that the quote has an eligible [local representation on Zero](#omnichain-on-zero). - Review what the equal split assigns to each selected market. Lans uses a limited list of verified quotes. Eligibility must account for backing, a current price source, liquidity and transfer risks. The asset list and freshness thresholds remain to be specified. ## Supply and allocation Separate the global token supply from its starting market allocations. **Global supply** is the total number of X tokens. **Launch inventory** is the portion assigned to the launch markets. Creating another market divides that inventory; it does not issue another copy of the supply. For illustration, allocating 900,000 tokens across three markets gives each market 300,000 tokens. These numbers explain the split; they do not set Lans supply parameters. **Illustrative allocation** - One market receives all launch inventory. - With N markets, each receives exactly 1/N of the inventory. - For example, three markets each receive 1/3, approximately 33.33%. This is an allocation example, not a price or liquidity simulation. Displayed percentages are rounded. The equal split describes the starting allocation. Once trading begins, the X actually held in each market changes as buyers receive tokens and sellers return them. ### Opening prices across different quotes The virtual reserve is split equally by economic value, then converted into each quote’s units. The opening-price rule aims to align prices when measured in the same currency. Equal allocation does not guarantee equal trading depth or lasting price parity. Real balances, quote prices and trading activity can change each market differently. Supply limits, rounding and the pricing formula still need specification. See [liquidity and reserves](#liquidity-and-reserves) for the distinction between balances and pricing inputs. ## Preparing a launch Review the token and every selected market as one launch. The creator provides the project name, ticker, description, image and public links, then selects one to five eligible quotes. ### Before signing The preview is where the creator checks the configuration for the whole launch: - The token supply and inventory assigned to every market. - Each market’s quote, opening price and relevant addresses. - All launch fees and their recipients. - The initial liquidity positions and their lock rules. - Any creator purchase: its amount, beneficiary and allocation across markets. **From configuration to launch** - Configure: provide the token identity and select eligible quotes. - Review: check supply, fees and any creator buy. - Local launch: create the token and its markets on Zero. - Launch record: publish addresses, allocations and control rights. One configuration ties together the token, its market allocations and the initial liquidity positions. The intended launch operation creates the token and local markets, distributes inventory and locks the initial positions. The token page brings together the resulting addresses, market activity and launch record. ### Launch modes **Natural launch** is the default. There is no creator buy or coordinated team-wallet purchase. All selected markets open to the public at the same time. **Transparent creator buy** allows a disclosed initial purchase by the creator or treasury. The amount, beneficiary wallet and distribution across markets appear before launch. Analytics identify this purchase separately from public buying. ## Buying and selling The selected market determines the quote paid or received and the balances used for the trade. A buyer spends a market’s accepted local quote to receive X. A seller exchanges X for that market’s quote. The result depends on the selected market, trade size, real balances and fee rules. ### A launch, then a trade - **The creator** selects Q1, Q2 and Q3 for the communities the project wants to reach. The launch splits one inventory across those markets. - **The buyer** holds accepted local Q2 on Zero, reviews X/Q2 and spends Q2 to receive X. - **The seller** later compares supported X markets. Selling into X/Q1 means reviewing the expected Q1 output and that market’s actual Q1 reserve. Buying earlier with Q2 does not set the terms of this later sale. Q1, Q2 and Q3 are illustrative quotes. This example does not establish an approved asset, a transfer route or a profitable round trip. ### Reviewing a trade - The selected market, payment asset and local token addresses. - The estimated output, applicable fees and price impact for the order size. - The market’s actual token inventory and real quote balance. A reference price alone is not an execution quote. Limits on the received amount and confirmation behavior remain to be specified. ### Prices and routing Markets can trade at different prices. Arbitrage can narrow differences as traders buy in one market and sell in another; it does not guarantee matching prices. The MVP includes a **router**, a common way to submit buys and sells to supported markets. Automatic market selection by price and depth is a later extension. ## Liquidity and reserves Read the assets currently held by a market separately from its pricing inputs. A market’s token inventory, real quote reserve and virtual reserve answer different questions. **What a market actually holds** - Token inventory: launched tokens currently held by this market. - Real quote reserve: quote assets actually held in this market. - Virtual reserve: an input used by the pricing formula, not an asset held in the market. A virtual reserve adds no spendable assets. Another market’s quote balance is not part of this market’s reserves. **Token inventory** is the X actually held by a market. Its starting balance comes from the launch allocation; buys and sells change it. The **real quote reserve** is the quote asset actually held there. A **virtual reserve** is a number used in the pricing formula, not a deposit of quote assets. It can affect the quoted price but cannot pay a seller. Adding it to real balances would overstate available funds. ### Depth and withdrawals Trading depth describes how much can be exchanged before the price moves substantially. Review it market by market: another market’s quote balance is not part of the selected market’s reserve. A combined liquidity figure can hide a shallow pair. The design requires initial liquidity positions to be locked. A lock concerns withdrawal of the position; the market’s tradable balances still change through buys and sells. The lock mechanism, duration, withdrawal rights and recovery conditions remain open. A lock does not guarantee token value or a buyer for every sale. ## Omnichain on Zero Why Zero and LayerZero fit the separation between asset origin and local trading. The MVP places the token and its markets on **Zero**. A quote may originate in another ecosystem, while the version accepted by a Lans market is held and traded locally on Zero. ### Why we chose this foundation Lans needs to connect communities that use different assets. We chose the Zero and LayerZero ecosystem because it fits this design: asset origins can differ while the first version keeps trading in one place. - **Cross-chain messaging.** LayerZero gives applications a way to exchange messages across supported chains. This is a building block for coordinating transfers and later cross-chain operations. - **Token-transfer standards.** Standards such as OFT (Omnichain Fungible Token) define how compatible assets can move through coordinated debit and credit operations. - **Local markets first.** Keeping the MVP markets on Zero gives each swap one local execution context. Asset transfers and their verification are handled separately from that swap. **From asset origin to a local market** - Quote Q1 from Ecosystem A needs a verified local Q1 representation on Zero before use in X / Q1. - Quote Q2 from Ecosystem B needs a verified local Q2 representation on Zero before use in X / Q2. - Quote Q3 from Ecosystem C needs a verified local Q3 representation on Zero before use in X / Q3. Each quote needs verified backing and a supported route to Zero before local use. These example paths describe a prerequisite; they do not establish that a transfer route exists. Before local use, Lans must accept the representation and verify its backing and transfer route. Holding the original asset on another chain does not automatically make that balance spendable in a Zero market. LayerZero provides interoperability building blocks. Lans defines quote eligibility, market rules, liquidity requirements, pricing and recovery. Every asset integration still needs its own security and configuration checks. Markets using remote native reserves and asynchronous settlement belong to a later phase. Protocol references: [LayerZero architecture](https://docs.layerzero.network/v2/concepts/layerzero-protocol-architecture) and [OFT value transfers](https://docs.layerzero.network/v2/concepts/value-transfer-implementations). ## Fees and costs Understand the fee categories before comparing launch or trade costs. The defined revenue model has three parts: - A fixed fee to create a launch. - A protocol share of market trading fees. - An optional creator fee, fixed and public at launch. **Creators** need every launch charge and recipient before signing. **Traders** need the applicable fees alongside estimated output and price impact. A token’s reference price by itself is not the full cost of a trade. Exact amounts, recipient splits and collection rules remain undecided. Network costs depend on the eventual implementation; no rate or transaction-cost estimate is confirmed here. ## Transparency and control Know what the launch establishes and which powers remain to be specified. ### The launch record The token page must make the important terms verifiable: - Token and market addresses and the launch allocation. - The supply and token rules that become immutable after launch. - Initial liquidity positions and their actual lock terms. - Any creator buy, fee recipients and disclosed team-controlled allocations. Team-controlled holdings must be presented together even when spread across wallets. Creator purchases need a clear label. Holder concentration and creator activity help readers interpret a market beyond its volume. Independent sniper activity should be visible in analytics rather than automatically described as organic demand. ### Administration and recovery Upgrade, pause, fee-access and recovery permissions remain to be specified. Failure handling must cover unavailable quotes, incomplete operations and uncertain confirmation states. Before use, documentation of a deployed release will need the actual contracts, the powers of each role and the procedures for a failed operation. ## Product scope and next steps Keep the defined MVP, proposed experiences and later extensions separate. ### MVP scope - One token across one to five local markets on Zero, with verified quotes and equal starting allocations. - Natural launch and transparent creator buy, immutable token rules and locked initial liquidity positions. - A trading router and one token page with market data, holder concentration and creator activity. - Explicit failure states and recovery rules. ### Parameters still to specify These choices need an executable specification before the product can be used: - Supply limits, opening valuation and the pool or pricing formula. - Eligible quotes, price freshness, liquidity and transfer-risk rules. - Fee rates and splits, creator-buy limits and liquidity-lock terms. - Administrative powers, confirmation behavior and recovery procedures. ### Proposals to evaluate Ideas under discussion include comparing market configurations before launch, modeling economic scenarios, highlighting assets held in a connected wallet and providing community links with a market preselected. ### Later extensions Custom allocation weights, more asset adapters, launches across multiple chains, remote native reserves and automatic routing require further design. An external revenue engine and token buybacks would require repeatable, verified realized profit. They are optional and are not assumed to fund launchpad operations. No delivery dates have been set. ## Frequently asked questions Short answers to the main questions about the market model. ### Can I launch or trade through Lans now? This guide describes the product model. It does not establish a live launchpad or verified contracts. See [product scope and next steps](#product-scope-and-next-steps) for the choices still to specify. ### Must a creator choose all five markets? No. One market is valid. Additional markets split the same inventory into smaller starting allocations; they do not automatically create more quote liquidity or demand. See [choosing the markets](#one-token-multiple-markets). ### Does every market issue a different token? No. Every market trades the same X token with one global supply. ### Will the prices always match? No. The opening-price rule aims to align prices when measured in the same currency. Trading activity and quote prices can cause them to diverge. ### Can I pay directly from another chain? A market accepts its approved local quote representation on Zero. An asset held elsewhere needs a supported transfer route; connecting a wallet alone does not move it. ### Does a virtual reserve guarantee I can sell? No. It affects pricing without supplying real quote assets. A sale must be assessed using the selected market’s real balances and pricing rules. ## Glossary The terms used to distinguish token supply, market balances and trade execution. **Global supply** The total number of units of the launched token. **Launch inventory** The portion of supply assigned to the launch markets. **Token inventory** The launched tokens currently held by a market, beginning with its launch allocation and changing through trades. **Real quote reserve** The quote assets actually held by a market. **Virtual reserve** A pricing input, not deposited quote assets available to pay sellers. **Quote asset** The asset spent to buy the launched token or received when selling it. **Market** A pair between the token and a quote, with its own reserves. **Basket** The set of markets selected for a launch. **Router** The component used to submit buys or sells to supported markets. **Price impact** The change in a market’s price caused by a trade. **Slippage** The difference between a trade’s expected and executed result. **LP lock** A restriction on withdrawing a liquidity position. **Local representation** A token on Zero representing an asset from another network through a verified transfer arrangement. **Backing** The arrangement that links a local token to the asset it represents.