FWAIR Launch

FWAIR Launch lets an artist bring a contiguous range of NFTs into the main FWA pool without supplying the ETH backing. The artist supplies the NFTs; supporters supply one fixed backing amount for each NFT. That ETH backs the future FWA position—it is not an upfront sale payment to the artist.

One manager, one contract per collection campaign

The deployed

 is the canonical deployer and registry. The manager owner first approves one exact campaign configuration. The artist then creates a byte-for-byte verified FWAIRLaunch child contract for that campaign. There is no proxy, shared implementation, or contract per NFT.

Every campaign fixes the artist, ERC-721 collection, contiguous token-ID range, NFT count, backing per NFT, per-wallet cap, support start, and support deadline. The token count may be from 1 through 10,000. The backing and wallet cap do not change after creation; a schedule change requires a new exact manager approval and must happen before support starts.

1. The artist escrows the collection

The artist approves the campaign contract to move the declared NFTs. Permissionless depositNext(count) calls then transfer the next sequential token IDs in bounded batches. Every NFT must still belong to the artist, and the entire range must be in campaign custody before the collection is reserved and the campaign enters Supporting. Creating an empty campaign never reserves a collection.

2. Supporters back sequential NFTs

During the support window, a wallet calls support(count) with exactly count × backingPrice ETH. Positions are assigned from the next unbacked token ID in order; supporters cannot choose a token. A transaction mined first gets the earlier position, so confirmed PositionSupported events are the final assignment record.

• Each campaign has its own per-wallet maximum. It limits one address, not one person, and is not Sybil resistance.
• An optional purchase-operator contract may apply an additional wallet policy. The website checks that policy through its server API before showing a wallet as allowed to back.
• Support is locked while the campaign is open. A supporter cannot cancel an individual position; the ETH becomes claimable only after a campaign or FWA outcome assigns it.

3. Full backing activates the collection

The final support transaction atomically activates and whitelists the collection, fixes one lifetime FWA reward share per backed NFT, enters Launching, and snapshots the campaign's launch-submission deadline. Anyone may then call launchNext(count) in bounded batches. Each call pairs one escrowed NFT with its supporter's ETH and creates a normal listing in the main FWA pool.

Complete means every campaign NFT was submitted to FWA. It does not mean every FWA listing has been allocated or every earning and claim has settled.

What supporters and artists receive

The campaign contract is the onchain FWA depositor for every launched position. It separates supporter principal and NFT entitlements from artist earnings. Active-listing fees and aggregate fee or crown credits accrue to the artist; harvested FWA depositor reward tokens are divided by the fixed supporter-share count. FWAIR adds no fee. An ETH settlement can still reflect FWA's existing settlement fee.

Failure and partial-launch recovery

Before full backing, the artist may cancel, anyone may expire the campaign after its deadline, and the manager owner may emergency-fail it. Bounded finalization credits full backing refunds to supporters and makes escrowed NFTs claimable by the artist. The collection is not activated.

Full backing does not skip the submission phase. If the complete range is not submitted before the snapshotted deadline, anyone may move the campaign to Unwinding. The already-launched prefix stays in FWA. Each position in the unlaunched suffix returns full backing to its supporter and its NFT to the artist.

Claims are pull-based

Outcomes accrue onchain first; they are not automatically pushed to a wallet. A supporter separately claims ETH, FWA reward tokens, and each NFT entitlement. The artist separately claims artist ETH earnings. Anyone may perform the bounded synchronization, harvesting, failure-finalization, and unwind work that makes those balances current, but only the recorded beneficiary can claim an asset.

Current mainnet controls

These are live manager settings and may change. Read them again before a transaction. Campaign-specific backing, wallet caps, dates, progress, and claims are shown on the drops pages. See Deployments for the complete active contract table.