Permissionless launches

New Strategy launches are currently disabled on this site, including ERC-721, ERC-1155, ERC-20, and recursive Strategies. This guide preserves launch mechanics and existing-request information for reference.

When launches are enabled, anyone can request a Strategy for an eligible ERC-721 collection on Ethereum. You do not need to own the collection or get permission from TokenWorks. A request does not give you ownership of the collection or the right to claim its royalties.

For ERC-721C collections that require validator approval, the app blocks payment until the collection administrator approves the current factory’s predicted Strategy address. Permissionless launch access does not bypass the collection’s transfer rules.

Launch eligibility (reference)

The queued initial-purchase flow below applies to ERC-721 launches. ERC-20 and ERC-1155 retain their separate payment and deployment flow.

1. Request a launch (when enabled)

The documented request flow starts by selecting Ethereum and NFT and entering the collection’s contract address. The app checks the collection, checks for an existing Strategy or request, and displays its predicted Strategy address. If its transfer validator requires approval, that exact address must be approved before the app allows payment. This request flow is unavailable while site launches are disabled.

Choose a name ending in Strategy and a ticker ending in STR. Review the current payment, collection, name, ticker, and predicted address before confirming the request in your wallet.

The documented NFT launch payment is 0.25 ETH plus gas. This amount is configurable: when launches are enabled, the review page reads the current contract price and requires the exact amount. A collection already launched through a recognized factory cannot be relaunched by choosing a different token name.

The request transaction is saved as soon as your wallet submits it. Keep its transaction hash if you need to recover the launch on another device.

Your payment funds an initial purchase

For the current factory, the payment above a two-wei liquidity seed is reserved to buy the newly launched Strategy token. At a 0.25 ETH payment, the reserved purchase budget is 0.249999999999999998 ETH.

That payment is estimated to buy roughly 1% of the total token supply: approximately 9.869 million tokens out of one billion in the verified launch calculation. This is an estimate, not a guaranteed allocation. The actual ETH spent and tokens received are shown from the completed launch receipt.

The original paying wallet receives the tokens, even if another wallet finalizes. The initial purchase is tax-free; later buys and sells follow the normal trading fee schedule. A free or tiny-price launch may complete without an initial purchase.

2. Wait for the countdown

The documented default request delay is one hour. Each confirmed request keeps its original deadline and reserved purchase budget, even if the price or default delay changes later.

After the factory’s first successful launch, the documented 24-hour cooldown separates successful launches across that factory. Before its first launch, only the request delay applies.

Your launch becomes eligible at the later of:

• Your request’s original deadline.
• The last successful launch time plus the factory’s current cooldown.

The countdown can move if another collection launches or the owner changes the cooldown. Requests are not guaranteed to launch in submission order. Reaching zero means the request may be finalized; it does not automatically send a transaction.

3. Finalize the launch

At the contract level, anyone can finalize a queued request when it is eligible. The finalizer pays gas only; there is no second launch payment. The site’s launch interface is currently disabled, so this describes the accepting factory’s behavior.

When the interface is enabled, the app checks the latest factory state and simulates finalization before opening the wallet. Another launch can consume the available slot before your transaction is mined, so the transaction can still revert. A reverted finalization leaves the paid request and purchase budget pending and available to retry.

Successful finalization deploys the token and pool, executes the reserved initial purchase, and starts the cooldown for the next launch.

Royalties belong to the collection

Paying to launch someone else’s collection does not entitle you to its royalties. With the default recipient used by the create form, a payer who is the collection contract’s recognized owner receives the royalty allocation; otherwise it remains unclaimed.

The collection owner can later claim and direct future royalties from the Strategy page. This changes the destination of future fees; it does not recover fees already distributed. Unclaimed royalties currently go to the hook’s configured fallback recipient.

Restricted collections and recovery

Some collections enforce ERC-721C or other transfer policies. For new ERC-721C requests, the app checks both compatibility and the required validator approval before allowing payment. If approval is missing, the collection’s whitelist administrator must approve the exact predicted Strategy address shown by the app. An approval for an address predicted by an older factory does not cover the current address.

The contracts can accept a compatible collection’s request before its address is approved; the app requires that approval earlier to avoid an unusable paid request. Existing paid requests remain recoverable and can be retried after the administrator adds approval. Finalization still requires the request delay and global cooldown to permit it, and checks the deployed Strategy against the current transfer policy.

A confirmed request has no cancellation or refund entrypoint. Approval can be revoked or the policy can change after payment. Passing the launch checks also does not certify every marketplace route; marketplace operators need their own applicable permissions.

The documented recovery flow identifies a request by its collection address, including requests accepted by older factories. While the site’s launch interface is disabled, check the original transaction and accepting factory for an existing paid request. Missing indexer data or a temporarily unavailable RPC does not mean a payment failed.

Site availability and contract pauses

New launches are currently disabled in this site’s interface. This does not establish that every factory is paused onchain. The public launcher also has a separate shared pause for new ERC-721, ERC-1155, and ERC-20 payments.

Existing paid NFT requests may still be finalized directly through their accepting factory if its timing, approval, and other contract checks permit it. Existing Strategy trading is separate from launch availability.