Create a Manifold-compatible mint wrapper, then launch a hosted page or embeddable widget.

It is a creator workflow for setting up a Manifold ERC-721 collection, adding a mint wrapper, configuring sale phases, and launching either a hosted mint page or a widget for your own site.

Think of the Manifold collection contract as the artwork container, and the wrapper as the mint packaging around it. The wrapper handles sale rules, allow lists, limits, payment routing, metadata assignment, and admin controls while minting tokens into the Manifold collection.

1/1/X Mint Factory is designed around the standard Manifold ERC-721 Creator Core contract. When you import an existing contract, 1/1/X Mint Factory verifies that it matches the expected Manifold contract type and that your connected wallet owns it before you continue.

The base collection flow uses the standard audited Manifold ERC-721 contract. The wrapper is separate 1/1/X mint logic, so 1/1/X Mint Factory displays wrapper source verification separately from the Manifold collection contract.

Use an existing contract if you already created the collection in Manifold and your connected wallet owns it. Create a new one if this drop needs a fresh ERC-721 collection contract before the wrapper is deployed.

The connected wallet is treated as the creator wallet. It owns newly created collection contracts, controls the wrapper admin settings, and can run owner-only actions like phase edits, allow-list updates, pausing, metadata updates, and withdrawals.

The treasury wallet is where creator mint funds are withdrawn. 1/1/X Mint Factory uses the connected wallet by default, and the Admin panel includes a treasury update control for changes after launch.

You may lose the ability to administer the wrapper or withdraw funds. Use a wallet you can safely maintain, and consider a secure multisig for higher-value launches.

Collectors pay mint costs (price + gas) and the platform mint fee. Creators pay launch/admin gas and permanent storage fees when they create the collection, deploy the wrapper, upload permanent metadata, or update admin settings.

1/1/X Mint Factory charges a flat platform fee of 0.0004 ETH per token at mint time.

The minter (collector) pays the platform fee directly in the mint transaction with each token they mint.

Some prompts are paid transactions, such as deploying a contract or attaching the final metadata URI. Other prompts are gas-free signatures used by storage providers. The launch step explains why each wallet action is needed before the wallet opens.

Yes. Hosting can stay inexpensive, but active usage adds costs for RPC calls, verification APIs, storage orchestration, analytics, indexing, support tooling, and secure creator-profile records.

1/1/X Mint Factory keeps costs lower by using creator-paid wallet transactions, charging permanent storage during launch, caching reads where possible, and avoiding direct large-file hosting. Ongoing operating costs come mainly from reliable RPC, Etherscan/API usage, indexing, creator records, and support tooling.

Permanent storage protects the artwork and metadata links so you do not have to keep the original IPFS folder pinned forever or risk empty images on marketplaces later.

The creator pays permanent storage fees from the connected wallet during launch. The cost depends on file size, generated metadata size, and the storage network or provider price at that moment.

Yes. Upload your finished artwork files to an IPFS folder first, copy the CID or full IPFS link into 1/1/X Mint Factory, and upload the metadata CSV. 1/1/X Mint Factory reads those files, builds final token metadata, and then stores the final package permanently before launch.

No. Pinata is an easy IPFS option because it has a clear upload UI and gives you a folder CID. Any IPFS provider works as long as the folder is public, pinned, and the asset filenames match the CSV.

After permanent storage is created and attached to the wrapper, collectors load the permanent links. Keeping your source IPFS folder pinned is still a good archive practice, but the permanent storage step removes long-term dependence on that source folder.

Using creator-provided IPFS keeps hosting costs lower, reduces upload abuse risk, gives artists control over their source files, and lets 1/1/X Mint Factory focus on validation, metadata generation, and permanent storage.

1/1/X Mint Factory supports the 1xStudio metadata template and compatible token metadata CSVs with token names, descriptions, asset filenames, and traits. During launch, each row is converted into the individual JSON metadata files needed for minting.

No. 1/1/X Mint Factory derives asset links from the CID or IPFS link you enter, so the CSV only needs token metadata and asset filenames.

