Deployments
The current Ethereum mainnet deployment's verified contract addresses and launch metadata, with links to Etherscan.
These are the active Ethereum mainnet contracts used by the current app and protocol paths. Contract addresses are linked directly to Etherscan.
| Contract | Role | Address |
|---|---|---|
| FWA | Core NFT pool — accounting, positions, selection, and settlement | 0xB276F62DB0ce8CA2Ca5bc522695bE604521eAc1c |
| FWARewards | $FWA emissions, purchaser epochs, reward buys, and routing | 0x6a1a1C0CfB3D3C538e13D36d608a5bcaa992fc78 |
| FWAVRFService | Dedicated subscription coverage, request fees, and sponsored processing | 0xa084c33Fb7a467307452898b8D58165ebd2E5D9f |
| FWAToken | $FWA incentive token (ERC-20) | 0xa0Df17B5aC76ABaBA36E1450E2cbCd18A620C845 |
| FWATokenTransfer | Permit2 escrow rail for next-block wallet-to-wallet $FWA claims | 0xcE6d5B618e034f87C7a8B6dCa65FB8669b8c301B |
| FWAERC20Wrapper | Owner-curated ERC-20 denominations wrapped into FWA-compatible ERC-721 packs | 0x727C739F07A89f11E883FE0F34937c55e4c3d74A |
| FWAERC20PackRenderer | Onchain metadata and SVG renderer for ERC-20 pack NFTs | 0x69Cc9c633867eEE71b17142BBBc2c6aaf14c61a4 |
| FWATokenWrapper | Block-locked $FWA bearer packs represented as ERC-721 NFTs | 0x470879Abd61FdCA91436fE27ed87dB2c8650f3e7 |
| FWATokenHook | Uniswap v4 hook for the $FWA liquidity pool | 0x2C67ebA8A50AF0dB5Fba55F725247a75CbDA6444 |
| OwnerSplitter | Fixed 80/10/10 recipient for the hook's separate FWA trading fees | 0x7400824eec17F86Cc74385862810710F9c46Ec04 |
| FWAClaim | Merkle-gated v1 snapshot distribution | 0xd4085d38855F17EdF0B1CCBFad7B3846fb305655 |
| FWAWhitelistAuthority | Delegated collection curation, durable blocks, and reservation-scoped FWAIR activation | 0x54B641aC97A9e9375665934b8e7a7D0b2C0E898B |
| FWAIRLaunchManager | Canonical launch deployment, exact campaign approvals, collection reservations, and activation | 0x900252d9A8F9AcC3DD1014C594c91fC33e5A6AAf |
FWAIR deployments
The active FWAIRLaunchManager is the canonical registry
and deployer for new campaigns. Every collection campaign gets its own
byte-for-byte verified FWAIRLaunch child and single-use
VRF consumer, so child addresses are not hardcoded in the singleton table
above. Discover launches through the active manager's
launches(id) or
launchForCollection(collection) reads, or through the
live drops catalogue
.
The active manager was deployed at Ethereum block
25877942. The
deployment manifest records source revision
49837e82685cd9022529da83cf723606b597f4c6 alongside the
exact creation, runtime, and artifact hashes. Its immutable whitelist
authority is the FWAWhitelistAuthority shown in the table.
Numeric launch IDs are manager-scoped; links, caches, and integrations should use the launch contract address instead. See the
FWAIR Launches overview
for the campaign lifecycle and asset flows.
Legacy deployment metadata
The previous FWAWhitelist is retired and disconnected from
the delegated curation path. The old snapshot Splitter
also remains deployed and configured as FWA's fallback
owner-payout address, but it receives no current FWA protocol-fee remainder
while 100% of those fees route to FWAToken buybacks. Historical and indexer
compatibility data may still expose both addresses even though neither
belongs in the active table above. That retired snapshot contract is
distinct from the active
OwnerSplitter that receives only the hook's separate
FWA trading fees.