🔵How to Create a Collection

Before you can mint NFTs, you must deploy a collection first. Think of a collection as your NFT “contract container” on the blockchain—every NFT you mint will belong to a specific collection. On Rare NFT, the recommended flow is:

1) Create (deploy) a collection → 2) Mint NFTs into it → 3) List NFTs for sale

If you skip step 1, you won’t have a destination contract to mint into.

---

What you need before starting

• A connected wallet (MetaMask or any supported EVM wallet).

• Enough gas on the network you choose:

  • BNB Chain: you need BNB for gas

  • Relix Chain: you need the chain’s native token for gas (testnet/mainnet depending on your environment)

• A clear decision on which chain you want your collection to live on:

  • Rare NFT supports Multichain (BSC & Relix Smart Chain), and your collection is deployed per-chain.

---

Step 1 — Connect your wallet

Open Rare NFT and click connect. Once connected, the page should display your wallet state (network + ability to sign).

You will deploy a contract, so your wallet will ask for transaction approval.

---

Step 2 — Switch to the correct chain (very important)

A collection is deployed to the blockchain network you are currently connected to.

That means:

✅ If you want your collection on BNB Chain, connect your wallet to BNB Chain first. ✅ If you want your collection on Relix Chain, connect your wallet to Relix Chain first.

On the “Deploy a New NFT Collection” page, check the network label shown in the UI (as shown in your screenshot). Use it as your confirmation that you’re deploying on the right network.

Common mistake (avoid this)

If you deploy on the wrong chain by accident, you can’t “move” the collection to another chain. You would need to deploy a new collection again on the correct chain.

So: always verify the chain before clicking Deploy.

---

Step 3 — Fill the Collection Details

In the Collection Details panel, you’ll see several fields. Here’s what each one means:

1) Name (Required)

This is the public name of your collection.

Examples:

• Rare Genesis

• Relix Legends

• RDC Weapons

Tip:

• Make it unique and recognizable. This is what users will see in listings and profiles.

2) Symbol (Required)

A short ticker-like identifier for your collection.

Examples:

• RGN

• RLEG

• RDCW

Tip:

• Keep it short (3–6 characters is ideal).

3) Description (UI only)

This description is used for the user interface and preview experience.

In most setups:

• It improves how your collection appears in the marketplace UI

• It may not be stored on-chain (depending on the contract logic)

Write something short and clean, example:

“A curated collection of Rare NFTs built for multichain trading.”

4) Collection Image (Optional, max 2MB)

This is the image that represents your collection in the UI.

Best practices:

• Use square images (recommended)

• Keep it under 2MB

• PNG/JPG works best

If you want your collection to look professional on marketplace pages, adding an image is strongly recommended.

---

Step 4 — Upload the image to IPFS (Recommended)

If you add a collection image, you should store it on IPFS so it stays accessible and consistent.

In your UI flow:

1. Click the upload area to select an image

2. Click Upload Image to IPFS

3. Wait until the upload completes

Once uploaded:

• The preview panel should update

• Your IPFS image field should show as set (or change from “not set”)

Why IPFS matters:

• It makes your collection image portable and easy to load across different platforms.

---

Step 5 — Set Royalty and Base URI

Royalty (BPS)

Royalty is a percentage fee paid to the royalty receiver for secondary sales.

Your UI uses BPS (basis points):

• 100 = 1%

• 500 = 5%

• 1000 = 10%

Recommended range:

• 2% to 10% (common marketplace standard)

Example: If you set 500 BPS, then royalty is 5.00%, matching what you see in the preview.

Base URI

Base URI is the “root” for NFT metadata resolution.

In simple terms:

• When you mint NFTs, token metadata can be formed like: BASE_URI + tokenId (depending on your contract)

If you’re not ready with metadata hosting yet:

• You can leave it empty for now (if your contract supports later updates)

• Or set it once you already have an IPFS folder / metadata endpoint ready

Tip:

• If your flow auto-fills Base URI after image upload, keep it unless you have a custom metadata setup.

---

Step 6 — Preview and verify before deploying

On the right side (Preview panel), confirm:

• Collection name

• Royalty percent

• Network (chain) matches your wallet network

• Base URI / Image state is correct

This preview is your last “sanity check” before you spend gas deploying.

---

Step 7 — Deploy the collection

When ready:

1. Click Deploy Collection

2. Confirm the transaction in your wallet

3. Wait for confirmation

After success:

• The new collection address will show under Your Collections (on-chain)

• You may see actions like Explorer and Copy next to it

This proves your collection contract is deployed and usable.

---

Step 8 — What happens next (Minting requires a collection)

Once you have at least one collection created, you can proceed to mint NFTs into it.

This is mandatory:

• No collection → no mint destination → no NFT can be minted

So your normal workflow becomes: ✅ Create collection → ✅ Mint NFT → ✅ List NFT for sale → ✅ Trade

---

Troubleshooting (quick fixes)

“Deploy Collection” does nothing

• Check wallet is connected

• Make sure you’re on a supported chain (BSC / Relix)

• Try refresh and reconnect wallet

Transaction failed / reverted

• You may not have enough gas token

• Wallet is on the wrong network

• RPC/network is unstable (retry after switching RPC or reconnecting)

Collection not showing in “Your Collections”

• Click Refresh

• Wait a few seconds after confirmation

• Verify on Explorer using the wallet transaction hash