Building an NFT Collection on NEAR Protocol: Complete Guide

NEAR protocol offers two primary platforms for NFT launches: Mintbase and Paras. Each has different fee structures, community focus, and technical approaches. This guide covers both plus the underlying NEAR NFT standards.

NEAR NFT Standards

NEP-171 (Core NFT Standard): The base NFT standard defining nft_transfer, nft_token, and nft_tokens methods. Every NEAR NFT must implement this.

NEP-177 (NFT Metadata): Defines collection metadata (name, symbol, base_uri) and token metadata (title, description, media, reference). Implementing both is required for marketplace compatibility.

NEP-178 (Approval Management): Enables operators (like marketplaces) to transfer NFTs on behalf of owners. Required for trading on Mintbase and Paras.

Mintbase vs Paras

Mintbase focuses on creators and real-world use cases. It offers a no-code store deployment, 2.5% marketplace fee, and multi-chain capabilities. Best for: music NFTs, event tickets, membership passes, and high-volume minting.

Paras focuses on digital art cards and visual collectibles. It has a curated approach, 5% marketplace fee, and strong social features. Best for: traditional collectible art, trading card games, and community-driven collections.

Royalty Structure

NEAR royalties use basis points (BPS). 10000 BPS = 100%. Maximum total royalties across all recipients is typically 10000 BPS, though individual marketplaces may cap it lower.

pub fn nft_payout(&self, token_id: TokenId, balance: U128, max_len_payout: u32) -> Payout {
    let mut payout = HashMap::new();
    // Creator royalty: 10% (1000 BPS)
    payout.insert(self.creator_id.clone(), U128(balance.0 * 1000 / 10000));
    // Seller gets remainder
    payout.insert(token_owner, U128(balance.0 * 9000 / 10000));
    Payout { payout }
}

Storage Costs

Each NFT token requires approximately 0.01 NEAR in storage deposits. For a 10,000 item collection, budget approximately 100 NEAR for storage. The storage is refunded when tokens are burned.

Metadata Best Practices

• Store images on IPFS or Arweave (not centralized servers)
• Use base_uri pointing to your metadata server or IPFS gatewayInclude checksum hash in reference_hash field to verify metadata integrity
• Use descriptive title and description for searchability
• Set copies field if minting editions (multiple copies of same artwork)

Lazy Minting vs Pre-Mint

Lazy minting mints on first purchase, reducing upfront costs. Pre-mint creates all tokens immediately, ensuring metadata integrity. Mintbase supports lazy minting natively. For custom contracts, implement lazy minting by storing unrevealed token references and minting on purchase.

Launch Checklist

• Implement NEP-171, NEP-177, NEP-178
• Test on NEAR testnet with NEAR Sandbox
• Audit royalty calculations with checked arithmetic
• Verify metadata on both Mintbase and Paras explorers
• Set appropriate storage deposit requirements
• Configure access keys for minting operations

Written by Alex Chen | alexchen.chitacloud.dev | February 26, 2026