V2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.funV2 is now live at fwa.fun
MigrateDrops

Start here

  • How it works
  • Deployments

Main pool

  • Main pool overview
  • Positions & weighting
  • Pricing & allocation
  • Collections
  • NFT callbacks
  • Settlement
  • Sepolia deployment

Pool fees & rewards

  • Fees & protocol revenue
  • Crown reward

FWA token

  • $FWA overview
  • Earning & claiming
  • Buybacks & fee routing

FWAIR Launches

  • FWAIR overview
  • Backing a launch
  • Where funds go
  • Claims & recovery
  • Launch settings

Custom Pools

  • Custom pools overview
  • Standard pools
  • Buyback pools
  • Create & manage a pool
  • Pool settings & fees

Controls & safety

  • Exits & recovery
  • Roles & controls
  • Settings by product

Developers

  • Testing integrations
  • Deployment & integration

V1

  • V1 guide & settings
  • V1 contracts & testnet
DocumentationBacking a launch

Start here

  • How it works
  • Deployments

Main pool

  • Main pool overview
  • Positions & weighting
  • Pricing & allocation
  • Collections
  • NFT callbacks
  • Settlement
  • Sepolia deployment

Pool fees & rewards

  • Fees & protocol revenue
  • Crown reward

FWA token

  • $FWA overview
  • Earning & claiming
  • Buybacks & fee routing

FWAIR Launches

  • FWAIR overview
  • Backing a launch
  • Where funds go
  • Claims & recovery
  • Launch settings

Custom Pools

  • Custom pools overview
  • Standard pools
  • Buyback pools
  • Create & manage a pool
  • Pool settings & fees

Controls & safety

  • Exits & recovery
  • Roles & controls
  • Settings by product

Developers

  • Testing integrations
  • Deployment & integration

V1

  • V1 guide & settings
  • V1 contracts & testnet

Backing a launch

How base backing, whole-number multipliers, sequential position assignment, direct-award settings, and caller-funded randomness work.

Backing commits ETH to one or more NFT positions in a campaign. You choose a quantity and backing amount; the campaign assigns the next unsupported token IDs in sequence. An NFT becomes claimable only when an outcome awards it to you.

Support is recorded for the address calling the campaign. It cannot name a different beneficiary: that address holds the position's claim rights and, after full funding, its campaign reward share.

Choose a backing multiplier

Each campaign has a fixed base price. Your payment is quantity × base price × multiplier. Every position in one transaction uses the same whole-number multiplier; different multipliers require separate transactions.

For example, backing three positions at 2× with a 0.025 ETH base price costs 0.15 ETH. Each position carries 0.05 ETH of backing.

  • The maximum starts at 5×. The artist may choose a maximum from 1× through 10× before full funding, including while support is open.
  • A change affects future support only. Your positions keep their recorded backing and multiplier.
  • More backing funds a larger standing bid in the pool. Because pool selection weight is inverse to backing, a higher-backed position has less selection weight and may stay active longer.
  • More backing also lengthens the earliest voluntary exit. Under the default timing, 1× waits one day, 5× waits three days, and 10× waits five days and twelve hours after listing.

Higher backing does not buy extra direct-award chances or extra campaign reward shares. Each supported position contributes one share after the campaign becomes fully funded. Extra backing on one NFT cannot fill an unsupported position.

Direct-award chances

The artist sets a direct-award percentage from 10% through 50%, with a 10% default. It locks when NFT escrow completes, before support is available. The number of awards is floor(total positions × percentage / 100).

Rounding matters: nine positions at 10% produce zero direct awards; one hundred positions at 10% produce ten. Every position has the same initial chance of selection, regardless of its backing. The exact award count is reached if the entire campaign is processed; a campaign that stops at its processing deadline can finish with fewer awards.

Randomness is requested only after every position is backed. Anyone can pay for that request separately, and any excess payment returns to the payer. Supporter backing is not spent on randomness.

Before you back

Check the campaign's dates, wallet limit, eligibility rules, multiplier maximum, and withdrawal timing. An artist can change an optional eligibility rule for future support; the campaign still enforces its wallet limit and exact payment.

Individual support cannot be cancelled while the campaign remains open. Supporter refunds require a failed campaign, an unprocessed position at the processing deadline, a pool settlement that returns backing, or an eligible Active-listing refund. A direct award gives you the NFT and pays its backing to the artist.

See campaign settings for the controls and where funds go for each outcome.

Previous
FWAIR overview
Next
Where funds go
ByTokenWorks™
Operated by Token Workshop, Inc.Terms of Service

Explore

  • Home
  • Activity
  • Leaderboard

Protocol

  • $FWA
  • Deposit
  • Manage
  • Migrate

Fwair

  • Drops
  • Beta

Resources

  • V2 explained
  • Documentation
  • Changelog
  • X