Pointers
Pointers are unique, case-insensitive strings that reference an active entity. Content servers can resolve these pointers to obtain the entity's identifier.
Remember that both entities and their files are immutable in the Decentraland content system, and their identifiers change when replacement versions are uploaded. Pointers, on the other hand, are stable references that persist across replacements. This is achieved by automatically redirecting the pointer to a new entity when the owner uploads a replacement.
Multiple pointers can resolve to the same entity, as is often the case with scenes.
As you may gather, the most common use of pointers is obtaining the ID for the active version (i.e. latest replacement) of an entity, in order to download it.
Pointer Types
There are 4 types of pointers that content servers can resolve to entities, each with its own syntax:
Scene pointers are parcel coordinates, such as
"0,0".Profile pointers are the Ethereum address of the owner.
Wearable pointers and emote pointers are either collection item or off-chain URNs.
Store pointers are off-chain URNs with the Ethereum address of the owner.
Outfits pointers are the Ethereum address of the owner suffixed by
:outfits.
You can find more details in their specific sections.
Resolving Pointers
Content servers have an endpoint that can resolve pointers into their active entity's manifest, by making a GET request to:
https://<content-base-url>/entities/<entity-type>?pointer=<pointer>Some useful examples, using the Foundation's content server:
Note that, if you already know the entity's ID, you can download the manifest file directly.
Last updated