NFTs & Semi-Fungibles
On Solana, NFTs are often thought of as SPL Tokens with 0 decimals and a supply of 1. According to the Token Metadata Standard, however, it is possible for a range of different tokens to have NFT-like characteristics. Phantom refers to all NFT-like tokens as collectibles and will display them separately from
Fungibletokens that appear on the Home tab. Specifically, Phantom will display all
ProgrammableNonFungibletokens on their own Collectibles tab.
Phantom groups collectibles by their Certified Collections introduced in v1.1.0 of the Token Metadata Standard. In order to be grouped together, individual NFTs should all reference the same verified collection mint address. This mint address is itself home to an NFT with metadata that describes the collection (Example). Creators must ensure that this collection is verified on-chain (i.e. that
verifiedis set to
If no verified collection is found, Phantom will fallback to grouping NFTs by the first verified creator's address in the on-chain
creatorsfield. If two unverified items share the same creator address at the 0 index of their
creatorsarray, they will be grouped into the same collection.
When a group is created, a best-effort process is used to determine that group’s name. Phantom will look to these fields in the following order of preference:
nameof the verified on-chain collection NFT
external_url(parsed to remove url parts)
name(of a single collectible)
- 7.address of the first verified creator in the
creatorsarray (also used to group the collection)
When displaying the detail view of an individual collectible, Phantom will prioritize on-chain data in the Metadata Account over off-chain JSON linked via the
urifield. This impacts both the
symbolfield which appears in both locations.
Supported Media Types
Phantom supports a wide-range of media types. For a full list, please refer to:
When determining what media to display for a given collectible, Phantom will search the off-chain JSON for data in the following order of preference:
animation_url— Phantom will select the media source at the collectible's
properties.files— If no
animation_urlis found, Phantom will choose the first file where the
cdnproperty is set to
true. Otherwise, a file will be chosen based on the media type in the following order of preference:
image— Finally, if Phantom still cannot find media to display, it will fallback to the media source at the collectible's
Determining Media Type
If a media source is found in
properties.files, and that source is defined as an object, Phantom will determine the media type based on that file's
typeproperty. Under the Token Metadata Standard, file objects are defined with the following structure:
The media type of the file. If selected, Phantom will use this to determine the media type (Example: "image/png").
The uri source of the file (Example: https://asfh3uxyeoyvtkfqc7jagy3mhtsszhyubnc3wfss5ismdgtw.arweave.net/BIp90vgjs_VmosBfSA2NsPOUsnxQLRbsWUuo-kwZp2o?ext=png)
An optional flag that dictates if the file is hosted on a cdn. If
In cases where Phantom cannot find a source from
properties.files, it may fallback to a media source that is defined as a
image). In these cases, Phantom will look for data in the following order of preference:
- 1.The media source uri’s
?ext=query string parameter (
- 2.The media source uri’s pathname extension (
- 3.If the media source uri comes from the
animation_url, Phantom will infer the media type based on the collectible's
- 4.If the media source uri comes from the
imagefield, Phantom will default to assume it is a png.
If no supported media type can be determined, no media will be selected, and users may see a placeholder image instead.