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

Flow NFT

Flow NFT is an open-source Cadence standard and contract reference for resource-oriented non-fungible tokens on the Flow blockchain. It defines NFT and collection interfaces, collection operations, metadata-view resolution and royalty support for Flow-native implementations.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Flow NFT — 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 a Flow application or contract needs the documented resource-oriented NFT model, collection interfaces, metadata views or royalties. The repository recommends Cadence tutorials before implementation.

Who it is for

  • Cadence smart-contract authors
  • Wallet and marketplace developers
  • NFT indexer developers
  • Applications that mint, hold or move NFTs on Flow

Documented uses

  • Create Flow NFT collections and empty collection resources
  • Represent NFT ownership through Cadence resources stored in accounts
  • Deposit, withdraw and enumerate NFTs in collections
  • Expose standardized NFT metadata views
  • Support royalty-enabled NFT implementations
Before you choose

Requirements & limits

The repository is publicly accessible and identified as open source under the Unlicense. It documents use across Emulator, PreviewNet, Testnet and Mainnet, with separate Emulator handling for deploying the standard contracts.

  • Cadence is required because the standard is implemented in Cadence.
  • The resource-oriented model places NFTs directly in user account storage and supports peer-to-peer transfer patterns.
  • Implementations must use the NFT and collection interfaces for the documented deposit, withdrawal and querying behavior.
  • Metadata interoperability depends on implementing the MetadataViews.Resolver interface where required.
  • Emulator setup differs because the repository notes that standard contracts must be deployed with the emulator’s -contracts flag.

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

Set up a Flow NFT contract around the standard

Prepare a Cadence NFT implementation that uses the documented Flow NFT contract interfaces and imports.

Before you start

  • Cadence programming knowledge; the repository recommends completing Cadence tutorials first.
  • A Flow development environment targeting Emulator, PreviewNet, Testnet or Mainnet.
  • The documented contract addresses for the selected network.
  • For Emulator use, the repository notes that the standard contracts must be deployed with the emulator’s -contracts flag.

Steps

  1. Define an NFT resource and collection using the NonFungibleToken interfaces.

  2. Implement collection creation, withdrawal, deposit and token-ID listing functions.

  3. Implement MetadataViews.Resolver when the NFT needs standardized metadata views.

  4. Import NonFungibleToken, ViewResolver and MetadataViews from the documented network address; deploy those contracts separately for Emulator as specified.

Expected outcome

A Cadence contract structure aligned with the Flow NFT standard and its documented collection and metadata interfaces.

Guide limitations

  • The guide covers contract structure and imports, not a complete application deployment or marketplace integration.
  • Deposit implementations must cast incoming resources to the specific NFT type before storing them, as required by the repository guidance.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
2 October 2026
Original website title
onflow/flow-nft · Official homepage title · retained in its source language
How we review sourcesSuggest a correction