Skip to main content

mQuark Protocol Elements

Concepts

To understand better how mQuark aims to achieve interoperability. Let's step back and look over the landscape of web3 and the quarks from the second concept of our Triple-E principle.

  1. Protocol Elements: Key protocol elements that help these people join together.

Protocol Overview​

There is no easy way for Metaverses, Businesses, or any Entity to know which NFTs have been adopted by which businesses or other platforms. It is essential for businesses to drive NFT adoption and for web3 developers to ride that wave. Only when businesses, Metaverse developers, and customers interconnect will we jump the adoption chasm.

mQuark will address these limitations and challenges through an accompanying SaaS Platform that establishes an interoperability standard or protocol that helps businesses, Metaverses, and game developers create categories of reusable NFTs with their own attached attributes. The smart contract, Developer Portal and APIs will allow developers to follow a common NFT standard, categorise in-game items and attributes, establish a common language among other metaverses, and allow their customers to take their owned NFTs from one Metaverse to another.

A developer from Platfrom A can use the APIs to either read the NFT’s attributes of Platform B or completely reimagine what that object is with their own attributes to attach. In short, a unique Prada shoe sold on their website that came with an accompanying NFT could be represented on the feet of an avatar in one metaverse but could be represented as a picture on the wall in another metaverse.

Schema Templates​

Schema are an EIP721 Standard Templates, that has certain characteristics which makes it inheritable by mQuark entities which are looking to provide users with interoperable world objects.

  • An abstract representation of an object or thing
  • Acts like a blueprint
  • Has a metadata
  • is inheritable by entities for their collections
  • each template has an ID

mQuark Entities​

To become an mQuark Entity, you must first register your business or metaverse with the mQuark Foundation. Registration requires some useful information like name, description, logo, etc. After sending the registration transaction to the mQuark Registry Contract, it will deploy a brand new Entity Contract for your account. And you will be able to manage your collections, funds, and subscriptions from your Entity Contract. You can also use the mQuark dApp to manage your entity.

NFT Collections​

Inheriting from the template ids, also known as Quarks, developers can forge a specific entity collection contract based on their abstract specification and extend it with their entity attributes. While Quarks can be used by developers to understand the base object of the NFT asset e.g. the fundamental abstract form of the asset can be a car, but their interpretation will be unique to their metaverse designs and visuals. In other words, it is up to the platform or entity how they interpret it in the realm of the meta-world.

To simplify, let's walk through another example. Let’s say you have a mQuark NFT, its Template ID is 5 and it represents an abstract shoe object. Wherever you go to a metaverse that supports the Quark protocol, they will already be knowing what your NFT is and how they will have a unique representation of that NFT in their world. This means, your NFT representation will be imported into that metaverse but its visuals may not be exactly the same as the NFT image itself. Because metaverse developers are going to decide how a shoe will look in their world. Depending on the metaverse, they can give you the option to edit the looks of the new bridged item.

Quark Requests

mQuark partners will be able to request templates through the Developer Portal. mQuark Foundation will be extending the Templates based on these requests.

DAO Prospect

The Unbounded DAO will be the major responsible entity for the mQuark Foundation. DAO or Decentralized Autonomous Organization is open to public stakeholders to make decisions about the governance of the protocol.

  • Entity developers create them from Templates,
  • They have Collection IDs like Template IDs
  • You can create as many collections from the same template
  • They have a total supply
  • They can be free or paid
  • If it is paid, it will have a minimum limit price acording to its selected template
  • They can be also be Whilisted
  • Free collections is locked to subscribe to entities
  • Free collections can be unlocked later by paying its template price.
  • There are three type of Metadata creation methods. Static , Limited Dynamic, Dynamic.
  • Static collections consists of only one variation of NFT.
  • Limited collections consist of a limited number of NFT variations, and mint handling is easy for the creator of the collection.
  • Dynamic collections can consist of an unlimited number of NFT variations, however, requires URI signature handling by the creator.
  • Creators can set name, image and attributes.

NFT Metadata​

URI slots are placeholders in an NFT's metadata that can be filled with URIs (Uniform Resource Identifiers) to represent various aspects of an NFT, such as its image or media files. A single NFT can have multiple URI slots, and each slot can be associated with a specific entity. URI slots enable NFT owners to update or change the metadata associated with their NFTs, even after they've been minted.

  • Every entity can have their own metadata slot specification
  • URI slots will be publicly readable, but it is only writable by the owner of the NFT with a valid signature signed by the slot’s owner.
  • Metadata will be readable from the NFT contract itself, and it requires Entity ID and Token ID as parameters to be accessed
  • Slots are added to NFTs while subscribing/selecting a entity

The pictorial representation depicts how interoperability will be made successful for quarks across various metaverses.

Development in progress

This section will be completed.