FAQ
Who is Spawn for?
Spawn is for anyone who wants to participate in token markets without the structural disadvantages that plague most launchpads. That includes people spawning tokens who want a genuine shot at building a community, traders who want to participate without getting front-run by bots, and communities who want to form around shared conviction rather than shared extraction.
You don't need to be technically sophisticated to use Spawn. The gasless, approval-free trading experience is designed to be as accessible as a centralized exchange - while keeping the non-custodial properties that make crypto worth using.
Why does Spawn focus so much on fairness?
Because unfair market structure doesn't just hurt individuals - it degrades the quality of the market itself. When MEV bots and bundlers can reliably extract value from launches, prices stop reflecting real demand. Communities form around extracting each other rather than around actual conviction. The result is a race to the bottom where the launchpad becomes a coordination mechanism for sophisticated actors at the expense of everyone else.
Spawn's position is that this is fixable at the design level. Fairness isn't a social norm Spawn asks people to respect - it's a property of the execution engine.
How does Spawn prevent bundling and MEV?
Spawn's off-chain bonding curve engine removes the underlying condition these attacks depend on: a public mempool with reorderable transactions. MEV extraction requires being able to see pending transactions and insert your own before them. Bundling attacks require being able to coordinate multiple transactions in a block. Neither is possible in Spawn's off-chain execution environment - there's no mempool, no block ordering to manipulate, and no gas auction that can be won.
See Fairness as Architecture ->
What does "proof of demand" mean?
It means a token has to demonstrate real market conviction before it earns on-chain permanence. During the bonding curve phase, any token can be traded - but no ERC20 is deployed until the token reaches the graduation threshold. Tokens that don't attract sustained demand don't graduate. This keeps blockchains cleaner and makes on-chain presence a meaningful signal rather than a trivial formality.
See Proof of Demand, Then On-Chain ->
Why does Spawn emphasize chainless discovery?
Because the best token markets surface the best projects - and that only happens when discovery isn't artificially limited by which chain a project happened to launch on. Most launchpads today create fragmented discovery: a token's reach is determined by which chain's community happens to be paying attention. Spawn is designed to let projects compete on merit across ecosystems rather than competing within chain-specific silos.
Can I participate from any chain?
Spawn supports non-custodial deposits from all major chains - Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Smart Chain, Solana, Linea, Scroll, zkSync, Mode, Blast, Redstone, HyperEVM, and Plasma. The cross-chain transfer happens automatically in the background. Once your deposit lands on Base, your balance is available to trade immediately.
Can the graduation destination be different for each token?
Yes. When spawning a token, the spawner chooses whether it will graduate to Base or Ethereum - the two supported destination chains in Spawn v1. The spawner can also choose to let the community vote on the destination instead, in which case the vote runs during the bonding curve phase. More destination chains, including Solana and BNB Chain, are planned for future versions.
Is my money safe on Spawn?
Spawn uses a non-custodial vault architecture - your funds are held in an on-chain contract, not by Spawn. You can withdraw at any time by calling the vault contract directly. Spawn's operational status doesn't determine whether you can access your funds.
That said, all smart contract systems carry risk. Spawn's vault is designed and audited with security as a core requirement, but no on-chain system is risk-free.
Is this documentation technical?
These docs are intentionally conceptual and product-focused. They explain how Spawn works and why it's designed the way it is, without diving into implementation internals. For technical architecture details, refer to the internal engineering documentation.