A Cardano launchpad runs token sales for new Cardano projects, but it cannot reuse an Ethereum sale contract. Cardano's ledger works on an extended UTXO (eUTXO) model, and Cardano tokens need no token contract. This guide explains how a Cardano IDO is built around those two facts, which tools teams use in 2026, and what a build costs in time.
What is different about Cardano
Native tokens instead of token contracts
On Cardano, each fungible token is defined by a minting policy, a script that decides when tokens can be minted or burned. After minting, tokens move like ADA in ordinary transactions, with no contract call.
A Cardano token has no transfer function, so an attacker cannot exploit one, but the same design also removes features that an ERC-20 contract can hold, such as transfer fees or blacklists. To fix the supply, the project uses a minting policy with a time lock that expires after the first mint.
Validators instead of contract accounts
Cardano smart contracts are validators: scripts that approve or reject the spending of a UTXO locked at their address. A validator reads the UTXO's datum, which holds state, and the redeemer, which names the action.
The app builds each transaction off-chain and selects the inputs, and the chain only checks that the finished transaction is valid. Since the Chang hard fork in 2024, Cardano runs Plutus V3 scripts. Teams write most new validators in Aiken, and Plutus (Haskell), Helios and OpShin are alternatives. The Cardano developer portal lists the current toolchain.
Concurrency
Each UTXO can be spent by only one transaction. If a sale keeps one "total raised" UTXO, only one buyer can update it per block, and the other buyers' transactions fail. Cardano DEXs such as Minswap and SundaeSwap met the same problem and solved it with orders and batchers, a pattern Cardano launchpads also use.
A batcher-based Cardano IDO design
- Contribution orders. Each buyer locks ADA or a stablecoin at an order script. The order's datum records the buyer's address, the amount and an allocation proof. Every order is a separate UTXO, so many buyers can place orders in the same block.
- Batching. An off-chain batcher collects the orders and submits transactions that spend several orders at once, update the sale state and check the caps.
- Allocation and refunds. In an overflow sale, buyers may commit more than the sale offers, and each allocation is scaled down. The batcher or a settlement step computes each pro rata allocation and returns the excess funds.
- Distribution. The tokens go to buyers directly or into a vesting UTXO for each buyer. Each vesting UTXO unlocks after a set time, which the validator checks against the transaction's validity interval.
- Liquidity. Part of the ADA raised in the sale and part of the project's tokens seed a pool on a Cardano DEX, and the LP tokens are locked at a script with a time lock.
The batcher must not be able to steal or redirect funds. Each order validator should allow only two outcomes: the buyer's allocation or a refund, paid to the address in the datum, and buyers should be able to cancel their own orders if the batcher stops.
Liquidity bootstrapping events
Minswap offers a liquidity bootstrapping event (LBE) as an alternative to a fixed-price Cardano IDO, in which the token starts with no liquidity and no set price. Buyers deposit ADA during the event, and the price of the new token rises as more ADA comes in. When the event ends, the deposited ADA and the project's tokens form a Minswap pool, and participants and the project each receive a share of that pool's LP tokens.
Other Cardano-specific details
- Minimum ADA per UTXO. Every output that carries tokens must also hold a minimum amount of ADA, set by a protocol parameter. Vesting outputs and small refunds must include that ADA, or the transaction fails.
- Time. Validators cannot read a clock and check the transaction's validity range instead, so sale windows and vesting dates are written as time ranges.
- Reference scripts and inputs. A team publishes each script once on-chain and references it from later transactions, which cuts fees and transaction size.
- Wallet connection. Browser wallets such as Lace, Eternl, Yoroi and VESPR expose the CIP-30 API for signing, and off-chain libraries such as Mesh and Lucid Evolution build the transactions.
- Chain data. Indexers such as Blockfrost, or Kupo with Ogmios, answer chain queries for the app.
- Token metadata. The project registers the token's name, ticker and decimals with the CIP-68 on-chain standard or the off-chain token registry, so wallets and DEXs display the token correctly.
ISPOs: a Cardano-native alternative
In an initial stake pool offering (ISPO), ADA holders delegate their stake to a project's stake pool. The delegators give up their staking rewards to the project and receive project tokens in return, without ever locking or sending their ADA. An ISPO still raises value in exchange for tokens, so it needs the same legal review as a sale, and the project must also run its stake pools reliably for the whole offering.
Security and auditing
eUTXO bugs differ from EVM bugs. Common Cardano issues include:
- Double satisfaction, where two validators each check that a payment exists and one payment can pass both checks, so an attacker pays once and takes funds twice.
- Missing checks that an output goes to the correct address with the correct datum.
- Datums without a size limit, where an attacker adds data until the transaction that spends the UTXO is too large to submit, and the funds stay locked permanently.
- Minting policies that an attacker can reuse in a later transaction to mint extra tokens.
Auditors need specific Cardano experience, and general EVM audit experience does not cover these issues.
Cardano launchpad build effort and cost drivers
As a reasoned estimate, a Cardano launchpad with an order-and-batcher sale, vesting and a web app takes four to six months for three or four engineers with Cardano experience, plus a specialist audit. Cardano has fewer reusable open-source sale components than EVM chains, and experienced Cardano engineers are harder to hire, so both factors raise the cost.
The Ethereum launchpad guide shows the EVM approach for comparison, and the Cardano NFT marketplace guide covers similar UTXO design problems. The crypto launchpad development guide covers sale formats and project vetting.
Frequently asked questions
Do I need a smart contract to create a Cardano token?
No. A minting policy creates the token, and the policy can be a simple native script, while validators are needed for the sale, vesting and liquidity logic.
Why does a Cardano IDO use batchers?
A shared state UTXO can be spent only once per block, so parallel buyers would collide. Separate order UTXOs and a batcher let many buyers join at the same time.
Which language should a Cardano launchpad use for validators?
Aiken is a common choice for new projects and is actively maintained, while Plutus suits teams that already write Haskell.
Is an ISPO safer legally than a token sale?
Not necessarily. Regulators look at the economic substance, and ISPO participants give up staking rewards in exchange for tokens, which is still a form of payment.