TimePiece Passport™ Tech

Overview

A token within the TimePiecePassport collection represents the ownership of a watch. The information about this watch is stored in metadata that is linked to this token. The data is stored permanently on ArWeave.

Documents on ArWeave

When someone sends a watch to OpenChrono's Authentication network, it is accurately condition reported and stored in a secure third party vault. Once these steps are complete, OpenChrono collects the documentation and stores it on ArWeave for anyone to see.

Additionally, a Terms-and-Conditions (T&C) document for every sale is created.

On ArWeave every document is indicated with a unique tx-id. This means that if a document needs to be updated, a new document will be uploaded instead with a new tx-id. Uploaded items can be accessed with the following link: https://arweave.net/<your tx id>.

All the documents that are uploaded to ArWeave for a certain token will be combined in a single passport. This passport is used as a representation of the watch and its owner. The passport itself is represented on ArWeave as a JSON file. This metadata links all uploaded documents together. Additionally, this document contains the seller, buyer, token ID, token contract, date, and time. This document is then uploaded and its tx-id is mapped to the minted token in the TimePieceNFT contract. The image below shows an example of the relations.

Example of data storage structure

The correct link for a token can be found by using the tokenURI() function (or its alias getTimePiecePassport()).

Minting

Minting is done after a watch is registered in Payload for the first time. The documents associated with authentication, legal, and storage are first stored in Payload (and consequently uploaded to ArWeave). Next, information about the watch and a description is stored in Payload. All this data is merged together in a single metadata file. When the watch data in Payload is published the NFT is minted and the tx-id of the metadata of linked to the NFT. The NFT is minted to the owner of the watch.

Updating watch data

If any data in the metadata has been updated in Payload (for example a description or the T&C is updated), a new metadata is generated. The tx-id of this newly uploaded metadata is then used to replace the currently linked tx-id to the token in the TimePieceNFT contract.

Metadata format

OpenSea is one of the biggest NFT marketplaces. We want our metadata to be compatible with their format so that data will be properly displayed on different marketplaces. We inherit the OpenSea specification, but we've added attributes that are relevant to TimePiece Passports™, like an array of warranties.

An example is shown below (and can also be accessed here). The corresponding OpenSea listing can be found here.

Last updated

Was this helpful?