| Property | Description | Example |
|---|---|---|
| Creator ID | Randomly generated UUID for the creator. This will be provided to you and only you will be able access it. | 40877d72-9957-4de7-af77-1ee9f54a529e |
| Creator Collection ID | A creator’s collection ID. This should be unique for each creator. It can be any string. | 12 | pb\_1232124| bedde205-5af2-423b-9092-088c8951a2ea |
| Token ID (optional) | The token ID is for uniquely identifying NFT assets in a collection. It will be empty if it is SFT (ERC1155 equivalent). This can be any string (like a UUID), however, it is best practice to stick to a number. | 4637 | 61d21cf3-6e0d-4b9d-a2c8-55583eb81a84 |
| Asset ID | This is the combination of creatorAddress,creatorCollectionId & tokenId. SFT assets will not have a Token ID. | 40877d72-9957-4de7-af77-1ee9f54a529e:12:4637 |
display swappable slots for partybear
}
```
## GraphQL Query
```graphql
query GetAssetTree($input: AssetTreeInput!) {
getAssetTree(input: $input) {
... on AssetTreeResultSuccess {
data
}
... on AssetTreeResultFailure {
errors {
message
}
}
}
}
```
```json
{
"input": {
"tokenId": "1000",
"collection": {
"chainType": "evm",
"location": "0x6bca6de2dbdc4e0d41f7273011785ea16ba47182",
"chainId": 1
}
}
}
```
Where,
* `tokenId` - The token ID of the NFT you want the asset tree for
* `collection.chainType` - Either `evm` or `root` to specify where the asset lives on The Root Network we have both EVM (`evm`) and native substrate (`root`) storage, so this specifies where to look
* `collection.location` - The location of the NFT, this is either a contract address if the `chainType` is `evm` or a collection ID (number) if the `chainType` is `root`
* `collection.chainId` - The Chain ID of the blockchain the asset lives on
# How it works
Source: https://docs.therootnetwork.com/asset-register/how-it-works
## Schemas
Schemas play a pivotal role in the Asset Register ecosystem. They exist within a specific namespace and provide a comprehensive description of an asset. The goal is to define the capabilities of an asset for linking, ensuring that any applications interacting with these assets can interpret and represent them correctly. These descriptions are crucial for seamless integration between various assets.
To achieve this, the Asset Register utilizes schemas. These schemas are registered both on-chain and off-chain through the Asset Register API. This process ensures that information about an asset's properties and compatibility with other assets (i.e. asset links) are globally accessible and permanently stored.
### Asset Schema
The Asset Schema is a detailed specification outlining the properties of an asset and its compatibility with other assets through asset links. These schemas should be stored in a globally accessible and permanent location. Moreover, they need to be registered against specific assets. The Asset Register facilitates the registration of these schemas, allowing Futureverse teams to store them on a dedicated namespace.
### Namespace
In the Asset Register, a namespace is a container for organizing and presenting schemas. It serves as a centralized mechanism to group related schemas together. This organizational approach is crucial for efficient management, preventing naming conflicts, and improving overall code organization. In the context of Futureverse, namespaces play a vital role in grouping schemas for internal use.
## Asset Linking
Asset linking is a fundamental activity within the Asset Register and is executed through transactions. This process is crucial for establishing relationships between different assets. Oracles actively monitor these transactions to ensure that asset links are consistent with the on-chain ownership of assets. This validation guarantees the integrity and accuracy of the linked assets.
## Ownership Resolution
Ensuring accurate ownership information within the Asset Register is paramount. The ownership status of assets correlates directly with user access. This correlation is vital for maintaining the security and integrity of the asset ecosystem. Ownership resolution mechanisms are in place to guarantee that asset ownership aligns with the specified user access.
## Transactions
Transactions are how actions are committed to the Asset Register. Assets are linked via transactions that are executed in an authenticated and unrepeatable manner. Every action, including those involving oracles, must be explicit. This ensures the security and transparency of the Asset Register, preventing unauthorized or duplicate actions.
# Introduction
Source: https://docs.therootnetwork.com/asset-register/introduction
The Asset Register is where you manage assets across applications in the open metaverse.
## Context
The Asset Register is a new ledger system and tool suite that enables developers to establish data parameters for their assets. It is a metadata repository that defines what an asset is, what an asset can do, and the various environments in which an asset can be applied.
Assets in web3 are currently restricted by their linear data composition. Each asset typically only has one corresponding metadata file and there is no way to create connections between assets in disparate ecosystems. Current systems tend to rely on specific chains, hindering asset relationships across different networks. Moreover, they primarily cater to on-chain assets, overlooking off-chain ones. Achieving interoperability for both types of assets across various applications is challenging.
The Asset Register addresses these challenges, and supports interesting use cases:
* Equipping accessories to assets across chains
* Linking user metadata to a collectible to show its provenance
* Managing which collections are compatible with which accessories
* Informing applications about what an object does and what engines it is compatible with
The Asset Register has three components: the Asset Register Core Ledger, the Asset Register API, and the Schema Management System, which sits on top for validation and is the main enabler of interoperability.
## Network Endpoints
When connecting to The Root Network through the API, you can choose to connect to a public web socket or a local node.