Launch settings
Campaign terms, backing multipliers, direct awards, and the timing rules that govern support and exits.
A campaign has its own backing price, limits, dates, and withdrawal timing. The tables show protocol limits and constructor defaults. Use your campaign's recorded terms for its actual backing amounts and deadlines.
Campaign settings
| Setting | Allowed value | When it can change |
|---|---|---|
| Collection and NFT range | One ERC-721 collection; 1–10,000 sequential token IDs | Fixed at creation |
| Base backing price | At least the manager minimum; 0.025 ETH minimum by default | Fixed for the campaign |
| Maximum positions per wallet | 1 through the campaign’s total position count | Fixed at registration |
| Support start and deadline | Future start at creation; deadline later than start | Artist may apply an approved reschedule before the current start and before any support |
| Maximum backing multiplier | 5× default; artist may choose 1×–10× in whole numbers | Until full funding; changes affect future support only |
| Direct-award percentage | 10% default; 10%–50% in whole percentages | Artist may change it until NFT escrow completes |
| Supporter eligibility rule | Optional; open support by default | Artist may replace or clear it for future support |
The manager owner approves the campaign's fixed configuration before the artist creates it. The artist separately controls its multiplier maximum, direct-award percentage, and optional eligibility rule. Setting the wallet cap equal to the total position count removes that practical limit; a per-address cap does not identify unique people.
Each support transaction fixes its positions' backing amounts. Each position gets one reward share once the campaign is fully funded, regardless of multiplier. The direct-award count rounds down to a whole number of NFTs.
Manager defaults and timing
| Policy | Constructor default | How it applies |
|---|---|---|
| Minimum base backing | 0.025 ETH | Owner-set floor, never below 0.025 ETH; also checked at final campaign funding |
| Active-listing withdrawal delay | 1 day + 12 hours per multiplier above 1× | Snapshotted at campaign creation; each position’s clock starts when submitted to the pool |
| Launch submission period | 30 days | Snapshotted at full funding; includes requesting randomness, fulfillment, and processing |
| Manager intake | Starts disabled | Owner controls new campaign creation, NFT deposits, and support |
The withdrawal base must be positive, and the delay at the maximum 10× tier cannot exceed 365 days. A later timing change affects subsequently created campaigns. A later submission-period change affects campaigns funded afterward; neither change rewrites an existing snapshot. A zero submission period makes newly funded campaigns immediately eligible for unwind.
Disabling manager intake leaves already funded launch processing, settlement, recovery, and claims available. Main-pool rules still apply: listing needs pool intake and sufficient backing, and voluntary withdrawal needs an Active listing and an available exit window.
Launch exemptions
Recognized campaign listings bypass the floor-price cap and price-drift removal, and pay zero owner settlement fee when purchasers keep or relist their NFTs. These exemptions remain attached to those listings. An ordinary listing from the same collection does not inherit them.
The pool can separately exempt an entire collection from oracle checks. That live setting does not grant the launch settlement-fee exemption. Purchaser cashout rates are also main-pool settings: ETH payouts and FWA purchase budgets use independent rates at settlement, rather than terms fixed by the campaign manager.
The 1% withdrawal fee during a listing's current crown tenure's first twelve hours still applies. See claims and recovery for timing and where funds go for the resulting amounts.