OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Smart Contracts

ERC721 Extensions

ERC721 Extensions is an MIT-licensed Solidity package of composable modules for OpenZeppelin ERC721 and ERC1155 NFT contracts. Its documented extensions cover supply tracking and token-ID assignment, sale timing, Chainlink price-feed conversion, wallet holding limits, and soulbound transfer restrictions.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

ERC721 Extensions — OpenViST project profile in Smart Contracts.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when building or adapting an OpenZeppelin 5.x NFT contract and a documented extension matches a rule the contract needs. Check the version requirements before integrating it into an existing codebase.

Who it is for

  • Solidity developers building ERC721 or ERC1155 NFT contracts on OpenZeppelin 5.x.
  • Teams creating reusable NFT contract templates that import only selected extension modules.

Documented uses

  • Add a maximum token supply and track the next token ID during minting.
  • Set a public-sale start time and restrict a contract function until that time.
  • Convert a USD-denominated amount into ETH using a Chainlink price feed.
  • Enforce per-wallet token holding limits or make an NFT non-transferable.
  • Choose sequential, start-offset, or semi-random token ID assignment.
Before you choose

Requirements & limits

The repository is public and identifies the package as MIT-licensed. Installation is documented through pnpm; no price or account requirement is stated.

  • The package targets OpenZeppelin 5.x and Solidity ^0.8.20 and requires @openzeppelin/contracts ^5.2.0.
  • Version 0.1.0 is not backward compatible with OpenZeppelin 4.x; it uses custom errors and the _update hook.
  • RandomlyAssigned uses block.prevrandao and is described as semi-random, not cryptographically secure.
  • For multi-token minting in one transaction, supply availability should be checked with ensureAvailabilityFor(amount).
  • WithSaleStart is built on Ownable; the owner can set the start time, but cannot change it after the sale has begun.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Add a limited-supply extension to an ERC721 contract

Set a token supply cap and use the extension's tracker and availability modifier in a mint function.

Before you start

  • A Solidity ERC721 contract built for OpenZeppelin 5.x and Solidity ^0.8.20.
  • @openzeppelin/contracts ^5.2.0 as a peer dependency.
  • The @1001-digital/erc721-extensions package.

Steps

  1. Install the package with pnpm install @1001-digital/erc721-extensions.

  2. Import the required extension into the Solidity contract.

  3. Inherit WithLimitedSupply and initialize it with the desired maximum supply.

  4. In the mint function, apply ensureAvailability(), obtain an ID with nextToken(), and mint the token.

Expected outcome

The contract example tracks token IDs and checks availability before a single-token mint, subject to the configured cap.

Guide limitations

  • nextToken() does not itself check whether tokens remain; use the availability modifier.
  • For multiple tokens minted in one transaction, the README recommends ensureAvailabilityFor(amount).
  • The package's v0.1.0 is not backward compatible with OpenZeppelin 4.x.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
1001-digital/erc721-extensions · Official homepage title · retained in its source language
How we review sourcesSuggest a correction