Creating A Digital Twin
Last updated
Was this helpful?
Last updated
Was this helpful?
Minting a 'Digital Twin' is conducted once all the required documentation have been created and collected, it is then uploaded to ArWeave immutable storage. Minting is conducted by an OpenChrono employee via the internal backend tooling. A mint queue is in place to ensure that all 'digital twins' are correctly minted.
When an owner/seller sends in a watch, it is authenticated and stored in a vault. These steps generate several documents which are stored on ArWeave for anyone to see.
Additionally, a terms and conditions for every sale is created.
On ArWeave every document is indicated with a unique tx-id. Meaning 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 TimePiecePassport contract. The image below shows an example of the relations :
