Collections
This deployment is whitelisted to a single collection: the Foundation shared minting contract.
The core protocol is collection-agnostic: a position is just a listed ERC-721 paired with ETH backing, so any standard collection can in principle be deposited, weighted, priced, and settled exactly the same way1. This deployment narrows that to one collection by whitelist: Foundation (FND), the shared minting contract where early crypto-art 1/1s were minted in 2021.
When whitelist enforcement is on, eligibility affects only new listings and relists2. Existing positions remain usable if a collection is removed later.
Launch configuration
| # | Collection | Contract |
|---|---|---|
| 1 | Foundation (FND) — shared minting contract, 114,275 tokens | 0x3B3ee1931Dc30C1957379FAc9aba94D1C48a5405 |
Enforcement is on at deploy, and the list is owner-curated only: the whitelist contract's optional public burn-to-whitelist path is disabled in this deployment. Early Zora (0xabEFBc9fD2F806065b4f3C237d4b59D9A97Bcac7, 31,296 tokens) may be added later with a single owner call. The live onchain allowlist is authoritative and may change.
Technical breakdown
- The pool stores each position's collection address and token id and moves the NFT with the standard transferFrom / safeTransferFrom interface. Weighting, pricing, VRF selection, and settlement all operate on the ETH backing and are independent of which collection a position belongs to.
- When whitelistEnabled is true, the pool checks its manager's per-collection mapping on both listNFT and relistNFT. The manager supports owner curation and sticky blocking; the optional transfer-to-dead-address entry path is disabled here (its token address is unset at construction). Removing a collection blocks only future listings; existing positions still allocate, settle, and withdraw.