VORJ
  • Welcome to VORJ
    • VORJ Smart Contracts
    • Indexer
    • Transaction Executor
    • Contract Deployer
    • Roles & Permissions
    • Organization, Project & Contracts
    • Plans, Resources and Usage
    • NFT Creation Flows
  • Guides
    • Video Guides
    • Written Guides
      • Backend User Guide
      • Frontend User Guide
    • API Pagination
  • Tutorials
    • How to create an account on VORJ
    • Create an organization and project space
    • Create, deploy & mint a fungible token
    • Fungible token utility
      • How to list your fungible token on the official token registry
      • How to manually add your token in the VeWorld wallet
      • How to create a liquidity pool for your fungible token
    • Create, deploy & mint a non-fungible token (NFT)
    • NFT utility
      • How to list your NFT on the official token registry
      • How to list your NFT on WoV
  • Changelog
  • The Legal Bits
  • FAQ
Powered by GitBook
On this page
  • Dynamic Table Flow
  • Metadata Only Flow
  • Media and Metadata Flow

Was this helpful?

  1. Welcome to VORJ

NFT Creation Flows

VORJ offers three distinct NFT creation flows.

PreviousPlans, Resources and UsageNextGuides

Last updated 1 year ago

Was this helpful?

Dynamic Table Flow

This flow is the default approach and provides a dynamic user interface allowing a user to create up to 5 attributes of metadata. The user can provide a collection description and add up to a maximum of 5 attributes across all of the media items. This creation flow is limited to collections that are less than or equal to 20 pieces of media.

Metadata Only Flow

This flow is enabled by uploading a valid metadata json object, see example metadata json object below. There is a required set of fields for the metadata json object to be considered valid.

The following keys are required:

  • tokenId: The unique tokenId for the media item.

  • name: The name of the media item.

  • description: The description of the media item.

edition is an optional field and if present will supersede the tokenId.

Valid values for both tokenId and edition are values that are greater than 0.

[  
  {
    "tokenId": "1",
    "data": {
      "name": "TokenId 1 Name",
      "description": "TokenId 1 Description",
      "edition": "1",
      "attributes": [
        {
          "trait_type": "Trait Type 1 Name",
          "value": "Trait Type 1 Value"
        },
        {
          "trait_type": "Trait Type 2 Name",
          "value": "Trait Type 2 Value"
        }
      ]
    }
  },
  {
    "tokenId": "2",
    "data": {
      "name": "TokenId 2 Name",
      "description": "TokenId 2 Description",
      "edition": "2",
      "attributes": [
        {
          "trait_type": "Trait Type 1 Name",
          "value": "Trait Type 1 Value"
        },
        {
          "trait_type": "Trait Type 2 Name",
          "value": "Trait Type 2 Value"
        }
      ]
    }
  }
]

Media and Metadata Flow

This flow is activated when a user opts into providing a metadata json object as an alternative to using the dynamic table flow. The user must upload a metadata object, following the same requirements and outline as above.

Example of the dynamic flow.