ERC721A

ERC721A Explained in Detail

ERC721A is an ERC721 implementation optimized for batch minting. It reduces gas by storing ownership data sparsely and inferring ownership for sequential token IDs.

That optimization changes internal assumptions compared with a plain ERC721.

Smart contract example

_mint(msg.sender, quantity);

In ERC721A, the second argument is a quantity, not a token ID.

ERC721A in Auditing

ERC721A bugs often appear around ownership inference, transfers, burns, supply counts, and batch mint boundaries. Custom code that assumes every token ID has its own explicit owner slot can break.

Auditors test token IDs around every boundary.

Red flags in code

• Custom logic assumes every token ID has an explicit ownership record.

• ownerOf behaves incorrectly after transfer or burn inside a batch.

• Off-by-one errors around start token ID, next token ID, or max supply.

• Safe mints call receiver hooks before mint limits are finalized.

• Interface support is wrong after adding royalty or custom extensions.

How to test or review it

• Batch mint and check first, middle, last, and next unminted token IDs.

• Transfer or burn one token inside a batch and recheck adjacent ownership.

• Fuzz quantity, payment, max supply, and per-wallet limits.

• Test safe mint to accepting, rejecting, and reentrant receivers.

• Verify supportsInterface for every extension.