Yes. The CID field accepts a raw CID, an ipfs:// link, or a gateway URL and normalizes it before checks run.

1/1/X Mint Factory blocks the next step and shows a clear error. Fix it by renaming files, updating the CSV filenames, or using the correct IPFS folder CID, then run the check again.

1/1/X Mint Factory flags the mismatch because every token needs metadata. You can either update the supply to match the uploaded metadata count or upload a CSV with the correct number of rows.

A phase is a time window with its own price, wallet limit, and access rule. For example, you can create an allow-list phase first and a public phase after it.

Duration is calculated from start and end times. If you edit duration, the end time updates. 1/1/X Mint Factory keeps phases sequential and non-overlapping, and reordering keeps the timing slot logic easy to follow.

The allow-list amount controls how many tokens that wallet can access in that allow-list phase. The phase max is still useful for public phases and as a general cap, but allow-list rows can give wallet-specific allowances.

It lets you upload one CSV once and apply the same wallet list across every allow-list phase, instead of uploading a separate CSV for each phase.

If enabled, unused allowance from earlier phases can carry into the next eligible phase. This helps collectors keep access if they missed an earlier window.

1/1/X Mint Factory walks through the required actions in order: create or confirm the Manifold collection contract, verify source, create the wrapper, create permanent storage, attach final metadata, and publish the mint page.

No. Deploying a contract needs a wallet transaction, but Etherscan source verification is an API submission and status check. The Verify button shows submission progress and changes to Check Status while Etherscan processes the request.

The wrapper is a separate deployed contract, so its source code is verified separately from the Manifold collection contract. Wrapper verification runs independently and does not block storage or mint page setup once the wrapper itself is deployed.

1/1/X Mint Factory shows an Etherscan reference after submission. You can use Check Status, copy the reference for support, or open the contract on Etherscan to confirm whether the source code is published.

Etherscan queues verification requests and sometimes returns delayed status updates. If it takes more than a few minutes, the verification card shows a Re-submit option so you can send a fresh request.

Ethereum Mainnet is the only supported chain. Support for L2 networks may be added later once contract deployment, wrapper creation, RPC, explorer verification, and storage payments are ready for each chain.

Confirm the connected owner wallet, collection contract, CSV and IPFS checks, mint page preview, allow-list behavior, permanent storage completion, Etherscan verification, and mint behavior before sharing the public mint page.

Choose hosted mint page if you want a dedicated page managed from 1/1/X Mint Factory. Choose widget if you want collectors to mint from your own website. You can choose both if you want a page and embeddable code.

Yes. The preview shows the look and feel, selected accent colors, timer styling, pre-reveal image, collection name, and supply progress bar even before the wrapper is live.

The mint page caps quantity by the most restrictive live limit: remaining supply, phase max, wallet allowance, and how much that wallet already minted. If only one token remains, the selector only allows one.

After selecting a wrapper, Admin lets the owner wallet review contract addresses, open the mint page, update phases, update allow lists, mint/admin airdrop, check and withdraw funds, update treasury, update metadata, pause, lock metadata, and manage wrapper ownership.

Yes, when the base ERC-721 contract supports burning and the connected wallet currently owns the token ID. Admin checks token ownership before showing the burn action.

The Funds tab can check the wrapper contract balance and show available funds in ETH. The owner wallet can then withdraw to the configured treasury wallet.

Drafts are saved against the creator wallet so they can be resumed later from the same wallet profile. Published creation records are stored securely and indexed by wallet, collection contract, wrapper contract, and mint page status.

Duplicating creates a new draft with the same editable settings, but clears deployed contract steps so the next launch creates or imports a new collection and wrapper.

Contracts, ownership, mint rules, funds, and final metadata URI live onchain or in permanent storage. Draft settings, UI preferences, helper labels, and creation records are saved to the creator profile so 1/1/X Mint Factory can show the right drafts, published pages, contract addresses, and admin tools when the wallet connects.