How Minting Works on OmniHub
OmniHub automatically creates a dedicated minting page when a collection is deployed on a supported network. No separate setup is required. That page becomes the public interface where users mint NFTs from the collection.
This guide explains how minting works on OmniHub, including:
- how the minting page is generated
- what creators can customize
- how minting phases work
- how wallet mint limits are counted across phases
- what users should check before and after launch
What happens after you deploy a collection
After a collection is deployed, OmniHub activates the project and provides a dashboard with key collection details, including the mint page, contract address, and transaction info/explorer links. This is documented for Editions, and the Drops flow also redirects creators to the dashboard after deployment.
OmniHub also documents automatic mint page generation for each deployed collection, and the page type depends on the collection format.
What the minting page is for
The minting page is the public page where collectors mint NFTs from your collection. OmniHub describes it as a dedicated page created automatically after deployment.
How the minting page works on OmniHub
OmniHub’s docs explain that the minting page is generated based on the collection format and can be customized later from the collection dashboard (Profile section). Creators can update presentation details without redeploying the collection.
Minting page auto-generation
You do not need to build or host a separate mint site. OmniHub generates the minting page automatically once the collection is deployed.
Minting page customization
OmniHub documents the following customization areas:
- collection name and description
- banner image
- social links
- share image (configured in dashboard settings)
This makes the minting page both a mint interface and a project landing page.
Minting phases on OmniHub
OmniHub has a documented minting phase model that explains how sale phases (for example OG, Allowlist, Public) are structured, including:
- phase start/end times
- phase price
- phase mint limit
- wallet limit behavior across phases
Why phases matter
Phases let creators control:
- who can mint first
- pricing at each stage
- wallet limits by phase
- public sale timing
This is useful for community launches, allowlists, and staged mint rollouts. This is an inference from the documented phase structure and examples.
How wallet mint limits work across phases
This is the most important rule in OmniHub’s minting phases guide:
Wallet minting limits are cumulative across all phases. Mints from earlier phases reduce how many NFTs that wallet can mint later.
OmniHub’s docs also state that each phase has its own minting limit, but the wallet’s total minting capacity is determined by the highest overall limit across phases.
Practical example from OmniHub docs
OmniHub’s example shows:
- OG phase limit = 1
- Allowlist phase limit = 1
- Public phase limit = 5
- total wallet cap remains 5 across all phases combined
So if a wallet mints 1 NFT early, it usually has fewer mints remaining for Public.
Example minting phase structure
OmniHub’s Minting Phases page includes an example with three common phases:
1. OG Mint
- early access window
- own phase time range
- own price
- own wallet limit
- phase-specific eligibility rules (example: OG participation can block Allowlist participation)
2. Allowlist Mint
- allowlist-only access
- own time window
- own price
- own wallet limit
- mints count toward the total wallet cap
3. Public Mint
- open to all
- own time window
- own price
- highest wallet cap in the example
- total per-wallet mints across all phases cannot exceed the public cap in the example scenario
How minting works for collectors
From the collector side, the flow is simple:
Step 1 - Open the collection minting page
Collectors use the mint page generated by OmniHub after deployment.
Step 2 - Check the current mint phase
Collectors should verify:
- whether the phase is OG / Allowlist / Public
- whether their wallet is eligible (for gated phases)
- current price
- current wallet limit and remaining allowance (based on prior mints)
Step 3 - Mint with a connected wallet
Collectors mint from the page according to the active phase rules and pay the phase price plus network gas fees. OmniHub docs separately note pricing fields exclude gas fees in collection setup docs.
How creators should prepare minting before launch
1. Set the correct mint settings during creation
OmniHub’s Create flow includes advanced settings such as:
- mint schedule
- royalties
- per-address mint limits
- transferability
These settings shape how the mint behaves once the collection is live.
2. Choose the right collection format
Minting behavior also depends on whether the collection is:
- Editions (same artwork)
- Drops (unique artwork / metadata-based)
OmniHub documents both flows separately, and the minting page type depends on the collection format.
3. For Drops, validate metadata and supply
OmniHub’s Drops docs note that supply should match the number of metadata files uploaded to IPFS to avoid minting issues. OmniHub also provides a dedicated IPFS guide for correct metadata structure.
What creators can update after deployment
OmniHub documents that creators can continue configuring the project from the dashboard after deployment, including mint page presentation settings. The mint page docs specifically mention profile-level customization (name, description, banner, social info, share image).
OmniHub also documents contract version upgrades as a separate one-time on-chain action to access new features and compatibility improvements, while keeping the same contract address via proxy architecture.
Common minting mistakes to avoid
Ignoring cumulative wallet limits
Wallet limits are cumulative across phases. Early mints reduce later mint capacity.
Launching without a clear phase plan
If you use OG / Allowlist / Public phases, define the timing, price, and wallet limits in advance so the mint flow is easy to understand.
Mismatch between supply and metadata (Drops)
For Drops, supply should match uploaded metadata count to avoid minting problems.
Forgetting mint page customization
The minting page is user-facing. Add a clear name, description, banner, and social links in the dashboard so collectors understand the project before minting.
Frequently asked questions
Do I need to create a separate mint website?
No. OmniHub automatically generates a dedicated minting page after deployment.
Can I edit the minting page after deployment?
Yes. OmniHub docs state you can customize mint page details in the collection dashboard/Profile section, including name, description, banner, and social info.
Are wallet mint limits separate for each phase?
Each phase has its own limit, but wallet minting is cumulative across phases, and earlier mints count toward the total wallet cap.
Does OmniHub support allowlist and public mint phases?
Yes. OmniHub’s Minting Phases documentation explicitly describes examples such as OG, Allowlist, and Public mint phases.
Can I upgrade the collection contract later?
Yes. OmniHub documents a contract version upgrade flow that preserves the contract address and mint history through a proxy-based architecture.
Sources and references
Official sources
- OmniHub Minting Page - https://omnihub-launchpad.gitbook.io/omnihub/create-and-deploy-nft/minting-page
- OmniHub Minting Phases - https://omnihub-launchpad.gitbook.io/omnihub/create-and-deploy-nft/minting-phases
- OmniHub Editions Collection - https://omnihub-launchpad.gitbook.io/omnihub/create-and-deploy-nft/editions-collection
- OmniHub Drops Collection - https://omnihub-launchpad.gitbook.io/omnihub/create-and-deploy-nft/drops-collection
- OmniHub How to Use IPFS - https://omnihub-launchpad.gitbook.io/omnihub/create-and-deploy-nft/how-to-use-ipfs
- OmniHub Contract version - https://omnihub-launchpad.gitbook.io/omnihub/create-and-deploy-nft/contract-version
- What is OmniHub overview - https://omnihub-launchpad.gitbook.io/omnihub
Related OmniHub pages
Last updated: February 26, 2026
Reviewed by: OmniHub team
Version: 1.0