nft-standards

NFT Standards - ERC-721 and ERC-1155 Smart Contract Development Guide

Skills Overview

The NFT Standards skill provides complete ERC-721 and ERC-1155 NFT standard implementation plans, covering metadata handling, minting strategies, and marketplace integration. It helps developers quickly build NFT contracts that comply with industry norms.

Suitable Use Cases

Create NFT Collectible Series

Ideal for issuing various NFT projects such as art collectibles, game items, and collectibles. Provides limited supply control, batch minting, and metadata management.

Develop NFT Marketplace Functionality

Supports standard interfaces for major marketplaces such as OpenSea and LooksRare, including EIP-2981 royalties implementation, enumeration features, and authorization management.

Implement On-Chain or Off-Chain Metadata

Supports two approaches: IPFS off-chain storage and fully on-chain metadata. You can choose based on needs, such as generating dynamic SVGs or using fixed JSON references.

Core Features

ERC-721 Standard Implementation

Based on OpenZeppelin’s non-fungible token (NFT) contract, includes URIStorage, Enumerable extension, limited supply control, price setting, and withdrawal functionality. Supports both single minting and batch minting.

ERC-1155 Multi-Token Standard

Suitable as a semi-fungible token standard for multiple asset types such as game items. Supports batch minting, batch transfers, and supply management, significantly reducing Gas consumption.

Advanced NFT Features

- EIP-2981 standard automatic royalty splitting
- Soulbound Token (SBT) non-transferable implementation
- Dynamic NFTs with attributes that change over time or with interactions
- ERC721A Gas-optimized batch minting
- On-chain SVG metadata generation

Frequently Asked Questions

Which should I choose: ERC-721 or ERC-1155?

ERC-721 is suitable for art collectibles where each token is unique, with each Token having independent metadata. ERC-1155 is suitable for scenarios like game items, where the same ID can have multiple copies and batch transfers save more Gas.

Why store NFT metadata on IPFS?

IPFS provides decentralized, permanent storage, avoiding the risk of losing metadata due to centralized server shutdowns. Combined with pinning services, it ensures content stays online continuously, aligning with the concept of permanent NFT storage.

How do I add royalty functionality to an NFT?

Implement the EIP-2981 standard interface. In the royaltyInfo function, return the royalty recipient address and royalty rate (typically 5%-10%). Mainstream marketplaces such as OpenSea and LooksRare will automatically recognize this standard and automatically allocate royalties during secondary-market trades.

Can Soulbound Tokens be transferred?

Soulbound Tokens (SBTs) prohibit transfers by overriding the _beforeTokenTransfer function. They can only be minted to the recipient’s address. Users may choose to burn their own SBTs, but cannot transfer them to others. They are suitable for scenarios such as identity verification and achievement badges.

How can I optimize Gas costs for batch minting NFTs?

Use the ERC721A standard instead of traditional ERC-721. It optimizes batch minting logic so that the Gas cost for minting multiple NFTs changes from O(n) to nearly O(1), greatly reducing minting costs for both the project team and users.