Skip to Content
CreatorsCollections Management

Collections Management

Own a collection? This page covers profile & branding, mint controls (for Drops), royalties, payouts, and safety. Everything is non-custodial and enforced by the underlying contracts.

To manage a collection, connect the owner wallet (or a wallet with delegated admin rights, where supported).
If your project uses a Multisig, ensure enough signers are available for admin actions.

Collection profile & branding

Keep your storefront crisp and trustworthy.

Editable fields

  • Name & symbol — shown on item and collection pages.
  • Description — short, scannable; include links to roadmap/whitepaper if relevant.
  • Logo (avatar) — square, high-contrast works best in dark/light themes.
  • Cover image (banner) — wide (hero) image for collection header.
  • Links — website, X/Twitter, Telegram, Discord, and support docs.

Good hygiene

  • Use consistent iconography between marketplace and socials.
  • Keep the description factual (supply, mint policy, royalties, license).
  • Verify your contract in the explorer and request verified status on the marketplace.

Royalties & marketplace fees

  • Royalties (optional): honored at settlement per the collection’s configured policy.
  • Marketplace fee: flat 2.5% of the final sale — 1.5% routed to the Reward Distributor (Non-Fungible Comrades holders), 1% to the Panthart fee wallet.
  • Currencies: sales can settle in ETN (native) or selected ERC-20s; proceeds and fee splits follow the listing’s currency.

For buyers’ perspective and fee math examples, see Collectors → Buying & Bidding and the Fee Calculator on the docs homepage.

721 Drop controls (phased mint)

If your collection is a Drop (ERC-721), you’ll see phase controls and supply caps in the UI.

Setup

  1. Basics — name, symbol, max supply, base URI (placeholder if planning a reveal).
  2. Branding — logo, banner, description, links.
  3. Royalties — set policy according to your creator terms.
  4. Admins — add maintainers (if your contract supports delegated roles).

Max supply and certain invariants may be locked on chain. Double-check before saving.

Proceeds & withdrawals

On a Drop collection page, owners can withdraw proceeds that have accrued from on-chain mints and primary sales.

  • Owner check — the connected wallet must be the collection owner (or a permitted payout role).
  • Multi-currency — proceeds withdraw in the same currency they were collected (ETN or the ERC-20 used).
  • Explorer links — every withdrawal shows a tx link for auditability.

If your project uses a Multisig for admin functions or treasury, make sure the withdraw call is made by the Multisig address and has the required signatures.

Moderation & safety

  • Freeze / unfreeze (if supported) — temporarily lock sensitive parameters during incident response.
  • Blacklist / stolen registry (if present) — integrate with your project’s stolen/flagged tokens policy.
  • Verification — request or maintain verified status; keep socials and site links in sync.

Always cross-check contract addresses in References → Contract Addresses before executing admin actions.

Troubleshooting

“I can’t edit the collection.”
You’re not connected with the owner/admin wallet, or the contract is locked. Reconnect the correct wallet or switch to your Multisig.

“Withdraw button is disabled.”
No proceeds are currently available, or you’re connected with a non-owner wallet.

“Reveal didn’t update images.”
Your new base URI may not be reachable or the cache hasn’t refreshed yet. Verify the CID, then hard refresh; confirm the tokenURI(tokenId) on chain points to the new location.

“Presale wallets rejected.”
The allowlist on chain doesn’t match your list. Re-generate proofs / Merkle root and update the config before reopening.

Last updated on
Listing & AuctionsCollectors