Tokens and locked supply
Launchpad locks launch supply in a dedicated vault. The token type depends on the network.
On Base, the launch token is an ERC-20. The factory reads the creator's token balance, deploys a vault, and pulls that balance in. USDC on Base is the quote.
On Stellar, the launch token is a Stellar asset, identified by an asset code and issuer account, such as a project code paired with its issuer's G... address. A code by itself does not identify an asset. XLM is Stellar's native asset and has no issuer. The Stellar Asset Contract lets Soroban contracts hold and transfer both native and issued Stellar assets. Its C... address is a contract interface to the same underlying asset.
Intended issuance flow
The complete launch flow is designed to:
Create the token. On Base, deploy or reuse an ERC-20. On Stellar, create the issuer and distribution arrangement.
Issue the configured supply to the distribution account or creator wallet.
Establish and publish the token's administrative controls.
On Stellar, deploy or locate its SAC on the selected network. On Base, confirm the ERC-20 address and decimals.
Transfer the launch supply from the distribution account into the dedicated vault.
Current factoryThe Stellar factory begins at this step. It does not create an issuer, issue an asset, or disable future issuance. The Base factory likewise expects an existing ERC-20 and an approval for the deposited balance.
What the vault receives
The factory reads the launch owner's full token balance, creates a new vault, transfers that balance, and verifies that the owner's balance became zero. The vault records the amount deposited as its launch supply.
That transfer cannot prove that other accounts hold no tokens or that the issuer or admin cannot mint more. A fixed-supply claim needs separate evidence about issuance, distribution, and remaining administrative authority.
What is locked
The vault accounts for the pool reserve, sale inventory, and team allocation. These buckets have different permitted uses. Team tokens follow vesting; curve inventory is distributed through trades; pool tokens are reserved for future settlement.
A contract lock does not neutralize token-level admin powers. On Stellar, authorization and clawback settings can affect balances held in a vault. On Base, review mint, pause, and blacklist controls on the ERC-20. Review those controls as well as contract code.
Network setup and precision
On Base, approve the factory (or the sale contract) to spend the launch token, and hold USDC plus ETH for gas.
On Stellar, classic accounts need the required trustlines for issued assets they receive. XLM does not need a trustline. These launch contracts do not create trustlines for users. The current Stellar factory accepts only host-verified Stellar Asset Contracts with seven decimals for both the project asset and quote asset. A custom contract implementing a similar token interface is rejected.