NFT & ERC-721 Gas Optimization

ROLE: You are an NFT contract optimization specialist who builds gas-efficient collection contracts. You understand the differences between ERC-721 implementations (OpenZeppelin, Azuki's ERC-721A, Solmate, custom) and how to choose and configure the right implementation for different use cases.

CONTEXT: NFT minting events are gas-sensitive — high gas costs during popular mints drive users away and increase costs for the project. I need to build an NFT contract that minimizes minting cost per unit, supports efficient batch operations, and keeps transfer costs low for secondary trading.

TASK:
1. ERC-721A & Batch Minting — Explain the ERC-721A optimization and when to use it. Cover the core innovation (lazy minting — batch mints only write to storage once regardless of quantity), the gas savings: single mint vs batch minting 5 vs 10 tokens compared to standard ERC-721, the trade-off (first transfer of each batch-minted token costs more gas because it needs to write the ownership), when ERC-721A is ideal (PFP collections where users mint multiple tokens) vs when it is not (1/1 art where batch minting is not common), and how ERC-721A handles tokenOfOwnerByIndex and other enumeration efficiently.
2. Mint Function Optimization — Detail techniques for minimizing the gas cost of minting. Cover removing unnecessary mint-time logic (on-chain metadata generation is expensive — move it off-chain), using merkle proofs for allowlist verification instead of on-chain mapping storage, minimizing state changes during mint (avoid writing metadata on-chain during mint, set it later), packing mint-related data into fewer storage slots, gasless minting through meta-transactions (user signs, relayer submits), and lazy reveal patterns (mint placeholder, reveal later — avoids sniping and reduces mint gas).
3. Transfer & Marketplace Optimization — Walk through optimizing transfers and marketplace interactions. Cover the gas cost breakdown of a standard ERC-721 transfer (ownership update, approval clear, balance update), operator approval patterns (approve vs setApprovalForAll gas comparison), implementing ERC-2981 royalties efficiently (view function with minimal computation), supporting bulk transfers (transferring multiple NFTs in one transaction), and the impact of transfer hooks (before/after transfer callbacks) on gas.
4. Metadata & Storage Strategies — Explain gas-efficient approaches to NFT metadata. Cover on-chain vs off-chain metadata trade-offs (on-chain is expensive but permanent, off-chain is cheap but dependent on IPFS/servers), base URI pattern (store one string, append token ID — minimizes per-token storage), on-chain SVG generation (expensive but fully decentralized — optimize SVG size), SSTORE2 for efficient on-chain data storage (storing data as contract bytecode), and token URI caching strategies for dynamic metadata.
5. Collection Management Optimization — Describe gas-efficient patterns for managing large NFT collections. Cover using bitmap-based tracking for mint status (1 bit per token vs 32 bytes per token), efficient royalty management (global royalty vs per-token royalty storage), admin functions that operate on ranges rather than individual tokens, supply tracking without enumeration (avoid ERC-721Enumerable if not needed — it adds significant gas to every transfer), and burn optimization (what to clean up and what to leave to save gas).
6. Emerging NFT Standards & Optimizations — Address newer NFT standards that offer gas improvements. Cover ERC-6551 token-bound accounts (allowing NFTs to own assets without gas-heavy wrapper contracts), ERC-5169 (linking scripts to tokens), ERC-4907 (rental standard with gas-efficient expiration), soulbound token patterns (non-transferable, simpler than full ERC-721), ERC-1155 semi-fungible tokens (more gas efficient for fungible-like NFTs), and comparing gas costs across these standards for different use cases.