Token Utilizing Object Digitization

Abstract

A system, method, and computer-readable storage medium for modeling an object. One method includes receiving, from an application on a user device, a content data set of an object and capture-event parameters of a capture event of the object; generating a three-dimensional (3D) object file based on the content data set, where the 3D object file is a digital twin of the object and corresponds to one or more characteristics of the object; storing the 3D object file and the capture-event parameters in a data repository; generating a token including a metadata object based on broadcasting the 3D object file, the content data set, and the capture-event parameters to a distributed ledger, where the metadata object embeds metadata of the object, a pointer to the capture-event parameters, and a pointer to the 3D object file in the token; and storing the token in a digital wallet address of a wallet storage.

Description

Technical Field

[0001] This implementation generally relates to assets, and more specifically, to tokens.

Background Art

[0002] This disclosure generally relates to assets, and more specifically, to tokens. In a computer network environment such as the Internet, users and entities such as people or companies may desire to create digital assets.

Summary of the Invention

[0003] Some arrangements relate to a system for modeling an object, the system including a data processing system including a memory and one or more processors. The one or more processors are to receive, from an application of a user device, a content data set of an object and capture-event parameters of a capture event of the object, the content data set including duplicate content of the captured object and associated metadata of the object, and to generate a three-dimensional (3D) object file based on the content data set, the 3D object file being a digital twin of the object and corresponding to one or more characteristics of the object, and to store the 3D object file and the capture-event parameters in a data repository, and to generate a token including a metadata object based on broadcasting the 3D object file, the content data set, and the capture-event parameters to a distributed ledger, the metadata object embedding metadata of the object, a pointer to the capture-event parameters, and a pointer to the 3D object file in the token, and to store the token in a digital-wallet address of a wallet storage of the user device.

[0004] In some arrangements, one or more processors are further configured to calculate an amount of payment associated with a curator's royalty according to a token's metadata object in response to receiving a transfer request on a distributed ledger, and allocate the payment to a curator wallet address associated with the curator according to the amount of payment.

[0005] In some arrangements, one or more processors are further configured to extract metadata of an object based on analyzing a content data set and capture event parameters, the metadata including historical data, provenance data, authentication data, and certification data, and store the metadata in a token's metadata object as a digital signature linking the metadata to a 3D object file.

[0006] In some arrangements, one or more processors are further configured to determine additional processing to perform on a 3D object file based on one or more 3D object file parameters, the 3D object file parameters including at least one of resolution, level of detail, file format compatibility, texture mapping, or surface normal adjustment, and regenerate the 3D object file of the object by applying the additional processing to the 3D object file.

[0007] In some arrangements, one or more processors receive a verifiable authentication information request associated with an authenticator from a third-party computing system, analyze the information of the authenticator, grant authority to the authenticator based on cross-referencing it with at least one of the object's metadata or capture events, generate digital identification information linked to the authenticator's identification information, generate verifiable authentication information corresponding to the digital identification information, where the verifiable authentication information includes verifiable data of the object's metadata or capture events, embed the verifiable authentication information into the 3D object file, broadcast the verifiable authentication information to the distributed ledger, and provide the digital identification information to the third-party computing system.

[0008] In some arrangements, multiple digital identification information are each uniquely assigned to each of the multiple authenticators, cryptographically protected, and each of the multiple digital identification information is configured to enable each of the multiple authenticators to digitally sign one or more parts of the object's metadata.

[0009] In some arrangements, one or more processors verify one or more parts of the metadata in response to receiving a combination of digital identification information and digital signature of one or more parts of the metadata.

[0010] In some arrangements, one or more processors are further configured to determine an object authentication agent based on a capture event and multiple environmental information including at least one of the origin of the physical object, the category of the physical object, the value of the physical object, and the rarity of the physical object, collect authentication agent information associated with the authentication agent and including at least one of the agent's identification information, the agent's qualifications, the field of expertise of the agent, the date and time of authentication, and the agent's notes, and update the token metadata object to further include the authentication agent information using a private key corresponding to the digital wallet address of the wallet storage of the user device.

[0011] In some arrangements, the content dataset includes at least one or more captured images, videos, or sounds of the object, the capture event parameters include at least the date, time, location, persons present or involved, and environmental conditions of the capture event, and generating the token includes minting a non-fungible token (NFT) using the object's metadata.

[0012] In some arrangements, one or more processors are further configured to present a 3D object file including adjustable content via an application of the user device, and when a part of the adjustable content is selected, the application is configured to adjust one or more features of the 3D object file.

[0013] In some arrays, broadcasting involves encoding 3D object files, content data sets, and capture event parameters, and signing the encoded 3D object files, content data sets, and capture event parameters with a private key corresponding to the digital wallet address of the user device's wallet storage, and transmitting the signed 3D object files, content data sets, and capture event parameters to a network of nodes participating in the distributed ledger, where the nodes independently verify the 3D object files, content data sets, capture event parameters, and associated signatures to confirm authenticity, integrity, and compliance with the consensus rules of the network of nodes, and including incorporating tokens into new exchange blocks, where the new blocks are added to the existing blockchain within the distributed ledger.

[0014] In some arrangements, it relates to a method for modeling an object. The method includes receiving, by one or more processing circuits, from an application of a user device, a content data set of the object and capture-event parameters of a capture event of the object, where the content data set includes duplicate content of the captured object and associated metadata of the object, and generating, by one or more processing circuits, a three-dimensional (3D) object file based on the content data set, where the 3D object file is a digital twin of the object and corresponds to one or more characteristics of the object, storing, by one or more processing circuits, the 3D object file and the capture-event parameters in a data repository, and generating, by one or more processing circuits, a token including a metadata object based on broadcasting the 3D object file, the content data set, and the capture-event parameters to a distributed ledger, where the metadata object embeds metadata of the object, a pointer to the capture-event parameters, and a pointer to the 3D object file in the token, and storing, by one or more processing circuits, the token in a digital wallet address of a wallet storage of the user device.

[0015] In some arrangements, the method further includes calculating, by one or more processing circuits, an amount of payment associated with a curator's royalty according to the metadata object of the token in response to receiving a transfer request on the distributed ledger, and allocating, by one or more processing circuits, the payment to a curator wallet address associated with the curator according to the amount of payment.

[0016] In some arrangements, the method comprises extracting object metadata by one or more processing circuits based on analyzing content data sets and capture event parameters, the metadata including history data, provenance data, authentication data, and authentication data, and the metadata further including being stored within a metadata object of a token as a digital signature linking the metadata to a 3D object file.

[0017] In some arrangements, the method comprises determining, by one or more processing circuits, additional processing to perform on a 3D object file based on one or more 3D object file parameters, the 3D object file parameters including at least one of resolution, level of detail, file format compatibility, texture mapping, or surface normal adjustment, and further comprising regenerating the 3D object file of the object by applying the additional processing to the 3D object file by one or more processing circuits.

[0018] In some arrangements, the method includes receiving, by one or more processing circuits, a verifiable authentication information request associated with an authenticator from a third-party computing system; authorizing, by one or more processing circuits, the authenticator based on analyzing information of the authenticator and cross-referencing it with at least one of object metadata or a capture event; generating, by one or more processing circuits, digital identification information linked to the identification information of the authenticator; generating, by one or more processing circuits, verifiable authentication information corresponding to the digital identification information, where the verifiable authentication information includes verifiable data of object metadata or a capture event; embedding, by one or more processing circuits, the verifiable authentication information into a 3D object file; broadcasting, by one or more processing circuits, the verifiable authentication information to a distributed ledger; and providing, by one or more processing circuits, the digital identification information to a third-party computing system.

[0019] In some arrangements, a plurality of digital identification information is each uniquely assigned to each of a plurality of authenticators, cryptographically protected, and each of the plurality of digital identification information is configured to enable each of the plurality of authenticators to digitally sign one or more portions of the object metadata.

[0020] In some arrays, the method further includes: determining, by one or more processing circuits, an authentication agent of an object based on a capture event and a plurality of environmental information including at least one of the origin of the physical object, the category of the physical object, the value of the physical object, and the rarity of the physical object; collecting, by one or more processing circuits, authentication agent information associated with the authentication agent and including at least one of the identification information of the agent, the qualification of the agent, the field of expertise of the agent, the date and time of authentication, and the agent annotation; and updating, by one or more processing circuits, a token metadata object to further include the authentication agent information using a private key corresponding to the digital wallet address of the wallet storage of the user device.

[0021] Some arrays are non-transitory computer-readable media that contain one or more instructions stored thereon, which receive, from an application of a user device, a content data set of an object and capture-event parameters of a capture event of the object, where the content data set includes duplicate content of the captured object and associated metadata of the object, and generate a three-dimensional (3D) object file based on the content data set, where the 3D object file is a digital twin of the object and corresponds to one or more characteristics of the object, and store the 3D object file and the capture-event parameters in a data repository, and generate a token including a metadata object based on broadcasting the 3D object file, the content data set, and the capture-event parameters to a distributed ledger, where the metadata object embeds the metadata of the object, a pointer to the capture-event parameters, and a pointer to the 3D object file in the token, and store the token in a digital wallet address of a wallet storage of the user device, and are executable by at least one processor to perform the above.

[0022] In some arrays, additional instructions are stored thereon and are executable by at least one processor, and in response to receiving a transfer request on a distributed ledger, calculate an amount of payment associated with the curator's royalty according to the metadata object of the token, and further allocate the payment to a curator wallet address associated with the curator according to the amount of payment.

[0023] These and other aspects and features of the present implementation will become apparent to those skilled in the art by considering the following description of specific implementations in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

[0025] It will be recognized that some or all of the figures are schematic representations for illustrative purposes. The figures are provided for the purpose of illustrating one or more embodiments and are not to be construed as limiting the scope or meaning of the claims.

[0026] Here, embodiments of the present invention will be described in detail with reference to the drawings. The drawings are provided as exemplary examples of the embodiments to enable those skilled in the art to practice the embodiments and alternatives that are obvious to those skilled in the art. In particular, the following figures and examples are not meant to limit the scope of the present embodiment to a single embodiment, and other embodiments are possible by exchanging some or all of the elements described or illustrated. Further, if certain elements of the present embodiment can be implemented partially or fully using known components, only those parts of such known components necessary for understanding the present embodiment are described, and detailed descriptions of other parts of such known components are omitted so as not to obscure the present embodiment. Embodiments described as being implemented in software should not be limited thereto, and can include embodiments implemented in hardware or in a combination of software and hardware, as will be obvious to those skilled in the art, unless otherwise specifically defined herein, and vice versa. In this specification, embodiments showing a single component should not be considered as limiting, but rather the present disclosure is intended to include other embodiments including a plurality of identical components, unless otherwise specifically stated herein, and vice versa. Further, the applicant does not intend that any term in the specification or claims be considered to have an uncommon or special meaning unless explicitly described as such. Further, the present embodiment includes current and future known equivalents to the known components referred to herein by way of example.

[0027] Generally, this technical solution provides improvements in the fields of photogrammetry, generative modeling, neural radiance fields, Distributed Ledger Technology (DLT), digital identity information, verifiable authentication information, and virtual environments. In some arrangements, the system and method implement generating a digital twin for physical non-digital-native objects, enabling these objects to be digitally represented in a virtual environment or an augmented reality implementation. Further, the system and method implement digital documentation of assets, which potentially includes authentication, appraisal, and title services through the provision of digitally verifiable authentication information. In some arrangements, the information and data of capture events can be recorded on a public distributed ledger, along with the information and data stored within NFT metadata.

[0028] In some arrangements, the system and method implement generating digital twins not only for physical non-digital-native objects but also for spaces and environments, enabling these spaces to be digitally represented in a virtual environment or an augmented reality implementation. This can be particularly beneficial for the purposes of architecture, urban planning, and heritage preservation, as well as for creating immersive virtual experiences for users. By digitizing a space or environment, users can explore and interact with these digital twins in ways that were previously impossible, such as simulating different design layouts, visualizing past changes, or taking virtual tours. Further, the system and method implement digital documentation of the photogrammetry process for these spaces, which potentially includes authentication, appraisal, and title services through the provision of digitally verifiable authentication information. This ensures that the digital twins of the spaces are accurate, trustworthy, and easily traceable back to their real-world counterparts. In some arrangements, the information and data of capture events for these spaces can be recorded on a public distributed ledger, along with the information and data stored within NFT metadata.

[0029] In various arrangements, digital twin objects (or spaces) for creating digital objects can be used in augmented reality implementations, enabling viewing of life-sized digital versions of objects in any environment. Further, NFTs are cryptographic assets on a blockchain with unique identification codes and metadata that distinguish them from each other. In some arrangements, NFTs are associated with and can represent digital native assets such as digital artworks. The present system and method can create a comprehensive solution for digitizing objects while guaranteeing their authenticity and origin using digital twinning and NFTs. By integrating photogrammetry (e.g., or NeRF and AI model generation), distributed ledger technology, digital identification information, and verifiable authentication information, the present system and method propose an improved implementation for filling the gap between the physical (or artificial) and digital domains and creating digital twins for objects.

[0030] Furthermore, the digital twin and NFT implementation forms not only enable objects (e.g., physical or artificial, and hereinafter, for the sake of brevity, when referring to objects, the term "physical" will be used regardless of whether they are physical or artificial) to be digitally represented in virtual environments and augmented reality settings, but also enable secure and transparent recording of capture events, authentication, verification, and other related details. As a result, these implementation forms improve the entire process of creating, managing, and storing digital representations of physical objects, and provide new applications and uses for the management, display, and storage of assets in the digital age. By using digital identification information and verifiable authentication information in conjunction with distributed ledger technology, a method is proposed that does not require secure and administrator-approved documentation for documenting the identification information and proof of actions. Therefore, the systems and methods described herein can provide documentation and help prove the authenticity of physical objects while storing them indefinitely in an immutable digital format, such as recorded on a public distributed ledger or blockchain, including rarity, origin, history, manufacturer, designer, verification, and other notable attributes. In some arrangements, the systems and methods implement a process for 3D digital objects that will be represented and connected in a form compatible with a distributed ledger so that they can be converted into NFTs within an application or online.

[0031] In the current system, there is no comprehensive solution for integrating physical objects into the digital world and leveraging the advantages of distributed ledger technology, which limits the ability to interact seamlessly in a virtual immersive environment. The systems and methods described herein address this gap by providing an integrated process that combines photogrammetry, digital identification information, verifiable authentication information, and distributed ledger technology to create a secure and transparent immutable digital representation of physical objects. By filling this gap, this implementation enables a robust and reliable way to digitize physical objects, verify their authenticity, and preserve their provenance. This not only improves the integration of physical objects into the digital world but also makes it possible to ensure the security and transparency of digital twins using distributed ledger technology. As a result, stakeholders such as collectors, museums, and insurers can access and interact with the digital representations of valuable and rare objects with confidence, knowing that the information is accurate, secure, trustworthy, and up-to-date. Thus, these implementations provide a secure and reliable ecosystem for the preservation and authentication of physical objects in the digital realm, ultimately expanding the scope and possibilities of both the physical and digital realms using virtual immersive environments (i.e., bridging the physical world to the digital world).

[0032] FIG. 1 is a diagram illustrating a system according to the present implementation form. As illustrated as an example in FIG. 1, an exemplary system 100 can include a network 101, a data processing system 102, and a client system 103. The network 101 can be any type or form of network. The geographical scope of the network 101 can vary widely, and the network 101 can be a Body Area Network (BAN), a Personal Area Network (PAN), a Local-Area Network (LAN), for example, an intranet, a Metropolitan Area Network (MAN), a Wide Area Network (WAN), or the Internet. The topology of the network 101 can be of any form and can include, for example, any of point-to-point, bus, star, ring, mesh, or tree. The network 101 can be virtual and can be an overlay network located on top of one or more layers of other networks 101. The network 101 can be of any such network topology known to those skilled in the art that can support the operations described herein. The network 101 can utilize different techniques and protocol layers or stacks, which include, for example, Ethernet protocol, Internet protocol suite (Transmission Control Protocol (TCP) / Internet Protocol (IP)), Asynchronous Transfer Mode (ATM) technique, Synchronous Optical Networking (SONET) protocol, or Synchronous Digital Hierarchy (SDH) protocol.The TCP / IP Internet protocol group can include an application layer, a transport layer, an Internet layer (e.g., including IPv6), or a link layer. The network 101 can be a certain type of broadcast network, a telecommunications network, a data communication network, or a computer network. The data processing system 102 can include a metadata input / output (I / O) controller 110, a token generator 112, a system processor 116, an interface controller 120, an authorization processor 130, and a data repository 150. The client system 103 can include a computing system located remotely from the data processing system 102. The client system 103 can include an interface controller 122 and a metadata processor 160. The third-party device 105 can include a computing system located remotely from the data processing system 102.

[0033] The data processing system 102 can implement an improved architecture that rationalizes and enhances the entire process of using photogrammetry to capture physical objects, verifying their authenticity through the expertise of leading experts in the field (if desired or required), and minting them as distinct NFTs on a publicly distributed ledger or blockchain. This end-to-end architecture leverages the power of verifiable authentication information, enabling experts to securely and transparently prove the authenticity, history, and other relevant attributes of the objects as being correct. By seamlessly integrating photogrammetry, expert authentication, and blockchain technology, the data processing system 102 establishes a robust, transparent, and secure framework for storing, managing, and transacting both physical objects and their digital twins. This improved architecture provides an accurate representation and documentation of valuable objects, fostering trust among collectors, investors, and other stakeholders in the art and collectibles ecosystem.

[0034] The metadata I / O controller 110 can acquire one or more object files containing metadata objects. The metadata I / O controller 110 can communicate with one or more external systems via the network 101 and can acquire one or more object files and / or metadata objects via the network 101. The metadata I / O controller 110 can generate object files and / or metadata objects based on one or more output criteria that can be transmitted, for example, to a computing device including the client system 103 or the third-party device 105. The metadata I / O controller 110 can identify one or more characteristics of the object files. The characteristics can include, for example, data type, output data type, input data type, or any combination thereof. For example, the metadata I / O controller 110 can acquire and identify metadata objects including video, audio, text, any medium, executable programs, or any combination thereof. The metadata I / O controller 110 can transmit metadata objects, object files (e.g., 2D and 3D), or one or more of references or links to one or more metadata objects or object files to the token generator 112. In some arrangements, the object files and metadata objects can be stored within the object storage 152 by the metadata I / O controller 110. In some arrangements, the client system 103 executed by the metadata processor 160 can perform the operation of digital twinning of the captured physical object. In various arrangements, the client system 103 is executed by the interface controller 112 and can provide the captured content data and the metadata of the physical object including the event parameters of the capture event (e.g., when the physical object is captured, as well as details and data regarding the event).

[0035] Generally referring to digital twinning, the metadata I / O controller 110 can receive metadata (e.g., including the content data set of the physical object and the capture-event parameters of the capture event of the physical object). The metadata I / O controller 110 can process a set of images to create a 3D digital twin object file representing the physical object. The metadata I / O controller 110 is implemented to efficiently and accurately generate the 3D digital twin object file and preserve the authenticity, details, and visual characteristics of the physical object. Generally, the metadata I / O controller 110 can include a plurality of sub-circuits or processing circuits configured to execute instructions for performing various tasks of the data processing system 102. However, although the various circuits are described individually, it should be understood that it is possible to combine each circuit or processor to perform various tasks and execute various instructions.

[0036] The metadata I / O controller 110 can include an image input processing circuit configured to receive a set of images that capture different perspectives of a physical object. The image input module may accept various image formats such as JPEG, PNG, or TIFF, and may be adapted to handle images captured by different devices such as cameras, smartphones, or other imaging devices. The metadata I / O controller 110 can include an input processing sub-circuit configured to receive a content data set and capture event parameters from an application of a user device. The content data set can include a set of images that capture different perspectives of a physical object, while the capture event parameters may include information such as capture time, location, and device details. Various image formats such as JPEG, PNG, or TIFF may be accepted, and the input processing sub-circuit can be adapted to handle images captured by different devices such as cameras, smartphones, or other imaging devices.

[0037] The metadata I / O controller 110 can further include a 3D object file generation processing sub-circuit that processes the content data set and the capture event parameters to create a 3D digital twin object file. This sub-circuit can adopt various 3D modeling techniques such as photogrammetry, structure from motion, etc. to generate an accurate and detailed 3D representation of the physical object. The 3D object file generation processing sub-circuit can adopt various feature detection algorithms such as SIFT, SURF, ORB, or other suitable methods to ensure accurate and robust feature detection across different imaging conditions and object types. Further, the metadata I / O controller 110 can further include a metadata generation processing sub-circuit that extracts and processes relevant metadata from the content data set and the capture event parameters. The extracted metadata can be stored in a metadata object and can include information about the physical object such as its dimensions, material properties, and unique identification information, as well as data related to the capture event such as the capture agent, authentication agent, and findings.

[0038] In some arrays, the metadata I / O controller 110 can further include a 3D object file generation processing sub-circuit that processes the content data set and the capture event parameters to create a 3D digital twin object file of the space or environment. This sub-circuit can employ various 3D modeling techniques such as photogrammetry, structure from motion, etc. to generate an accurate and detailed 3D representation of the physical space or environment. The 3D object file generation processing sub-circuit can employ various feature detection algorithms such as SIFT, SURF, ORB, or other suitable methods to ensure accurate and robust feature detection across different imaging conditions and spatial or environmental types. Further, the metadata I / O controller 110 can further include a metadata generation processing sub-circuit that extracts and processes relevant metadata from the content data set and the capture event parameters. The extracted metadata can be stored in a metadata object and can include information about the space or environment such as its dimensions, material properties, and unique identification information, as well as data related to the capture event such as the capture agent, authentication agent, and findings.

[0039] In a specific example, assume that the digital twin is of an art gallery space. The content data set and capture event parameters may include high-resolution images or videos captured from various angles and positions within the gallery. These images or videos will include information about the dimensions of the space, the arrangement and installation of the walls, the layout and design of the floor, and the locations of doors, windows, and other architectural elements. Additionally, the content data set will also capture objects within the space such as artworks displayed on the walls, sculptures installed on pedestals, and any furniture or fixtures present. The metadata extracted from the content data set may include the dimensions of each artwork, the artist name, the production date, and any associated provenance information. Similarly, the metadata regarding sculptures, furniture, and fixtures may include their dimensions, materials, manufacturers, and any relevant historical data. In some arrangements, the metadata generation processing sub-circuit will process this information to create a comprehensive set of metadata objects that describe the physical space and its contents in detail. The 3D object file generation processing sub-circuit will then use the content data set and metadata to construct an accurate and detailed 3D digital twin of the complete art gallery space with all the architectural elements, artworks, sculptures, and furniture that exist within the physical environment. This digital twin enables users to explore and interact with the art gallery in a virtual reality or augmented reality setting, enhancing the experience and understanding of the space and its contents.

[0040] The metadata I / O controller 110 can also include an output processing sub-circuit that stores the generated 3D digital twin object file and its associated metadata in the object storage 152 of the data repository 150. This sub-circuit can save 3D object files in various formats such as OBJ, STL, or GLTF, and can store the metadata as a separate file or embed it within the 3D object file. The output processing sub-circuit can also facilitate sharing, transferring, or exporting the 3D digital twin object file and its metadata to other applications, devices, platforms, or within the data processing system 102. The feature matching processing sub-circuit can be included in the metadata I / O controller 110 to establish correspondences between features detected across a set of input images. The feature matching processing sub-circuit can utilize various matching algorithms such as brute-force matching, Fast Library for Approximate Nearest Neighbor (FLANN)-based matching to establish accurate and reliable feature correspondences. The metadata I / O controller 110 can also include a 3D reconstruction processing sub-circuit that combines the feature correspondences and geometric information from the input images to create a 3D point cloud representing the physical object. The 3D reconstruction processing sub-circuit can implement various 3D reconstruction techniques such as bundle adjustment, multi-view stereo to generate a high-density and accurate 3D point cloud. A mesh generation processing sub-circuit can also be provided within the metadata I / O controller 110 to convert the 3D point cloud into a 3D mesh model that can function as the basis for the 3D digital twin object file. The mesh generation processing sub-circuit can adopt various meshing algorithms such as Poisson surface reconstruction, Delaunay triangulation to create a high-quality 3D mesh that accurately represents the geometric shape and surface properties of the physical object.

[0041] In some arrangements, the metadata I / O controller 110 can further include a texture mapping processing sub-circuit that applies texture information from the input image onto the 3D mesh model, resulting in a realistic and visually consistent 3D digital twin object file. The texture mapping processing sub-circuit can utilize various texture mapping techniques such as projective texture mapping, UV mapping, etc. to ensure proper texture alignment and seamless blending across the 3D mesh model. In some arrangements, the metadata I / O controller (110) can include additional processing sub-circuits or components such as a quality assessment processing sub-circuit for evaluating the accuracy and visual quality of the generated 3D digital twin object file, a user interface processing sub-circuit for providing user interaction and control during the generation process, or a communication processing sub-circuit for interacting with other systems or services such as a distributed ledger (e.g., blockchain storage 156) or an authentication system (e.g., authorization processor 130).

[0042] The metadata I / O controller 110 can receive and process the captured physical objects and associated data from the client system 103 or the third-party device 105. When the metadata I / O controller 110 receives the content data set and the capture event parameters, it starts the photogrammetry process by acquiring multiple overlapping photos of the object taken from various angles. The controller then uses algorithms and computer vision techniques to process these photos and finally generates a detailed and accurate three-dimensional digital representation of the object, known as its digital twin or object file (or 3D object file). Once the digital twin is created, the metadata I / O controller 110 proceeds to integrate the information derived from photogrammetry with a distributed ledger or blockchain technology. This integration process may include creating a unique hash of the digital twin and its metadata, which can include the object's history, origin, and other relevant attributes. The controller then stores this hash along with the metadata on a distributed ledger or blockchain (e.g., blockchain storage 156) to ensure a secure and transparent record of the object's information.

[0043] Photogrammetry can be used as a method for generating a detailed and accurate three-dimensional digital representation of an object, known as its digital twin or object file (or 3D object file), but it should be understood that there are additional arrays that can be implemented. For example, Neural Radiance Fields (NeRF) is a technique that utilizes machine learning to create a continuous 3D representation of a scene from a set of 2D images. The NeRF algorithm can train a neural network to represent the scene as a continuous function, which can then be used to generate new views of the object from different angles. Similarly, other methods such as volume reconstruction, structured light scanning, and time-of-flight imaging can also be employed to generate 3D object files depending on the specific requirements and constraints of the application. When a digital twin is created using photogrammetry or an alternative method, the metadata I / O controller 110 proceeds to integrate the information derived from the 3D reconstruction with distributed ledger or blockchain technology. This integration process may include creating a unique hash of the digital twin and its metadata, which can include the object's history, origin, and other relevant attributes.

[0044] In addition to generating a digital twin and integrating it with distributed ledger or blockchain technology, the metadata I / O controller 110 can also document and record the conditions of the photogrammetry event. This includes information such as date, time, location, and the parties involved in the capture process. The controller ensures that this information is securely and accurately recorded on a distributed ledger or blockchain such as the blockchain storage 156. This immutable record serves as a reliable reference for the digital capture of objects and provides a verifiable and tamper-proof history. By maintaining this comprehensive record, the metadata I / O controller 110 adds an additional layer of trust and transparency to the associated information of the digital twin. Stakeholders such as collectors, investors, and connoisseurs can confidently rely on this recorded data to verify the authenticity and accuracy of the digital twin and its associated metadata, further enhancing overall trust and confidence in the ecosystem of valuable objects and their digital counterparts.

[0045] Generally, the token generator 112 integrated within the distributed ledger of the blockchain storage 156 can mint non-fungible tokens (NFTs) associated with the digital twin. This NFT can include a reference to a metadata object stored on the blockchain or distributed ledger, further strengthening the connection between the digital twin and the attestation granted with the permissions provided by the agent. When the object is converted into a 3D file through photogrammetry (or another process) and the details of its associated capture event are recorded in the distributed ledger or blockchain, the integrated token generator 112 initiates the NFT minting process. During this process, the token generator 112 creates a unique and indivisible NFT on the distributed ledger or blockchain. This NFT functions as a digital certificate of ownership and authenticity for the physical object, effectively linking the digital twin to its real-world counterpart. To ensure that the NFT contains all relevant information related to the object, the token generator 112 embeds relevant details such as the object's history, origin, authentication, and other attributes within the metadata of the NFT. Additionally, the metadata object generated by the token generator 112 indicates the photogrammetry capture event details previously recorded on the distributed ledger or blockchain.

[0046] Looking at the token generator 112 in more detail, the token generator can be integrated into the distributed ledger of the blockchain storage 156 and can generate one or more non-fungible tokens (NFTs) linked to the specific metadata of the object obtained from the metadata I / O controller 110. The object file and the associated metadata object can be stored in the object storage 152. In some arrangements, the metadata I / O controller 110 can generate a 3D object file, a content dataset, and capture event parameters for minting and provide them to the token generator 112. The token generator 112 can generate tokens corresponding to specific metadata objects. In some arrangements, the token generator 112 can obtain existing tokens and assign the existing tokens to specific metadata objects.

[0047] The token generator 112 can generate non-fungible tokens that are unique relative to all other tokens generated by the token generator 112 for identifying object files and metadata objects, fungible tokens that can be generated or replicated any number of times, and semi-fungible tokens that can be generated or replicated a specific number of times that is below or meets a specific replication threshold. One or more fungible tokens or semi-fungible tokens can be associated with, for example, a specific object or the same object. The token generator 112 can access the token storage 154 to determine whether the replication threshold corresponding to a specific threshold is met, and in response to the determination that the replication threshold corresponding to the specific threshold is met, can prevent or defer the generation or replication of tokens that exceed or meet the replication threshold. The token generator 112 can obtain from the metadata I / O controller 110 a 3D object file, a content dataset, and capture event parameters and can store one or more non-fungible tokens, fungible tokens, or semi-fungible tokens on the distributed ledger.

[0048] The system processor 116 can execute one or more instructions associated with the system 100. The system processor 116 can include an electronic processor, an integrated circuit, a sub-circuit, etc. that includes one or more of digital logic, analog logic, digital sensors, analog sensors, communication buses, volatile memory, non-volatile memory, etc. The system processor 116 can include, but is not limited to, at least one microcontroller unit (MCU), microprocessor unit (MPU), central processing unit (CPU), graphics processing unit (GPU), physics processing unit (PPU), embedded controller (EC), etc. The system processor 116 can include memory that is operable to store or stores one or more instructions for operating the components of the system processor 116 and for operating the components operably coupled to the system processor 116. The one or more instructions can include at least one of firmware, software, hardware, operating system, embedded operating system, etc. The system processor 116 or the system 100 can generally include at least one communication bus controller for communicating between the system processor 116 and other elements of the system 100.

[0049] The token generator 112 integrated within the distributed ledger of the blockchain storage 156 can generate one or more smart contracts executable to restrict the output of one or more specific object files based on one or more metadata objects. The system processor 116 can execute, for example, the smart contracts generated by the token generator 112. The token generator 112 can obtain one or more object files and / or metadata objects and can generate a control structure corresponding to the object file or metadata object. For example, the token generator 112 can generate a control structure (e.g., a metadata control structure) for encapsulating a plurality of object files each associated with a specific metadata characteristic. This control structure can restrict access to the object files and / or metadata objects within the control structure, for example, by an encapsulation layer that encrypts all the object files within the control structure using a common encryption method. The encapsulation layer can control the output of a plurality of object files within the control structure by uniformly and simultaneously decrypting the metadata objects according to a common encryption method. The metadata characteristics can include, for example, the type of output, the size associated with the output, or any combination thereof. For example, the metadata characteristics can include an increasing periodic value in the metric of the object file or can include the media type associated with the media object. The media type can include, for example, video, audio, text, or any combination thereof. The token generator 112 can store, within the token storage 154, one or more control structures that encapsulate one or more object files.

[0050] The token generator 112 can generate a smart contract based on one or more tokens and control structures. The token generator 112 can generate a smart contract that includes one or more executable instructions to limit or transmit the output of one or more object files encapsulated within a particular control structure. The token generator 112 can generate a smart contract that can conditionally transmit the output of one or more of the object files in response to the detection of one or more attributes for outputting what is satisfied (and / or verifying the authenticity of at least a portion of the physical asset). The tokens can include one or more non-fungible tokens, fungible tokens, and semi-fungible tokens. The token generator 112 can store the smart contract in the token storage 154 and can link the tokens to the smart contract. The token generator 112 can, for example, publish, post, or add tokens linked to the smart contract to the blockchain, for example, one or more tokens corresponding to the smart contract can be published, posted, or added to the blockchain.

[0051] In some arrays, the token generator 112 can generate alternative (or combined) mechanisms for managing access to and control of the digital twin based on one or more tokens and control structures. In one example, the token generator 112 can create a Decentralized Autonomous Organization (DAO) that governs the rights to use and access digital twin content. The DAO would be composed of token holders who can vote on proposals to modify access conditions or to share revenues generated from the digital twin. In another example, the token generator 112 can implement a multi-signature scheme where multiple parties must provide signatures for the execution of certain actions related to the digital twin. This can include granting access to the digital twin, updating metadata, or transferring ownership. The multi-signature scheme improves the security and reliability of the digital twin management process. Tokens involved in these alternative (or combined) mechanisms can include one or more non-fungible tokens, fungible tokens, and semi-fungible tokens. The token generator 112 can store related data or agreements in the token storage 154 and link the tokens to the implemented mechanisms. The token generator 112 can publish, post, or add tokens linked to a selected mechanism to the blockchain, and can publish, post, or add one or more tokens corresponding to the mechanism to the blockchain.

[0052] The interface controller 120 can link the data processing system 102 to one or more of the network 101, the client system 103, and the third-party device 105 through one or more communication interfaces. The communication interface can include, for example, a specific component of the data processing system 102 or an application programming interface ("API") that is compatible with the data processing system 102. The communication interface can provide a specific communication protocol that is compatible with a specific component of the data processing system 102 and a specific component of the client system 103. The interface controller 120 can be compatible with a specific object file and a metadata object, and can be compatible with a specific object file distribution system corresponding to the specific object file. For example, the interface controller 120 can be compatible with the transmission of video object files, audio object files, image object files, or any combination thereof. For example, the interface controller 120 can be compatible with payment processing transmissions using a protocol that is compatible with payment processing latency and encryption structures.

[0053] The authorization processor 130 can verify one or more tokens against one or more smart contracts to ensure the authenticity and origin of the 3D digital twin object file. By obtaining one or more tokens and comparing them with the tokens required by a specific smart contract, the authorization processor 130 can determine whether a specific token is compatible with a specific smart contract. This determination is made by detecting whether a specific token matches the specific token characteristics associated with a specific smart contract. For example, the authorization processor 130 can identify that a token is compatible with a smart contract by comparing the hash of the token with the hash included in the smart contract.

[0054] In some arrangements, the authorization processor 130 provides an implementation for verifying the authenticity of physical objects captured via photogrammetry by utilizing digital proofs from authorized parties. These parties possess verifiable authentication information associated with digital identification information (e.g., Decentralized IDentifier: DID) that can prove the correctness of their expertise and the legitimacy of their authentication process. This approach ensures a higher level of trust and confidence in the authenticity, origin, and overall value of the object. In some arrangements, the authorization processor 130 generates an authorization instruction based on its determination. In response to the authorization instruction, the authorization processor 130 may provide a control structure, or one or more object files, or a metadata object to the client system 103 or a third-party device 105 by decrypting the encapsulated layer of the control structure.

[0055] Furthermore, the authorization processor 130 can execute a smart contract using a compatible token to read from the object storage 152 a specific object file or metadata for the smart contract, or a reference to a specific object file or metadata. This process ensures that the digital proof of authentication provided by an authorized party is securely and accurately integrated with the 3D digital twin object file, thereby enhancing the overall integrity and reliability of the system. In some arrangements, the authorization processor 130 can verify one or more tokens against one or more smart contracts. The authorization processor 130 can obtain one or more tokens and compare the one or more tokens to the one or more tokens required by a specific smart contract. The authorization processor 130 can detect whether a particular token is compatible with a particular smart contract by detecting whether the particular token matches the particular token characteristics associated with the particular smart contract. For example, the authorization processor 130 can detect that a token is compatible with a smart contract based on comparing the hash of the token to a hash included within the smart contract.

[0056] In some arrangements, the authorization processor 130 can generate an authorization instruction based on one or more determinations and transmit the authorization instruction to another system within the data processing system 102 or from an external source (e.g., to the client system 103 or the third-party device 105). The authorization processor 130 can provide, for example, an object file, an NFT, or one or more metadata objects by decrypting the encapsulation layer of the control structure in response to the authorization instruction. The authorization processor 130 can execute a smart contract using, for example, a compatible token to read from the token storage 154 a specific object file for the smart contract or a reference to a specific control structure.

[0057] The authorization processor 130 can perform one or more actions in response to an authorization instruction generated by the authorization processor 130. The authorization processor 130 can provide, for example, an output from a specific object file within a specific control structure in response to the receipt of a token or a reference to a token. In some arrangements, the process incorporates the use of digital identification information to include various stakeholders who can attest to the correctness of the specific details associated with a photogrammetric capture event, the attributes of an object, and other aspects or features of the digitized physical object. These stakeholders can potentially include experts in the field of the object who can provide support for the authenticity, historical significance, provenance, sales history, and ownership history of the object. Appraisal agents, insurance agents, or other experts may also provide information related to the object.

[0058] In some arrangements, the use of digital identification information enables these agents to provide verifiable authentication information linked to one or more digital identification information, ensuring a high level of trust and confidence in the inspection or examination of objects and the information associated with them. The authorization processor 130 manages this digital identification information, ensuring that the agent's authentication information is secure, trustworthy, and traceable, adding a layer of reliability specifically added to the overall process. This information, including the agent's attestation, can be recorded in conjunction with the photogrammetric capture event (e.g., stored within the metadata). The token generator 112 then creates a non-fungible token (NFT) with corresponding metadata that references this recorded information, further strengthening the connection between the digital twin and the attestation granted with the rights provided by the agent.

[0059] The integration of digital identification information and verifiable authentication information in this process is managed by the authorization processor 130, ensuring a high level of confidence in the authenticity and accuracy of the information surrounding the physical object and its digital twin. This approach promotes transparency and trust in the ecosystem, developing an environment where collectors, artists, and other stakeholders can interact with and explore the world of valuable objects and their digital counterparts with confidence.

[0060] In some arrangements, the object receiving digital capture via photogrammetry is inspected by a major expert in the field of the object. After inspection, the expert authenticator may provide verifiable authentication information linked to digital identification information, proving the presence and approval in the capture event as correct. For example, the digital identification information can be decentralized identification information (DID), which can be unique identification information including information about an individual's identification information. In some arrangements, verifiable credentials (VC) can be used to store and represent machine-readable authentication information. In the above example, the authorization processor 130 can generate a template doc (e.g., a DID document) issued to the user that can add the user's identification information (i.e., where the DID references the DID document).

[0061] In some arrangements, digital identification information can function as unique verifiable authentication information for authenticating and representing users, assets, or entities within a digital environment. In the context of NFTs, digital identification information can be used to associate the creator, owner, or other relevant parties with a digital asset or token. For example, the digital identification information may be a unique alphanumeric code, a public key within a cryptographic key pair, or a blockchain address. These digital identification information can be adopted in various ways to ensure the security and authenticity of transactions involving digital assets such as NFTs. In the case of a royalty payment mechanism, the digital identification information of the legacy account holder (i.e., the entity controlling the private key to the original creator or minting address) can be associated with the NFT. When the NFT is transferred or sold, the smart contract (or code) embedded within the token can automatically calculate the percentage of the transaction value and allocate it as royalties to the legacy account holder. In some arrangements, this process can occur for the initial sale or transfer, as well as all subsequent sales or transfers that use the digital twin as a value transfer mechanism.

[0062] The authorization processor 130 can use a consensus algorithm to record these records safely and transparently and store them on a publicly distributed ledger. The metadata associated with the NFT, created using the 3D digital twin file by the token generator 112, may be readily available for review. Thus, the present system and method enable curators of rare and valuable vintage objects to document and monetize their curation work by digitally recording the objects they curate using the disclosure of the NFT digital twin and the metadata. Further, these curation systems can be monetized by incorporating royalty fees programmed into the NFTs that can be paid upon transfer of the tokens. This arrangement incentivizes and rewards curators for their contributions to the preservation, study, and sharing of valuable objects, and develops a vibrant ecosystem for collectors, artists, and connoisseurs alike.

[0063] In some arrangements, unique physical characteristics of an object, such as a grain pattern, are recorded via photogrammetry and utilized as an authenticator to document distinct features of the object within the associated NFT minted by the token generator 112 to a distributed ledger (e.g., blockchain storage 156). This approach, managed by the authorization processor 130, ensures a high level of security and trust in the authenticity of the digital twin, bridging the gap between the physical and digital environments while preserving the object's intrinsic value and history.

[0064] In some arrangements, the unique physical properties of an object, such as a wood grain pattern, a fabric pattern, a surface texture, or other distinctively different features, are recorded via photogrammetry and used as an authenticator to document the unique attributes of the object within an associated NFT minted by the token generator 112 to a distributed ledger (e.g., blockchain storage 156). By capturing these essential properties, the system can provide a higher level of detail and accuracy in the representation of the physical object as a digital twin. In some arrangements, the authorization processor 130 manages the authentication process to ensure that the captured data accurately represents the specific characteristics of the object. This processor analyzes the data from the photogrammetry capture, extracts unique features, and creates a digital signature or fingerprint that is inherently linked to the object. This digital fingerprint becomes an integral part of the metadata associated with the NFT and functions as a reliable and robust authenticator for the digital twin (e.g., 3D object file).

[0065] The authorization processor 130 may also use machine learning algorithms to analyze the unique features and generate an even more precise and reliable digital representation. These algorithms can be trained to recognize specific patterns or characteristics within the data, further enhance the authentication process, and increase the level of security and trust in the authenticity of the digital twin. Once the digital fingerprint is created and linked to the NFT, verification of the original object can be performed at any point in the future, providing a sure connection between the physical object and its digital representation. This approach, managed by the authorization processor 130, ensures a high level of security and trust in the authenticity of the digital twin, bridging the gap between the physical and digital realms while preserving the object's inherent value and history.

[0066] Furthermore, incorporating unique physical characteristics into the metadata of an NFT can serve as a deterrent against potential forgery or fraud in the art world and collectibles market. The ability to verify the authenticity of a digital twin against its physical counterpart with such a high degree of accuracy will make it increasingly difficult for malicious actors to deceive collectors and investors. In addition to ensuring authenticity, using unique physical characteristics as an authenticator within the NFT framework promotes transparency and accountability within the ecosystem. Stakeholders, including artists, collectors, and investors, can trust the digital twins they interact with and know that the associated NFTs are securely linked to their physical counterparts. This increased trust will develop an improved and robust environment for the exchange, provenance, and preservation of valuable objects and their digital representations.

[0067] The data repository 150 can store data associated with the system 100. The data repository 150 may include one or more hardware memory devices for storing binary data, digital data, and the like. The data repository 150 may include one or more electrical components, electronic components, programmable electronic components, reprogrammable electronic components, integrated circuits, semiconductor devices, flip-flops, arithmetic units, and the like. The data repository 150 may include at least one of a non-volatile memory device, a solid-state memory device, a flash memory device, and a NAND memory device. The data repository 150 may include one or more addressable memory regions disposed on one or more physical memory arrays. The physical memory array can include, for example, a NAND gate array disposed on at least one of a particular semiconductor device, an integrated circuit device, and a printed circuit board device. The data repository 150 may include object storage 152, token storage 154, and blockchain storage 156.

[0068] In some arrangements, the data repository 150 includes a plurality of databases generated and stored by objects that have undergone the processes or methods described herein. The databases can give rise to an insurable asset pool and provide the owner of the object with the ability to obtain insurance for those items of value. By creating such databases, a reliable and secure source of information regarding these objects can be provided, streamlining the insurance process and providing greater confidence to both insurers and insureds. For example, in relation to the insurance process, a decentralized autonomous organization (DAO) including the owner of the object may be implemented. In this way, it is ensured that the objects documented and recorded within the data repository 150 can be managed in a mutually styled manner, developing a sense of community and shared responsibility among members. Decentralized organizations can utilize the power of blockchain and consensus algorithms to propose claims and dispute resolutions while ensuring transparency, efficiency, and trust in the decision-making process.

[0069] In some arrangements, the information recorded about an object can be stored within the metadata of a 3D object file and will be associated with a non-fungible token (NFT) created using the 3D digital file. To facilitate the process of capturing the object and creating a digital twin, the interface controller 120 can execute a number of API calls, including those for photo-stitching software to create a digital 3D object file through photogrammetry. Further, the interface controller 120 can execute API calls to a decentralized ledger or blockchain to record the capture data and mint the NFT.

[0070] To further enhance the transparency and reliability of the history of an object, additional relevant information is recorded on the blockchain storage 156 and / or stored within the object storage 152, which is then referenced within the metadata of the NFT. This set of data may include, but is not limited to, the parties involved in implementing the intake of the object, the date and time of intake, the date and place of manufacture, the manufacturer and designer, materials, condition reports, origin and previous ownership, previous repairs or modifications, historical compliance, authentication, and sales history. By including this rich information within the metadata of the NFT and linking it to a distributed ledger, the present disclosure provides a robust, transparent, and secure method for storing, managing, and trading physical objects and their digital twins. This comprehensive approach ensures that all relevant data is easily accessible, verifiable, tamper-proof, and develops trust and confidence among collectors, investors, and other stakeholders in the art and collectibles ecosystem.

[0071] The object storage 152 can store object files, also known as digital twins, generated through the photogrammetry process and other related content data sets, which include captured images, metadata, and capture event parameters of the physical object's capture event. The object storage 152 can accommodate object files and content data sets associated with the data processing system 102, the client system 103, the third-party device 105, or any combination thereof. The object storage 152 can be implemented to maintain a secure and organized repository of object files, ensuring that the digital twins are easily accessible, verifiable, and tamper-proof. The content data sets stored within the object storage 152 include information about the physical objects, such as their unique physical characteristics, origin, authentication, identification, status reports, and other related metadata. This collection of data can be used to establish trust and confidence in the authenticity and accuracy of the digital twins and their corresponding physical objects.

[0072] In addition to storing object files and content data sets, object storage 152 maintains a record of capture event parameters associated with the capture events of each physical object. These parameters can include the date and time of the capture event, the location, the device used, the individual or organization responsible for the object's ingestion, and other relevant details. Object storage 152 can be configured to efficiently manage and organize the stored object files, content data sets, and capture event parameters, enabling easy search and access as needed. Object storage 152 can also include object metadata on a distributed ledger or blockchain (e.g., blockchain storage 156), including, but not limited to, the date and time of object ingestion, capture agent identification information, authentication agent identification information and comments, appraisal agent identification information and comments, previous ownership records, related historical data, previous sales records, and other information considered important for the description of the object.

[0073] Token storage 154 can store one or more NFTs, fungible tokens, and semi-fungible tokens, along with their corresponding addresses indicating links to their respective tokens. Token storage 154 can accommodate NFTs, fungible tokens, and semi-fungible tokens associated with data processing system 102 or any of its components, client system 103 or any of its components, third-party device 105 or any of its components. These tokens can represent various aspects of physical objects or their digital twins, including the unique physical characteristics, origin, authentication, verification, and other relevant metadata of the objects. Token storage 154 also maintains a record of digital fingerprints or unique authenticators derived from distinct features of the objects, to be managed by authorization processor 130. These authenticators are securely linked to the corresponding NFTs, ensuring that the digital twins maintain a robust connection to their physical counterparts. By storing these authenticators along with the tokens, token storage 154 provides an additional layer of security and trust in the authenticity and origin of the digital twins.

[0074] Furthermore, the token storage 154 can store information about various stakeholders involved in the authentication, verification, and curation processes. This information, captured through verifiable authentication information linked to digital identification information, is securely linked to each NFT, providing a comprehensive and transparent record of the experts involved in the object's history and its evaluation. In some arrangements, the token storage 154 also maintains a record of any transaction or transfer, including NFTs, fungible tokens, and semi-fungible tokens. This transaction history provides insights into the market value of the object, changes in ownership, and other related financial aspects, contributing to a more transparent and trustworthy ecosystem for collectors, artists, and investors alike. By storing and managing various types of tokens and their associated data, the token storage 154 can store, manage, and trade digital twins.

[0075] The blockchain storage 156 can include a distributed ledger technology (DLT) and a ledger configured to store non-fungible tokens (NFTs) and smart contracts associated with a particular object file or digital twin. The blockchain storage 156 provides a secure and transparent distributed repository for NFTs, smart contracts, and metadata associated with digital twins and their corresponding physical objects. This storage is designed to maintain the integrity and immutability of the stored data, ensuring trust and confidence in the authenticity and accuracy of digital twins and their associated information. The blockchain storage 156 can be configured to accommodate various types of distributed ledger technologies, including, but not limited to, blockchains, directed acyclic graphs (DAGs), and other distributed data structures.

[0076] The NFTs stored within the blockchain storage 156 represent unique digital representations of physical objects and their associated digital twins. These tokens are linked to object files and corresponding metadata, providing a secure connection between the digital and physical realms. NFTs can function as digital certificates of authenticity, ownership, and provenance, enabling seamless and secure transactions and transfers of ownership within the ecosystem. The smart contracts stored within the blockchain storage 156 govern the rules and conditions associated with the NFTs and their corresponding digital twins. These programmable scripts can automate various processes and actions such as royalty payments, access control, and verification of digital identification and authentication information. The blockchain storage 156 can be organized and structured to enable efficient search and access to the stored NFTs and smart contracts.

[0077] The blockchain storage 156 can store one or more smart contracts and corresponding addresses for a particular smart contract indicating a link to the corresponding smart contract. The control structure storage 158 can store one or more control structures and corresponding addresses for a particular control structure indicating a link to the corresponding control structure, as well as the object files, metadata, and corresponding addresses included therein. The blockchain storage 159 can store one or more blockchains linked to one or more smart contracts, tokens, control structures, or metadata objects by the corresponding addresses for a particular smart contract, token, control structure, or metadata object indicating a link to a particular blockchain.

[0078] The interface controller 120 can link the client system 103 and the third-party device 105 to one or more of the network 101 and the data processing system 102 via one or more communication interfaces. The communication interface can include, for example, a specific component of the data processing system 102 or an application programming interface (「API」) compatible with the data processing system 102. The communication interface can provide a specific communication protocol compatible with a specific component of the data processing system 102 and a specific component of the client system 103. The interface controller 120 can be compatible with specific object files and metadata (including, for example, content data sets and capture event parameters), and can be compatible with a specific object file distribution system corresponding to the specific object files and metadata objects. For example, the interface controller 120 can be compatible with the transmission of image metadata, audio metadata, video metadata, or any combination thereof. For example, the interface controller 120 can be compatible with payment processing transmissions using a protocol compatible with payment processing latency and encryption structures. The communication interface of the client system 103 can be compatible with the communication interface of the data processing system 102 to perform one-way or two-way communication between the interface controllers 120.

[0079] The metadata processor 160 of the client system 103 can execute one or more actions in response to an authorization instruction generated by the authorization processor 130. The metadata processor 160 can receive an output from a specific object file or NFT within a specific control structure, for example, in response to receiving a transmission by the interface controller 122 based on a control structure or a reference to a control structure.

[0080] One or more third-party devices 105 may be used by a third party having a relationship with the client system 103 or the data processing system 102 (e.g., a vendor, customer, entity, supplier, etc.) to perform various actions and / or access various types of data, and some of the various types of data may be provided via the network 101. As used herein, the term "third party" may refer to an individual who operates one or more third-party devices 105 while interacting with resources or data via the third-party devices 105. The third-party devices 105 may access the website (e.g., using a browser), access the Internet (e.g., using a mobile application such as a decentralized application (dApp)) to provide services, supply products, and electronically transmit data (e.g., exchange requests, attributes) to the data processing system 102 and receive and / or transmit any other type of data (e.g., geographical location data of digital or physical assets, environmental data of digital or physical assets).

[0081] In some arrangements, the third-party device 105 can be configured to collect environmental data and provide it to the data processing system 102. In various arrangements, the third-party device 105 can also potentially be used to electronically transmit data to the client system 103 and can be configured to receive and / or transmit any other kind of data. For example, the third party may be a supplier of software applications installed on physical assets. In another example, the third party may be a supply chain or logistics company that transfers physical and digital assets. The third-party device 105 (which may also be referred to herein as a "computing system") can be a mobile computing device, a desktop computer, a smartphone, a tablet, a smartwatch, a smart sensor, or any other device configured to receive and display content (such as mobile applications such as web pages, decentralized applications (dApps), etc.) and facilitate interaction with the content. The third-party device 105 can also potentially include input / output circuitry for communicating data to the data processing system 102 and the client system 103 via the network 101. In some arrangements, each third-party device 105 can have a digital wallet address or can exchange (e.g., receive or transmit) alternative or non-alternative value (such as cryptocurrency, digital currency, stocks, collateral, loans, certificates of rights, etc.).

[0082] In a particular arrangement, the third-party device 105 can be utilized by various stakeholders who can attest to the correctness of specific details associated with a photogrammetry capture event, such as an expert in the field of the object, an appraisal agent, or an insurance agent. These stakeholders may provide digital identification information (e.g., DID) used to confirm their involvement, expertise, and authenticity. Examples of such events include verifying the authenticity of an object, assessing its historical significance, confirming its origin, evaluating the condition of the object, and documenting the ownership history of the object. The digital identification information can guarantee a high level of trust and credibility in the information provided by these stakeholders as it can securely attest to the inspection or examination of the object and related details as being correct. By utilizing the third-party device 105, these various stakeholders can efficiently collaborate to contribute to the capture event and seamlessly integrate their inputs into the overall process. The third-party device 105 can be configured to receive the digital identification information and other related data and transmit them to the data processing system 102, the client system 103, and the token generator. This facilitates a secure and transparent record of stakeholder attestation and involvement in the photogrammetry capture event, as well as the subsequent minting of associated NFTs on a distributed ledger.

[0083] To securely generate digital identification information and provide it to the data processing system 102, the third-party device 105 may implement various encryption techniques and protocols. For example, the third-party device 105 may use a Public Key Infrastructure (PKI) to generate a pair of public and private keys for the involved parties. The private key will be securely stored on the device and will maintain confidentiality, while the public key will be shared with the data processing system 102 and other related entities. During a photogrammetric capture event, the third-party device 105 may use the private key to digitally attest or sign a document, which may include the involvement of the parties, expertise, and any relevant information associated with the object. This digital signature serves as proof of authenticity and guarantees that the digital identification information and associated information have not been tampered with and are trustworthy.

[0084] When the data processing system 102 receives a digitally signed attestation, it can verify the signature using the public key of the party, thereby confirming the integrity of the provided digital identification information and associated data. This verification process ensures that the information received from the third-party device 105 has been securely transmitted and originated from a trustworthy source, maintaining the overall integrity of the system. By leveraging encryption techniques and secure communication protocols, the third-party device 105 can effectively generate digital identification information and provide it to the data processing system 102, maintaining the integrity of the information and developing a secure and trustworthy environment for all stakeholders involved in the capture and preservation of valuable objects and their digital twins.

[0085] Now refer to FIG. 2, a flowchart of a method 200 for modeling an object according to this implementation. At least the exemplary system 100 can implement the method 200 according to this implementation.

[0086] In the overview of method 200, at block 210, one or more processing circuits (e.g., data processing system 102) can receive the content data set of an object and the capture-event parameters of a capture event. At block 220, one or more processing circuits can generate a three-dimensional (3D) object file. At block 230, one or more processing circuits can generate a token including a metadata object based on a broadcast. At block 240, one or more processing circuits can generate a talk including a metadata object based on a broadcast. At block 250, one or more processing circuits can store the token in the digital wallet address of wallet storage. Depending on a particular sequence, additional, fewer, or different operations may be performed. In some embodiments, some or all of the operations of method 200 may be performed by one or more processors executing on one or more computing devices, systems, or servers. In various embodiments, each operation may be rearranged, added, deleted, or repeated.

[0087] Referring generally to method 200, this provides improvements for auditing, inventory management, verification of insured interests, preservation of objects for posterity, and improving access to rare and valuable objects. By maintaining a safe and trusted record of physical objects, stakeholders can rely on the information provided, knowing that it is accurate, up-to-date, and has anti-tampering features. The advantages of method 200 include the integration of virtual environments and augmented reality using rare and valuable physical objects. Many of these objects, such as artworks stored in a secure location and not on display in museums or galleries, may previously have been inaccessible to a wider range of customers. Through the creation of digital twins in the form of NFTs, users can interact with these objects in an improved way, opening up new possibilities for the exploration, education, and appreciation of cultural heritage and history. Furthermore, method 200 enables users to experience rare and valuable objects remotely, developing global collaboration and knowledge sharing. By creating digital twins of physical objects, this technology enables people around the world to access, study, and analyze these items in a virtual environment. This improved accessibility can lead to opportunities for discovery, insight, and research, developing a deeper understanding and appreciation of the cultural heritage we share.

[0088] In some arrangements, the current owner or minting party of a physical object is given the opportunity to define the royalty to be paid upon transfer of the NFT, which represents the digital twin of the physical object. This feature enables the creator or owner to benefit from future exchanges involving the object and ensures that they receive ongoing compensation for their work or investment. The royalty mechanism incentivizes the continued support and development of the digital twin ecosystem and promotes a sustainable and fair environment for artists, collectors, and other stakeholders involved in the creation, preservation, and exchange of valuable physical objects and their digital counterparts. Additionally, method 200 facilitates the creation of a more transparent provenance and authentication process for physical objects. By leveraging the power of the blockchain, the disclosed method can track the entire life cycle of a physical object from its creation to its current ownership. This level of transparency helps reduce fraud and forgery in the art and collectibles worlds and enhances market trust and confidence for both buyers and sellers.

[0089] In block 210, one or more processing circuits can receive, from an application of a user device, a content dataset of a physical object and capture-event parameters of a capture event of the physical object, the content dataset including duplicate content of the captured physical object and one or more associated characteristics and histories of the physical object. In some arrangements, the content dataset can be obtained through a photogrammetry process that includes capturing multiple overlapping images, videos, or audio of the physical object from various angles and viewpoints. This dataset includes detailed information about the unique characteristics of the object, such as texture, color, pattern, and dimensions, as well as associated histories, provenances, and any other relevant attributes.

[0090] In some arrangements, the capture event parameters provide context for the digital representation of a physical object, including information such as the date and time of the capture event, the location where the capture occurred, the parties involved in the capture event (e.g., an expert, an authentication agent, or a device operator), the environmental conditions during capture (e.g., lighting, temperature, humidity), and the equipment and settings used to capture the content data set (e.g., camera model, lens, resolution, exposure settings). Additionally, the capture event parameters may include any pre - processing steps or calibration data used to ensure the accuracy and reliability of the captured content data set. The pre - processing steps can include lens distortion correction, image alignment, color balance, and other necessary adjustments. The calibration data may include information about the spatial relationships between the camera, reference objects, or markers used during the capture event to improve the precision of the digital representation.

[0091] In block 210, one or more processing circuits can receive, from an application of a user device, a content data set of an object and capture event parameters of the capture event of the object, where the content data set includes duplicate content of the captured object and associated metadata of the object. In some arrangements, the content data set can be obtained through a photogrammetry process, which includes capturing multiple overlapping images, videos, or audio of the object from various angles and viewpoints. This data set includes detailed information about unique characteristics of the object such as texture, color, pattern, and dimensions, as well as associated metadata, which includes history, origin, and any other relevant attributes.

[0092] In some arrays, the capture event parameters provide context for the digital representation of the object, including information such as the date and time of the capture event, the location where the capture was taken, the parties involved in the capture event (e.g., an expert, an authentication agent, or a device operator), the environmental conditions during capture (e.g., lighting, temperature, humidity), and the equipment and settings used to capture the content data set (e.g., camera model, lens, resolution, exposure settings). Additionally, the capture event parameters may include any pre - processing steps or calibration data used to ensure the accuracy and reliability of the captured content data set. The pre - processing steps can include lens distortion correction, image alignment, color balance, and other necessary adjustments. The calibration data may include information about the spatial relationships between the camera, reference objects, or markers used during the capture event to improve the precision of the digital representation.

[0093] In block 220, one or more processing circuits generate a three-dimensional (3D) object file based on the content data set, and the 3D object file functions as a digital twin of the object and corresponds to one or more characteristics of the object. Creating the 3D object file involves processing and reconstructing the content data set captured using algorithms and techniques for extracting depth information by stitching together overlapping images, videos, or audio to form a precise and accurate digital representation that closely corresponds to unique characteristics of the object, such as shape, size, texture, and color. The 3D object file can be linked so that it can be configured to present an image or video of the physical object in response to a selection by an application on a user device, and the link destination can be a destination or pointer to a storage location of a metadata object (stored, for example, in token storage 154). In some arrangements, one or more processing circuits can generate one or more 3D object files according to the content data set and capture event parameters. One or more processing circuits can receive, collect, or obtain metadata of the physical object, including, but not limited to, video of the physical object, scannable codes, audio, text, any media or digital representation, a pair of public and private keys, an executable program, or any combination thereof.

[0094] To create a 3D object file that functions as a digital twin of an object, the processing circuit can utilize algorithms and techniques for processing and reconstructing the captured content dataset. This process includes stitching together overlapping images, videos, or audio and extracting depth information to form a precise and accurate digital representation that closely corresponds to the unique characteristics of a physical object, such as shape, size, texture, and color. During block 220, the processing circuit can also perform optimizations, compressions, or other post-processing techniques on the 3D object file to improve its visual quality, reduce its file size, or enhance its compatibility with various platforms and applications. These optimizations ensure that the digital twin is efficiently stored, transmitted, and displayed across different systems and devices while maintaining its accuracy and fidelity. By generating the 3D object file, block 220 creates a digital twin that accurately represents the physical object and its associated information, laying the foundation for subsequent tokenization and blockchain integration.

[0095] As used herein, "smart contract control structures", "metadata control structures", and "control structures" may be computer programs (also known as programs, software, software applications, scripts, or code) configured to create a single control structure for each metadata object by combining one or more attributes of physical or digital assets. In some arrangements, one or more processing circuits can implement and execute control structures for outputting, adding, or updating metadata objects of one or more tokens to include one or more metadata, attributes, and conditions (such as smart contracts), fields, values, etc. Control structures can be described in any form of programming language, including compiled or interpreted languages, and / or declarative or procedural languages, and can be deployed in any form, including as a stand-alone program or as other units suitable for use in a circuit, component, subroutine, object, or computing environment. Metadata objects can correspond to files in a file system, but may not necessarily do so. Metadata objects can be stored within a portion of a file that holds other programs or data (such as one or more scripts stored within a markup language document), within a single file dedicated to the token, or within multiple cooperating files (such as files storing one or more subsystems, subroutines, or portions of code). Control structures can be deployed to execute on one computer, or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network. The processes and logical flows described herein can be implemented by one or more programmable processors executing one or more control structures (or computer programs) that perform actions by operating on input data.

[0096] As used herein, the term "smart contract" generally refers to self-executing code (e.g., in a ledger network or other system) that is executed when a set of conditions agreed upon by the parties to the smart contract are met. The figures and the specification generally discuss using smart contracts on 3D object files or metadata objects associated with physical objects, but the systems, methods, and apparatuses disclosed herein can also be used for a plurality of types of non-fungible assets or fungible assets, including but not limited to, goods, common stock, options, dollar bills, fiat currency, digital currency, certificates of interest, leases, wills, other negotiable instruments, non-smart contracts, traditional legal contracts, financial payments, taxes, and other types of non-fungible assets or fungible assets used and exchanged by the parties. The parties to a smart contract for an NFT or other type of non-fungible asset or fungible asset can be individuals, agents, companies, organizations, entities, providers, etc.

[0097] In another arrangement, one or more processing circuits can transform an object artificially generated from human or animal intellectual understanding to generate a 3D object file. This transformation can include interpreting and processing the descriptions, concepts, or ideas provided by a human or animal (at block 210) and using algorithms and techniques to create a digital representation of the object based on the provided information. The generated 3D object file can function as a digital twin of the artificially created object, reflecting unique characteristics such as the shape, size, texture, and color envisioned by the human or animal. In this arrangement, one or more processing circuits can generate a 3D object file by utilizing natural language processing, machine learning, and computer vision techniques to interpret and process the input from a human or animal. These techniques can be used to transform the intellectual understanding into a digital representation that closely corresponds to the unique characteristics of the envisioned object. The processing circuits can also perform optimizations, compressions, or other post-processing techniques on the 3D object file to improve its visual quality, reduce its file size, or enhance its compatibility with various platforms and applications. These optimizations ensure that the digital twin is efficiently stored, transmitted, and displayed across different systems and devices while maintaining its accuracy and fidelity. By generating a 3D object file based on the intellectual understanding provided by a human or animal, this arrangement creates a digital twin that accurately represents the envisioned object and its associated information, laying the foundation for subsequent tokenization and blockchain integration.

[0098] For example, an artist may conceptualize a unique sculpture in their mind but has not yet physically created it. To convert this intellectual thought into a 3D object file, the artist first describes the envisioned sculpture in detail and may provide information about its shape, size, texture, color, and other relevant characteristics. One or more processing circuits will then receive this description, possibly in the form of text, voice input, or a rough sketch. Utilizing natural language processing, machine learning, and computer vision techniques, the processing circuits interpret and process the artist's input and extract important information about the envisioned sculpture. These techniques will help the processing circuits create a digital representation of the sculpture based on the provided information. The generated 3D object file functions as a digital twin of the sculpture envisioned by the artist while reflecting the unique characteristics described by the artist. By converting the intellectual thought into a 3D object file, the artist can then use this digital representation for various purposes such as tokenization, virtual exhibition, or as a reference for creating a physical sculpture.

[0099] In this example, one or more processing circuits can generate a 3D object file by utilizing natural language processing, machine learning, and computer vision techniques to interpret and process inputs from humans or animals. These techniques can be applied in various ways to facilitate the conversion of intelligent thought or description into a 3D object file. Natural language processing (NLP) techniques can be used to analyze and understand text or verbal descriptions provided by humans or animals. For example, an artist might describe an envisioned sculpture using specific terms related to its shape, size, color, or texture. The processing circuit would then use NLP algorithms to extract important information from these descriptions, such as identifying relevant objects, attributes, and the relationships between them. This parsed information can function as a basis for generating a 3D object file. Machine learning (ML) techniques can be utilized to create predictive models and identify patterns within the provided data. For example, based on the information extracted from NLP analysis, the processing circuit could apply ML algorithms to generate a parametric model that represents the artist's vision. This model can be iteratively refined taking into account feedback from the artist or other input sources to improve the accuracy of the generated 3D object. Computer vision techniques can be implemented to further refine the 3D object file by analyzing and processing any visual input from humans or animals, such as sketches or reference images. The processing circuit can employ image recognition and feature extraction methods to identify important elements in the visual input and incorporate them into the 3D object file. This can help ensure that the generated digital representation closely matches the artist's intended design.

[0100] In an alternative (or combined) example, the artist may be connected to a neural or brain-computer interface (BCI) system (e.g., part of the interface controller 120) that can directly interpret their thoughts. The artist may be envisioning a unique sculpture in their mind, but the BCI system will capture the brain signals associated with those creative thought processes. These captured signals are then analyzed and decoded by one or more processing circuits that utilize advanced machine learning algorithms and neural decoding techniques to interpret the artist's thought patterns and extract important features of the envisioned sculpture, such as its shape, size, texture, and color. Once the relevant information is extracted from the artist's brain signals, the processing circuits will generate a 3D object file that represents the artist's intellectual thoughts as a digital twin of the envisioned sculpture. This digital representation reflects the unique characteristics the artist had in mind and enables it to be used as a reference for further refining or modifying the digital sculpture, tokenizing it, or creating a physical piece. By connecting the artist to the BCI system, the process of converting intellectual thoughts into a 3D object file becomes more direct, allowing for a seamless transition from the artist's mind to a tangible digital representation.

[0101] In another example related to the level of an asset, an auto - photographed baseball becomes a top - level digital asset with some support files, forming a complete package of information that provides context, authenticity, and provenance. A 3D object file representing the auto - photographed baseball is generated and associated with a unique non - fungible token (NFT) (generated at block 240). This NFT functions as a gateway to access all related information, which includes the 3D object file, and other support files such as a photo of Babe Ruth signing the baseball, a video of the signing event, and any other relevant documents. To enhance the quality of the digital representation of the auto - photographed baseball, capture - event parameters are also recorded during the digitization process. These parameters can include a timestamp, location data, and the signatures of the parties involved in the digitization, examples of which are the archaeologist who discovered the bone or an expert who authenticated the signature on the baseball. In addition to the main 3D object file, other multi - media files can be included to provide additional context and support the authenticity of the digital asset. For example, a photo of the doctor holding the auto - photographed baseball or a document verifying the origin of the baseball can be added to the collection of associated files. These supplementary materials contribute to the overall value of the digital asset, making it more desirable and meaningful to collectors, investors, and enthusiasts.

[0102] In the context of an example of an automatically photographed baseball, one or more processing circuits can generate a three-dimensional (3D) object file based on a content data set, and the 3D object file functions as a digital twin of the baseball and corresponds to one or more characteristics of the baseball, such as its shape, size, texture, and color. In this scenario, multiple levels of digital assets may be involved, including the primary baseball asset, a handwritten signature on the baseball, and any other associated assets such as a certificate of authenticity and a photograph of Babe Ruth signing the baseball. To create a 3D object file for each of these assets, one or more processing circuits will process and reconstruct the captured content data set using algorithms and techniques to stitch together overlapping images, videos, or audio and extract depth information. This results in a precise and accurate digital representation of the assets that closely corresponds to their unique characteristics. The 3D object files for each asset can be linked together, and each link functions as a destination or pointer to the storage location of the corresponding metadata object (stored, for example, within token storage 154). This enables the presentation of an image or video of the physical object in response to a selection by an application on a user device.

[0103] In another example related to the level of assets, historical sites such as Machu Picchu become top-level digital assets with some supporting files, forming a complete package of information that provides context, historical background, and cultural significance. A 3D object file representing Machu Picchu is generated and associated with a unique non-fungible token (NFT) (generated at block 240). This NFT functions as a gateway to access all relevant information, which includes the 3D object file, as well as other supporting files such as photos of the historical site, videos of archaeological excavations, and any other relevant documents. To enhance the quality of the digital representation of Machu Picchu, capture event parameters are also recorded during the digitization process. These parameters can include a timestamp, location data, and the signatures of those involved in the digitization, such as archaeologists, historians, or experts in cultural heritage preservation.

[0104] In the context of the Machu Picchu example, one or more processing circuits can generate a three-dimensional (3D) object file based on a content data set, and the 3D object file functions as a digital twin of the historical site and corresponds to one or more characteristics of the historical site, such as its architecture, topography, and surrounding scenery. In this scenario, multiple levels of digital assets may be included, which include the main historical site assets, individual structures or features within the historical site, and any other associated assets such as historical documents, artworks, or stories related to the historical site. To create 3D object files for each of these assets, one or more processing circuits will process and reconstruct the captured content data set using algorithms and techniques to stitch together overlapping images, videos, or audio and extract depth information. This results in a precise and accurate digital representation of the assets that closely corresponds to their unique characteristics. The 3D object files for each asset can be linked together, and each link functions as a destination or pointer to the storage location of the corresponding metadata object (stored, for example, within token storage 154). This enables the presentation of images or videos of the historical site and its features in response to a selection by an application on a user device.

[0105] Referring to the example of Machu Picchu, in order to digitize and tokenize space and generate 3D object files and associated tokens (e.g., NFTs) for historical sites like Machu Picchu, some objective calculations and numerical data may be determined to ensure the accuracy and precision of the digital representation. In some arrangements, potentially LiDAR or photogrammetry techniques can be used to capture high-resolution images and videos of the historical site in order to obtain detailed spatial and visual information. These data points can be processed to generate a point cloud consisting of a large number of three-dimensional coordinates representing the surface of the historical site. To create an accurate 3D object file, algorithms such as Iterative Closest Point (ICP) or Simultaneous Localization and Mapping (SLAM) can be employed to align and integrate these point clouds, thereby reducing noise and inconsistencies. In some arrangements, surface reconstruction algorithms such as Poisson surface reconstruction or marching cubes method can be used to generate a mesh from the aligned point cloud consisting of interconnected vertices, tangents, and faces that define the 3D structure of the historical site. Additionally, texture mapping techniques are applied to project the captured visual information such as colors and patterns onto the generated mesh. This process requires the calculation of texture coordinates (UV coordinates) that map each vertex of the mesh to a corresponding position within the 2D texture image. In some arrangements, unique identification information can be generated for each asset included in the digital representation in order to generate tokens (e.g., NFTs) linked to the 3D object file. These identification information can be based on cryptographic hash functions or other unique identification methods. In some arrangements, the token generation process can also include encoding metadata including the origin, historical context, and associated files of the asset into the token structure.This metadata is then securely stored with the 3D object file, linked to a token, and enables seamless search and presentation of historical sites and their features in a virtual environment or augmented reality application.

[0106] In some arrangements, one or more processing circuits can generate multiple 3D object files according to the content data set and capture event parameters. The multiple processing circuits can receive, collect, or obtain the metadata of the physical object, including but not limited to the video of the physical object, scannable code, audio, text, any medium or digital representation, a pair of public and private keys, an executable program, or any combination thereof. This multi-layered approach enables a more comprehensive representation of the automatically captured baseball and its associated assets, allowing users to access, verify, and interact with the digital twins and their metadata on a distributed ledger or blockchain.

[0107] In block 230, one or more processing circuits store the 3D object file and capture event parameters in a data repository (e.g., data repository 150). This storage ensures that the digital twin and its associated information are securely and efficiently stored, enabling easy search, access, and management of the data. The data repository 150 can be a centralized or distributed storage system designed to provide performance, reliability, and scalability for managing 3D object files and capture event parameters. In particular, the object storage 152 within the data repository 150 can be utilized to store the 3D object files and capture event parameters. Each 3D object file and associated capture event parameter can be stored as a unique object within the object storage 152 identified by unique identification information.

[0108] In some arrays, the object storage 152 can provide features such as versioning, metadata management, and data deduplication. Versioning can track changes to 3D object files and capture event parameters over time, allowing users to access previous versions or restore data in case of accidental deletion or corruption. Metadata management can store additional information related to 3D object files and capture event parameters, examples of which include creation date, creator or owner, and any associated license or copyright information. Data deduplication optimizes storage usage by identifying and eliminating redundant data, thereby reducing storage costs and improving overall efficiency. Additionally, the object storage 152 can implement data encryption and access control mechanisms to ensure the security and privacy of stored 3D object files and capture event parameters. Data encryption can be applied using encryption algorithms such as the Advanced Encryption Standard (AES), Rivest-Shamir-Adleman (RSA), or other secure encryption methods to protect data both at rest and in transit. Access control mechanisms, including role-based access control and authentication protocols, can be implemented to restrict access to stored data, allowing only authorized users or systems to access and manage 3D object files and capture event parameters.

[0109] In block 240, one or more processing circuits generate a token containing a metadata object based on broadcasting a 3D object file, a content dataset, and capture event parameters to a distributed ledger. The metadata object is embedded together with the object's metadata, a pointer to the capture event parameters, and a pointer to the 3D object file. The token generation process typically involves minting a non-fungible token (NFT) that uniquely represents the digital twin and functions as a digital certificate of ownership and authenticity of the object. The NFT is minted on a specific blockchain platform such as Ethereum, Bitcoin, or a financial smart chain, and is assigned unique identification information that distinguishes it from other tokens on the blockchain. By generating a token that encapsulates the 3D object file and its associated metadata, block 240 establishes a secure and verifiable transparent link between the object and its digital twin.

[0110] In some arrangements, the metadata integrated into the token includes information about the physical object, including its unique characteristics, history, origin, and other relevant attributes. This metadata object also incorporates capture event parameters that provide context and certainty to the digital twin by documenting the conditions and circumstances under which the physical object was digitized. The metadata object may also include any additional data or documentation, such as expert authentication or appraisal, that further enhances the quality of the digital twin and increases its value and usefulness.

[0111] Token creation can include minting a non-fungible token (NFT) that uniquely represents the information and data of an object and functions as a digital certificate of ownership and authenticity of a physical object. To generate an NFT, the processing circuit can use a smart contract to embed a metadata object within the token. The metadata object includes the metadata of the object, which includes the unique characteristics and history of the physical object, pointers to capture event parameters, and pointers to 3D object files. This integration securely and transparently links all relevant information about the physical object and its digital twin within the NFT, providing a comprehensive and complete record of the digital or physical movement of the object.

[0112] In block 240, one or more processing circuits can broadcast a 3D object file, a content dataset, and capture event parameters to a distributed ledger. By broadcasting this information to the distributed ledger, various stakeholders can subsequently access, verify, and interact with the generated NFTs and their associated information. In response to this broadcast, a token containing metadata objects is generated (or returned). To facilitate token generation, the processing circuit initiates an exchange on a selected blockchain platform. In some arrangements, the exchange can include specifying a destination address (e.g., a user's digital wallet address or a designated smart contract) and providing exchange details such as the 3D object file, content dataset, capture event parameters, and any other information. The processing circuit may also digitally sign the transaction using the user's private key or other encryption methods to ensure the integrity and authenticity of the transaction. This signature verifies that the user or entity initiating the transaction is authorized to do so and prevents unauthorized parties from tampering with or changing the transaction details. Once the transaction is prepared and signed, the processing circuit broadcasts it to the blockchain network. Nodes on the network then verify the transaction and ensure that it complies with the platform's consensus rules and protocols. If the verification is successful, the transaction is added to a new block, appended to the blockchain, and permanently records the generated NFT and its associated data. By broadcasting the 3D object file, content dataset, and capture event parameters to a distributed ledger or blockchain, block 240 creates a transparent and secure record of the digital twin, enabling various stakeholders to track its ownership, origin, and history.

[0113] Furthermore, the processing circuit may apply cryptographic algorithms and techniques such as digital signatures or hashes to ensure the integrity and authenticity of metadata objects and their contents. These encryption means create a secure connection between the digital twin and the NFT, making it difficult for unauthorized parties to alter or forge the digital representation. The NFT generation process may also involve minting tokens on specific blockchain platforms such as Ethereum, Bitcoin, Binance Smart Chain, etc., depending on factors such as user preferences, platform compatibility, or available features and functions. Once the NFT is minted, unique identification information is assigned that distinguishes it from other tokens on the blockchain and enables the user to easily track, manage, and verify its ownership, origin, and associated data. By generating a token that encapsulates the metadata object, block 240 establishes a secure and verifiable transparent link between the physical object and its digital twin.

[0114] Generally, one or more processing circuits can generate (or mint) one or more non-fungible tokens that are linked to metadata objects and encapsulated within a control structure. The one or more processing circuits can generate tokens corresponding to specific one or more metadata objects. The generation and / or minting of NFTs can be included in digital assets stored on a blockchain. Thus, NFTs can digitally represent various aspects of an object and can function as proof of ownership and provenance of a specific object (e.g., a physical asset, an intellectual asset). NFTs can be verified by anyone on the blockchain, and the tokens guarantee the authenticity of 3D object files. Each NFT can store a data value composed of at least token identification information and a contract number. The token identification information can be a unique set of characters (e.g., numbers, symbols, and letters) that uniquely identifies a specific NFT. For example, token identification information #1 can be identified as "G8fNM64!", and token identification information #2 can be identified as "lkj93IOs". The contract number can be a unique set of characters (e.g., numbers, symbols, and letters) that uniquely identifies the control structure used by the NFT when managing and executing functions such as restricting the NFT and outputting from the NFT. For example, control structure #1 can be identified as "CS_00001", and control structure #2 can be identified as "CS_00002". Thus, the data value can be an aggregation of two pieces of identification information such as the cryptographic hash of the two pieces of identification information (e.g., the data value before hashing "G8fNM64!CS_00001", the data value after hashing "DFCD 3454 BBEA 778B 712A 652G 336F 90B1 7D9A 46AF"), or can be encrypted (e.g., using RSA encryption, AES encryption, SHA encryption, DES encryption). In some arrangements, the data value can be the public key of the NFT used to decrypt the NFT and / or can be an interface with a destination address on the blockchain.

[0115] In some arrangements, one or more processing circuits can hash a control structure (or contract number) using a cryptographic hash or another math-based function (e.g., SHA1, MD5, etc.) to create a digital signature of the control structure that can be stored within the token storage 154. In some arrangements, one or more processing circuits can hash a token using a cryptographic hash or another math-based function (e.g., SHA1, MD5, etc.) to create a digital signature of the NFT that can be stored within the blockchain storage 156. The cryptographic hash of the token can enable the users and systems described herein to verify them before receiving the token and modifying and / or updating the token or blockchain.

[0116] In some arrangements, one or more processing circuits can obtain an existing token and assign the existing token to one or more specific metadata objects. In other arrangements, one or more processing circuits can generate non-fungible tokens that are unique to all other tokens generated by one or more processing circuits that can identify a metadata object, fungible tokens that can be generated or replicated any number of times, and semi-fungible tokens that can be generated or replicated a specific number of times that falls below or meets a specific replication threshold. One or more fungible tokens or semi-fungible tokens can be associated with, for example, a specific metadata object or the same metadata object. One or more processing circuits can access the token storage 154 to determine whether a replication threshold corresponding to a specific threshold is met, and in response to determining that the replication threshold corresponding to the specific threshold is met, can prevent or defer the generation or replication of tokens that exceed or meet the replication threshold. For example, the token generator 112 can generate multiple NFTs based on some new metadata objects or NFTs indicated by the obtained existing tokens.

[0117] In some arrangements, tokens may be embedded within a 3D object file. This integration creates a direct link between the digital representation of a physical object and its corresponding token, streamlines access to the information associated with the token, and enhances the overall security of the asset. By directly embedding the token into the 3D object file, the token becomes an essential part of the digital twin, establishing a more robust connection between the token and the unique characteristics, history, and provenance of the object.

[0118] In some arrangements, the tokens need not be embedded within the 3D object file itself, but rather may be closely associated with a metadata object associated with the 3D object. For example, this metadata object can include information about capture events such as timestamps, locations, and the parties involved. One or more of these parties may digitally sign a transaction recorded on a distributed ledger technology (DLT) to attest to the correctness of the state of the digitized object or the capture event itself. The output of the NFT can be restricted to a remote device (e.g., client system 103 or third-party device 105) remote from one or more processing circuits. This restriction can be an attribute such that when at least one or more attributes of the control structure are satisfied and / or detected, an output can be generated. Additionally, the output may be restricted prior to verifying the authenticity of at least a portion of the physical object or 3D object file. In some arrangements, outputting can include releasing or transferring fungible value or assets from one digital wallet address (e.g., a blockchain address) to a digital wallet address. In various arrangements, outputting can include releasing or transferring non-fungible value or assets from a first digital wallet address (e.g., a blockchain address) to a second digital wallet address.

[0119] Referring to the example of the baseball in block 220, one or more processing circuits generate tokens including metadata objects based on broadcasting a 3D object file, content dataset, and capture event parameters to a distributed ledger for the automatically captured baseball and its associated assets. Each 3D object file, such as the baseball, the autographed signature, and any other associated assets like a certificate of authenticity or a photo of Babe Ruth signing the baseball, will generate a corresponding token. In some arrangements, the metadata objects embedded within each token include the metadata of the respective object, a pointer to the capture event parameters, and a pointer to the 3D object file. The capture event parameters can be similar or identical for each asset since they are all related to the same comprehensive context of the automatically captured baseball.

[0120] When the processing circuits generate these tokens, they initiate an exchange on a selected blockchain platform. The exchange can include specifying a destination address (e.g., the user's digital wallet address or a designated smart contract) and providing exchange details such as the unique identification information of each token, the metadata object, and any other required information. The processing circuits may also digitally sign the transaction using the user's private key or other encryption methods to guarantee the integrity and authenticity of the transaction. Once the transaction is prepared and signed, the processing circuits broadcast it to the blockchain network. Nodes on the network verify the transaction and ensure that it complies with the platform's consensus rules and protocols. If the verification is successful, the transaction is added to a new block and incorporated into the blockchain, permanently recording the NFTs and their associated data.

[0121] In another arrangement, a single token can be associated with multiple objects, effectively representing the entire collection of assets related to an automatically captured baseball. This single token has metadata objects embedded within it, including pointers to each of the 3D object files such as the baseball, the autograph, a photo of Babe Ruth signing the baseball, and any other associated assets. The metadata objects also include the metadata of all these objects and their respective capture event parameters, creating a comprehensive digital representation of the entire collection. By using a single token to represent the collection of assets, users can more easily manage, buy, sell, and transfer the entire collection as an integrated entity on the blockchain. This approach simplifies the tracking of provenance and ownership history, ensuring that all related assets are held together and their relationships are preserved.

[0122] In block 250, one or more processing circuits can store the token in the digital wallet address of the user device's wallet storage. To initiate the storage process, the processing circuit can first verify the user's digital wallet address. This address can function as unique identification information for the user on the blockchain and is important for enabling the receipt, storage, and management of NFTs and other digital assets. The address can be provided by the user during a setup process, automatically generated by wallet software, or read from the user's device.

[0123] Upon verifying the user's digital wallet address, the processing circuit initiates the transfer of tokens from a minting location, such as a smart contract or the originating address, to the user's digital wallet. This involves creating a blockchain transaction and defining the source and destination addresses, the unique identification information of the tokens, and the required fees or gas. To ensure the authenticity and integrity of the transaction, the transaction is digitally signed using the private key of the originating address. In some arrangements, before the transaction can be completed, as detailed in block 240, the transaction is broadcast to the blockchain network where it undergoes a series of verification and consensus processes. Once the transaction is confirmed, the tokens are successfully transferred to the user's digital wallet address and stored within the wallet storage of the user device. Block 250 ensures that the user retains full control and ownership of their NFTs and provides a secure and accessible storage solution for tracking the provenance of the objects. Through the process of storing tokens at a digital wallet address, the user can utilize the digital representation of physical objects for various purposes such as buying, selling, displaying, or verifying authenticity and provenance.

[0124] In some arrangements, one or more processors can generate a smart contract programmed to automatically calculate and allocate payments when tokens are exchanged, calculate the payment amount associated with a curator's royalty according to a token's metadata object in response to receiving a transfer request on a distributed ledger, and configure to allocate the payment to a curator wallet address associated with the curator according to the payment amount. In particular, one or more processing circuits can be configured to generate a smart contract programmed to automatically calculate and allocate payments when tokens are exchanged. In response to receiving a transfer request on a distributed ledger, one or more processing circuits can calculate the payment amount associated with a curator's royalty according to a token's metadata object. Thereby, the curator can receive compensation for the effort in maintaining, preserving, and improving the value of the objects it supervises.

[0125] In some arrangements, the smart contract functions as an automatically executable contract with contractual terms written directly into the code. By automating the calculation and allocation of payments, the smart contract ensures that transactions are executed efficiently and securely, minimizes the possibility of human error, and reduces the need for intermediaries. In some arrangements, royalty information can be stored within a token's metadata object. This royalty mechanism promotes a sustainable and fair environment and encourages continued investment in the preservation, authentication, and promotion of valuable physical objects and their digital counterparts. Further, one or more processing circuits can automatically allocate the calculated payment to a curator wallet address associated with the curator. This seamless transfer of funds ensures that the curator receives royalty payments quickly and securely and reduces the risk of funds disappearing or being sent to the wrong destination.

[0126] In some arrangements, one or more processing circuits can extract various characteristics (or metadata) of a physical object by analyzing the content data set and capture event parameters. These characteristics (or metadata) can include historical data, provenance data, appraisal data, and authentication data, all of which are important information contributing to the overall value, authenticity, and importance of the object. Historical data can include the background of the object, its origin, any previous owners, and its past movement history. Provenance data refers to the management of the object's distribution process and provides a clear and verifiable record of previous ownership and transactions. Appraisal data consists of expert evaluations of the object's value, which may be based on factors such as rarity, condition, demand, and historical importance. Authentication data includes any evidence or expert opinion that confirms the authenticity of the object, such as certificates, expert analysis, or scientific test results. In some arrangements, one or more processing circuits can store the extracted characteristics as digital signatures within the metadata object of the token. This digital signature functions as a unique verifiable link between the characteristics and the token, ensuring that the object's provenance, historical data, appraisal data, and authentication data are securely and persistently associated with its digital twin.

[0127] One or more processing circuits can determine that additional processing is required for the 3D object file based on specific 3D object file parameters. These parameters can include resolution, level of detail, file format compatibility, texture mapping, or surface normal adjustment. By considering these factors, the processing circuit can optimize the 3D object file to meet various needs such as memory requirements, visualization quality, and compatibility with different systems and platforms. Resolution refers to the number of pixels or points used to represent the 3D object file, which directly affects the visual quality and file size of the object. The processing circuit may adjust the resolution to balance the level of detail with memory and performance constraints. The level of detail is related to the complexity of the geometry of the 3D object file and the amount of information it contains. The processing circuit can optimize the level of detail according to the intended use of the digital twin, ensuring that it retains sufficient detail for its purpose without imposing an excessive burden on rendering or storage resources. File format compatibility is important to ensure that the 3D object file can be accessed and utilized across various platforms and applications. The processing circuit can convert the 3D object file to different formats or generate multiple versions to accommodate diverse software and hardware environments.

[0128] Texture mapping involves applying a 2D image or pattern to the surface of a 3D object file, adding a sense of presence and depth to its appearance. The processing circuit can optimize the texture mapping to improve the visual quality of the digital twin, ensuring that the texture is correctly aligned with the geometric shape of the object and does not introduce visual artifacts or distortions. Surface normal adjustment refers to the process of refining the surface normals of a 3D object file that determine how light interacts with the surface of the object. By adjusting the surface normals, the processing circuit can enhance the appearance of the object, making it visually more accurate and appealing when rendered in a virtual or augmented reality environment. After determining the additional processing required, one or more processing circuits can regenerate the 3D object file by applying the necessary adjustments. This optimized 3D object file ensures that the digital twin is suitable for various applications such as virtual exhibitions, augmented reality experiences, or digital archives.

[0129] In some arrangements, one or more processing circuits can generate multiple digital identification information (e.g., decentralized identification information (DID)) and provide it to one or more third-party computing systems, and these third-party systems are associated with various aspects of the digital twin creation process such as capture events, 3D object files, or tokens (NFTs). This digital identification information is uniquely assigned to each of the multiple third parties, can be cryptographically protected for each third party, and ensures that each identification information is exclusive to a specific third party and is protected from unauthorized access or tampering. Further, each of the multiple digital identification information can be configured to enable each of the multiple third parties to digitally sign one or more parts of the metadata of the 3D object file. To verify one or more parts of the metadata, one or more processing circuits can verify the digital signature associated with the digital identification information. This is done in response to receiving a combination of the digital identification information of the multiple digital identification information and the digital signature of one or more parts of the metadata. By matching the corresponding digital identification information with the digital signature, the processing circuit can ensure the authenticity and integrity of the metadata, providing a reliable and secure foundation for the digital twin and its associated NFT.

[0130] In some arrangements, one or more processing circuits can determine an authentication agent for a physical object based on a capture event and multiple environmental information. This environmental information may include factors such as the origin, category, value, and rarity of the physical object. By considering these various factors, the processing circuit can identify the most suitable authentication agent for verifying and authenticating the physical object. Once the authentication agent is determined, the processing circuit can collect the authentication agent information associated with the agent. This information may include the agent's identification information, qualifications, expertise, date and time of authentication, and related notes created by the agent during the authentication process. After collecting the authentication agent information, one or more processing circuits can update the metadata of the digital twin to further include this authentication agent information.

[0131] In some arrangements, the content dataset includes a diverse array of media, which may include one or more captured images, videos, or audio recordings of physical assets. This collection of media ensures a digital representation of the physical object, enabling the user to better understand, properly evaluate, and interact with the digital twin of the object. The capture event parameters can include various elements such as the date, time, and location of the event, as well as the individuals present or involved during the capture process. These parameters may also include environmental conditions such as lighting, temperature, and humidity that can potentially affect the quality and accuracy of the captured media. When generating a token, one or more processing circuits can use the metadata of the 3D object file to mint a non-fungible token (NFT). The minting process creates a unique and indivisible digital asset securely linked to the physical object through its metadata. This metadata, which includes information about the object such as its characteristics, provenance, and authentication, ensures that the NFT is an accurate and trustworthy digital representation of the physical asset.

[0132] In some arrangements, one or more processing circuits can present a 3D object file via an application on a user's device that features adjustable content enabling interaction with the user. Selecting a portion of the adjustable content configures the application to modify one or more features of the 3D object file, giving the user flexibility to explore and engage with the digital twin in a more personalized immersive manner. These adjustable features can include, but are not limited to, zooming, rotating, changing lighting conditions, or modifying textures, and can facilitate a deeper understanding of the details and complexity of the physical object.

[0133] In a process of broadcasting a 3D object file, a content dataset, and capture event parameters to a distributed ledger, one or more processing circuits perform several steps to ensure security, authenticity, and network compliance. First, the 3D object file, content dataset, and capture event parameters are encoded to facilitate secure transmission. Next, the encoded 3D object file, content dataset, and capture event parameters are signed using a private key corresponding to the digital wallet address of the user's device wallet storage, establishing a verifiable link between the data and its originating wallet. The signed data is then transmitted to a network of nodes participating in the distributed ledger.

[0134] These nodes can independently verify 3D object files, content datasets, capture event parameters, and associated signatures, and confirm the authenticity, integrity of the data, and compliance with the consensus rules governing the node network. This decentralized verification process ensures that 3D object files, content datasets, and capture event parameters are accurate and trustworthy, and that anti-tampering or forgery prevention functions are working. When a node verifies data, a token containing metadata objects is generated (or returned), and this token is incorporated into a new block of the exchange. This new block is then added to the existing blockchain within the decentralized ledger, further strengthening the immutability of the token and creating a permanent record of the token's existence, ownership, and history.

[0135] In some arrangements, a "manual capture" process is employed to create a digital twin of a physical object with higher accuracy and reliability. In this approach, the physical object is transported to a dedicated studio with a controlled environment specifically designed for photogrammetry. This environment ensures optimal lighting and conditions for the precise digital capture of the physical object's details, texture, and color. In these arrangements, one or more authentication agents have the opportunity to physically inspect the object during the capture process. These agents have expertise in the area of the object and can provide valuable insights and verification of the object's authenticity, origin, and other essential attributes. The involvement of expert authentication agents in the manual capture process can enhance the trust and reliability of the digital representation.

[0136] The inspection findings of the authentication agent, along with other relevant details related to the photogrammetry process and the object itself, are recorded on a public distributed ledger or blockchain using a consensus algorithm. This information can include a set of data, which includes the date and time of capture, the agent performing the capture, the inspection and findings of the authentication agent, and object attributes recognized by anyone, such as current ownership, manufacturer, designer, production date, conditions at the time of capture, origin, historical compliance, curator, sales history, appraisal, and documentation. This rich data can be securely stored within the metadata of the 3D object file and is associated with a non-fungible token (NFT) created using the 3D digital file. This provides an additional layer of verification and trust in the digital representation of physical objects, as expert authentication agents can personally inspect the object and ensure that its details are accurately documented. The manual capture process not only improves the overall accuracy of the digital twin but also instills greater confidence in potential buyers, insurers, and other stakeholders regarding the authenticity and origin of the object. Therefore, the combination of a controlled environment, expert authentication, and secure recording of relevant information on the blockchain ensures a high level of trust, transparency, and accuracy in the digitization of valuable objects.

[0137] Before block 210, one or more processing circuits can initiate a user onboarding process by creating an account using a blockchain or a public distributed ledger. During this onboarding process, various information about physical objects, including details about the owner and metadata, is collected and securely stored. This metadata may include the origin, history, dimensions, materials, and other relevant attributes of the object. Once the information is collected, one or more processing circuits can analyze the data and determine whether the object is eligible for ingestion based on predetermined criteria. These criteria may include factors such as the rarity, value, cultural importance of the object, or specific requirements set by the platform, ensuring that only eligible objects undergo the ingestion process and are subsequently represented as digital twins on the blockchain.

[0138] In some arrangements, one or more processors are further configured to: (1) receive, from a third-party computing system, a verifiable authentication information request associated with an authenticator; (2) analyze the authenticator's information and grant the authenticator permission based on cross-referencing it with at least one of the object's metadata or capture event; (3) generate digital identification information linked to the authenticator's identification information; (4) generate verifiable authentication information corresponding to the digital identification information, where the verifiable authentication information includes verifiable data of the object's metadata or capture event; (5) broadcast the verifiable authentication information to a distributed ledger; and (6) provide the digital identification information to the third-party computing system. In some arrangements, a plurality of digital identification information is each uniquely assigned to each of a plurality of authenticators, cryptographically protected, and each of the plurality of digital identification information is configured to enable each of the plurality of authenticators to digitally sign one or more portions of the object's metadata. In some arrangements, one or more processors verify one or more portions of the metadata in response to receiving a combination of digital identification information and digital signature of one or more portions of the metadata.

[0139] In some arrangements, one or more processors can be configured to perform a series of steps to authenticate and authorize a third-party authenticator. First, the processor receives a verifiable authentication information request associated with the authenticator from a third-party computing system. In some arrangements, this can include a request to verify the authenticator's expertise in the art or in a specific field such as antique authentication. Next, the processor analyzes the information provided by the authenticator and cross-references it with the object's metadata or capture event to grant the authenticator permission. In some arrangements, this can include matching the authenticator's authentication information with a list of approved experts in a specific area. Once the authenticator is authorized, the processor generates digital identification information linked to the authenticator's identification information. In some arrangements, this can include creating a unique hash based on the authenticator's personal information and expertise. Following the creation of the digital identification information, the processor generates verifiable authentication information corresponding to the digital identification information. In some arrangements, this can include generating a digitally signed certificate that proves the authenticator's expertise and identification information is correct. After generating the verifiable authentication information, the processor broadcasts this authentication information to a distributed ledger or blockchain. In some arrangements, this can include adding the verifiable authentication information to a smart contract associated with the object or capture event. Finally, the processor provides the digital identification information to the third-party computing system, enabling the authenticator to securely access the system and interact with the object or capture event, as well as other parties involved in the process. In some arrangements, this can include granting the authenticator access to a secure portal where the authenticator can review and authenticate the object or capture event.

[0140] Generally, verifiable authentication information refers to cryptographically secure, tamper-evident, and digitally signed information that proves the authenticity, ownership, or specific attributes of a physical object represented by a digital twin to be correct. This can function as a digital proof that can be used by a third-party device 105 to verify that a digital twin and its associated metadata are genuine and accurate based on the verification of the issuing authority. For example, a museum may wish to verify the authenticity and provenance of a rare painting before displaying it. The museum sends a request for verifiable authentication information to a data processing system 102 that manages the digital twin of the painting as a third-party device 105. The authorization processor 130 can match the metadata object of the token associated with the painting and the capture event with the museum's request and ensure that the museum is granted access to this information. If the authorization is successful, the system generates verifiable authentication information, which may include information such as the painting's authentication data, provenance, ownership history, and details of the capture event. The verifiable authentication information is then provided to the museum's third-party device 105, enabling the museum to independently verify the authenticity and provenance of the painting based on the digital twin and its metadata object stored within a token from a distributed ledger (e.g., blockchain storage 156). This process ensures that for the display of the painting, the museum can trust the information associated with the digital twin and make decisions based on that information.

[0141] Verifiable authentication information is not a key, but rather a digital document or data structure that contains legitimate credentials about an object, entity, or individual. Verifiable authentication information can be issued by a data processing system 102 called an issuer, and can be digitally signed using cryptographic techniques to guarantee its authenticity and integrity. The digital signature enables other parties known as verifiers to trust the verifiable authentication information. Thus, verifiable authentication information can be a digital document that contains information about a physical object such as its authenticity, origin, ownership history, and details of the capture event. The data processing system 102 that manages the digital twin acts as the issuer, while a third-party device 105 such as the museum in the previous example acts as the verifier. When receiving verifiable authentication information, the verifier can use the issuer's public key to verify the digital signature and confirm that the authentication information has not been tampered with and that it has been actually issued by an authorized party. Through this process, the verifier can trust the information contained in the verifiable authentication information without the need to contact the issuer directly.

[0142] In some arrays, the digital identification information can be a unique reference assigned to various stakeholders (experts, appraisal agents, insurance agents, etc.) who may be able to prove certain details about an object or capture event as correct. This digital identification information can be used to identify and authenticate these stakeholders. For example, a stakeholder can use that digital identification information to digitally sign verifiable authentication information, which proves that the inspection, review, or verification of the object and its information is correct. This digital signature can link the verifiable authentication information to the stakeholder's digital identification information, ensuring that the information belongs to a specific and trustworthy source. For example, an expert on vintage guitars can be assigned unique digital identification information by the data processing system 102 (e.g., specifically, the authorization processor 130). This identification information is cryptographically protected and linked to the expert's identification information. During a photogrammetric capture event, the expert inspects the vintage guitar while verifying its authenticity, historical compliance, and origin. The expert creates verifiable authentication information that includes the information verified by the expert about the vintage guitar. This verifiable authentication information includes details such as the guitar's place of origin, manufacturing date, owner history, and condition. The expert uses their digital identification information to digitally sign the verifiable authentication information. This digital signature ensures that the verifiable authentication information is traceable back to the expert while confirming that the provided information is from a trusted and authenticated source. The verifiable authentication information, along with the expert's digital signature, is recorded on a blockchain or distributed ledger. This provides a record that is immutable and tamper-proof with respect to the inspection and verification of the vintage guitar by the expert.

[0143] In some arrangements, the corresponding non-fungible token (NFT) metadata object for the vintage guitar will include references to verifiable authentication information and the digital identification information of the expert. This ensures that potential buyers, insurers, and other stakeholders can rely on the authenticity, provenance, and other details of the vintage guitar as verified by the expert. Thus, the digital identification information functions as a unique reference for each party involved in the object's verification process. This is used to authenticate these parties when they digitally sign the verifiable authentication information that includes the information they have verified. This process helps to establish trust and guarantee the authenticity and provenance of the object and its metadata in a decentralized and secure manner, such as being recorded on a blockchain or distributed ledger.

[0144] In some arrays, to grant an authenticator permission based on at least one of the object's metadata or capture events, one or more processing circuits can evaluate the authentication information and expertise of the authenticator related to a specific object or capture event. This process ensures that the authenticator has the necessary qualifications, knowledge, and experience to verify details of the object such as its authenticity, origin, and historical compliance. For example, the object can be an antique guitar. The authorization process may include verifying the following aspects. (1) Authenticator's identification information - Confirm that the authenticator is a legitimate expert in the field of antique guitars and not a counterfeiter or unauthorized individual. (2) Authenticator's qualifications - Ensure that the authenticator has the necessary qualifications such as relevant certifications, education, or professional affiliations that prove the correct expertise in antique guitars. (3) Authenticator's specialty - Confirm that the authenticator specializes in a specific type of guitar being evaluated, such as a particular brand, period, or technique style. (4) Authenticator's experience and track record - Evaluate the authenticator's history of successful appraisals, inspections, or other verifications of similar objects to ensure that the authenticator has a reliable and trustworthy track record in the field. (5) Details of the capture event - Evaluate the authenticator's involvement in the photogrammetric capture event, such as their presence during the capture process, their role in inspecting the object, and any relevant findings they provided during the event. By granting an authenticator permission based on the object's metadata or capture events, one or more processing circuits can ensure that the verifiable authentication information provided by the authenticator is reliable and trustworthy.This authorization process not only enhances the authenticity of the object and the credibility of potential buyers, insurers, and other stakeholders in terms of origin, but also helps maintain the overall integrity and security of the digital twin ecosystem.

[0145] In some arrangements, when the buying and selling of an object occurs, the digital identification information and verifiable authentication information can be used to guarantee the authenticity and origin of the object and to facilitate smooth and secure transactions. For example, before the transaction, potential buyers and other stakeholders can examine the verifiable authentication information associated with the digital identification information of the object. By examining the authentication information, they can confirm the authenticity, origin, and other relevant details of the object, such as the involvement of an expert authenticator in the inspection process. In the above example, during the transaction, the digital identification information of the authenticator can be used to sign the metadata associated with the object. This digital signature serves as proof of the authenticator's consent that the transferred object is legitimate and demonstrates their authority to do so. The signature also guarantees the integrity of the metadata and prevents unauthorized changes. In the above example, when the transaction is completed, the new owner of the object can be recorded within the metadata and on the distributed ledger. This update reflects the change in ownership and is added to the origin history of the object. The verifiable authentication information of any involved parties, such as authenticators, appraisers, or insurers, can also be updated to reflect their involvement in the transaction, further enhancing the quality of the object's metadata and history. Additionally, with regard to royalties, the digital identification information of the authenticator can be used to calculate and allocate royalties in response to the buying and selling of the object. The digital identification information helps identify qualified parties and ensures that they receive appropriate compensation for their business or investment related to the object.

[0146] Generally, verifiable authentication information can exist on a distributed ledger such as a blockchain that guarantees their security, immutability, and accessibility. By storing the authentication information on a distributed ledger, it becomes virtually impossible for a single party to tamper with or modify the information without obtaining the consensus of the network participants. In addition to being stored on a distributed ledger, verifiable authentication information can also be embedded within or referenced in the metadata of a digital twin (e.g., a 3D object file or an NFT). This enables stakeholders such as potential purchasers or insurers to access the authentication information when they need to consider the authenticity, origin, or other relevant details of the object. In some cases, the actual verifiable authentication information may not be directly stored within the metadata but can be linked to them through unique identification information (e.g., a hash or digital identification information). This identification information functions as a secure reference to the authentication information stored on the distributed ledger, enabling stakeholders to access and verify the authentication information without requiring the authentication information to be stored within the metadata itself. By storing verifiable authentication information on a distributed ledger and linking them to the metadata of a digital twin, one or more processing circuits can maintain a secure and transparent record of the object's history and guarantee the reliability of the information provided.

[0147] In some arrays, a private key can be used to update the token's metadata object to include verifiable authentication information. The private key can belong to the owner of the token or the party responsible for updating the metadata. The private key can be used to sign the updated metadata, ensuring that the changes are genuine and authorized by the rightful owner or authorized party with the proper rights. When the updated metadata is signed using the private key, the corresponding public key can be used by other parties to verify the authenticity of the signed metadata. The public key can be derived from the private key without disclosing any confidential information, ensuring the security of the private key. In this way, the private key is used to sign and authorize changes to the metadata, while the public key enables other parties to verify the authenticity and integrity of the updated metadata.

[0148] In some arrangements, one or more processing circuits can incorporate digital twin metadata or metadata objects into a 3D object file. For example, during the capture process, one or more processing circuits may record details surrounding an event, such as a timestamp, location, and the parties involved. A party may certify the correctness of the state of a digitized object or the state of a capture event by signing a transaction recorded on a distributed ledger technology (DLT). This exchange can function as a record that the event occurred and may include a digital signature from an account that attests to the correctness of the event. If such an account belongs to a digital identification information (DID), this may, in this case, act as an issuer, and the DID may include a reference to verifiable credential information (VC). In this way, a party can provide verifiable credential information for the exchange by signing it, and the transaction immutably recorded on the DLT is then referenced within the metadata of a non-fungible token (NFT) minted in a secondary step. In some arrangements, the metadata of the NFT can directly reference a DID document or unique identification information instead of, or in addition to, the transaction.

[0149] Referring now to FIG. 3, a physical object modeling architecture 300 according to some arrangements is shown. Architecture 300 provides a systematic process for creating a digital twin of a physical object and tokenizing it into a non-fungible token (NFT). The process begins with a 2D physical object, such as a guitar, shown in step 310. To create an accurate digital representation, in step 320, multiple captures of the physical object are taken from various angles and positions. These captures may consist of high-resolution images, videos, or other types of data and may be acquired using specialized equipment and methodologies such as photogrammetry or structured light scanning.

[0150] In step 330, the collected data is processed to create a 3D object file that represents the digital twin of the physical object. This 3D object file incorporates the captured details of the object's shape, surface texture, color, and other related attributes. The digital twin may then undergo additional processing or refinement based on specific requirements such as resolution, level of detail, or file format compatibility. Finally, in step 340, the metadata and other information about the object and events are tokenized into tokens such as non-fungible tokens (NFTs). This token is a unique digital asset that represents the digital twin of the physical object and includes metadata with important information about the object, such as its origin, authentication, and ownership. The tokenization process securely links the 3D object file to the token, ensuring that the digital twin is securely and immutably associated with its corresponding NFT on the blockchain or distributed ledger, providing a verifiable and tamper-proof record of the digital representation of the physical object.

[0151] FIG. 4 depicts a computer system 400 that can be used to implement, for example, the exemplary data processing system 102, the exemplary client system 103, the exemplary third party device 105, and / or various other exemplary systems described in this disclosure. The computing system 400 includes a bus 405 or other communication component for communicating information, and a processor 410 coupled to the bus 405 for processing information. The computing system 400 also includes a main memory 415, such as a random-access memory (RAM) or other dynamic storage device, coupled to the bus 405 for storing information and instructions to be executed by the processor 410. The main memory 415 can also be used to store location information, temporary variables, or other intermediate information during execution of instructions by the processor 410. The computing system 400 may further include a read only memory (ROM) 420 or other static storage device coupled to the bus 405 for storing static information and instructions for the processor 410. A storage device 425, such as a solid state device, magnetic disk, or optical disk, is coupled to the bus 405 for permanently storing information and instructions.

[0152] The computing system 400 may be coupled via the bus 405 to a display 435, such as a liquid crystal display or an active matrix display, for displaying information to a user. An input device 430, such as a keyboard including alphanumeric and other keys, may be coupled to the bus 405 for communicating information and command selections to the processor 410. In another implementation, the input device 430 includes a touch screen display 435. The input device 430 can include a cursor control, such as a mouse, trackball, or cursor direction keys, for communicating direction information and command selections to the processor 410 and for controlling cursor movement on the display 435.

[0153] In some implementations, computing system 400 may include a communication adapter 440, such as a network adapter. Communication adapter 440 may be coupled to bus 405 and may be configured to enable communication with computing or communication network 101 and / or other computing systems. In various exemplary implementations, communication adapter 440 may be used to achieve any type of networking configuration, such as wired (e.g., via Ethernet), wireless (e.g., via Wi-Fi, Bluetooth, etc.), pre-configured, ad-hoc, LAN, WAN, etc.

[0154] According to various implementations, the processes that result in the exemplary implementations described herein can be achieved by computing system 400 in response to a processor 410 executing an array of instructions included in main memory 415. Such instructions can be read into main memory 415 from another computer-readable medium, such as storage device 425. Execution of the array of instructions included in main memory 415 causes computing system 400 to perform the exemplary processes described herein. Also, one or more processors of a multi-processing array may be employed to execute the instructions included in main memory 415. In alternative implementations, instead of, or in combination with, software instructions, wired-connected circuitry may be used to implement the exemplary implementations. Accordingly, implementations are not limited to any specific combination of hardware circuitry and software.

[0155] Although an exemplary processing system is described in FIG. 4, implementations of the subject matter and the functional operations described herein can be performed using other types of digital electronic circuitry, or in computer software, firmware, or hardware, or in any combination of one or more of them, including the structures disclosed herein and their structural equivalents.

[0156] The subject matter described in this specification may sometimes illustrate different components that are included within or connected to other different components. It should be understood that the architecture so depicted is exemplary and that in practice, many other architectures that achieve the same functionality can be implemented. In a conceptual sense, any arrangement of components for achieving the same functionality is effectively "associated" so that the desired functionality is achieved. Thus, any two components of this specification combined to achieve a particular function can be considered to be "associated" with each other so that the desired functionality is achieved, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired function, and any two components that can be so associated can also be considered to be "operably couplable" to each other to achieve the desired function. Specific examples of being operably couplable include, but are not limited to, components that are physically mating and / or physically interacting, and / or wirelessly interacting and / or wirelessly interacting, and / or logically interacting and / or logically interactable.

[0157] Regarding the use of plural and / or singular terms in this specification, those skilled in the art can convert from plural to singular and / or from singular to plural as appropriate for the context and / or application. Various singular / plural substitutions may be explicitly described in this specification for clarity.

[0158] In general, as used herein, and in particular in the appended claims (e.g., the body of the appended claims), the terms are generally understood by those skilled in the art to be intended as "non-limiting" terms (e.g., the term "including" should be construed as "including but not limited to", the term "having" should be construed as "having at least", the term "includes" should be construed as "includes but not limited to", etc.).

[0159] The figures and descriptions may illustrate a specific order of method steps, but such step order may be different from that illustrated and described, unless otherwise specified above. Also, unless otherwise specified above, two or more steps may be performed simultaneously or partially simultaneously. Such variations may depend, for example, on the selected software and hardware systems and the designer's selections. All such variations are within the scope of the present disclosure. Similarly, the software implementations of the described methods may be accomplished using standard programming techniques with rule-based logic and other logic to perform various connection steps, processing steps, comparison steps, and decision steps.

[0160] Furthermore, if the specific number of claim descriptions to be introduced is intended, such intention should be understood by those skilled in the art to be explicitly described in the claims, and if there is no such description, such intention does not exist. For example, for the purpose of assistance in understanding, the following appended claims may include the use of introductory phrases "at least one" and "one or more" for introducing claim descriptions. However, the use of such phrases should not be construed to limit any particular claim that introduces a claim description by the indefinite article "a" or "an" to a disclosure that includes only one such description, even if the same claim includes an introductory phrase such as "one or more" or "at least one" and an indefinite article such as "a" or "an" (for example, "a" and / or "an" should typically be construed to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim descriptions. Furthermore, even if the specific number of claim descriptions to be introduced is explicitly described, those skilled in the art should recognize that such description should typically be construed to mean at least the described number (for example, a minimal description of "two descriptions" without other modifiers should typically mean at least two descriptions, or two or more descriptions).

[0161] Furthermore, when conventions similar to “at least one of A, B, and C, etc.” are used, generally, such a configuration is intended in the sense that one of ordinary skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” includes, but is not limited to, a system having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C). When conventions similar to “at least one of A, B, or C, etc.” are used, generally, such a configuration is intended in the sense that one of ordinary skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” includes, but is not limited to, a system having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C). In essence, it should be further understood by one of ordinary skill in the art that any disjunctive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, is to be understood as encompassing one of the terms, any of the terms, or both terms. For example, the phrase “A or B” would be understood to include the possibilities of “A,” or “B,” or “A and B.”

[0162] Furthermore, unless otherwise specified, the use of words such as “approximate,” “about,” “around,” “substantially,” etc. means plus or minus 10%.

[0163] The foregoing description of the exemplary implementations has been presented for purposes of illustration and description. It is not intended to be exhaustive or limiting with respect to the precise forms disclosed, and modifications and variations are possible in light of the above teachings, or may be obtained from practice of the disclosed implementations. The scope of the present disclosure is intended to be defined by the appended claims and their equivalents.

Claims

1. A system for modeling an object, comprising: a memory; receiving, from an application of a user device, a content data set of the object and capture event parameters of the capture event of the object, wherein the content data set includes duplicate content of the captured object and associated metadata of the object; generating a three-dimensional (3D) object file based on the content data set, wherein the 3D object file is a digital twin of the object and corresponds to one or more characteristics of the object; storing the 3D object file and the capture event parameters in a data repository; generating a token including a metadata object based on broadcasting the 3D object file, the content data set, and the capture event parameters to a distributed ledger, wherein the metadata object embeds the metadata of the object, a pointer to the capture event parameters, and a pointer to the 3D object file in the token; storing the token in a digital wallet address of the wallet storage of the user device; one or more processors configured to perform the above; A system comprising a data processing system comprising the above.

2. The one or more processors are further configured to: calculate an amount of payment associated with a curator's royalty according to the metadata object of the token in response to receiving a transfer request on the distributed ledger; allocate the payment to a curator wallet address associated with the curator according to the amount of payment; The system according to claim 1.

3. The one or more processors are further configured to: Extracting the metadata of the object based on analyzing the content data set and the capture event parameters, where the metadata includes historical data, source data, authentication data, and verification data, and the metadata is stored in the metadata object of the token as a digital signature linking the metadata to the 3D object file, and the system according to claim 1 is further configured to perform this.

4. The one or more processors are determining additional processing to be performed on the 3D object file based on one or more 3D object file parameters, where the 3D object file parameters include at least one of resolution, detail level, file format compatibility, texture mapping, or surface normal adjustment, and regenerating the 3D object file of the object by applying the additional processing to the 3D object file, and the system according to claim 1 is further configured to perform this.

5. The one or more processors are receiving a verifiable authentication information request associated with an authenticator from a third-party computing system, analyzing the information of the authenticator and granting permissions to the authenticator based on cross-referencing it with at least one of the metadata of the object or the capture event, generating digital identification information linked to the identification information of the authenticator, generating verifiable authentication information corresponding to the digital identification information, where the verifiable authentication information includes verifiable data of the metadata of the object or the capture event, embedding the verifiable authentication information into the 3D object file, broadcasting the verifiable authentication information to the distributed ledger, providing the digital identification information to the third-party computing system, and the system according to claim 1 is further configured to perform this.

6. A plurality of digital identification information is uniquely assigned to each of a plurality of authenticators, encrypted and protected, and each of the plurality of digital identification information is configured to enable each of the plurality of authenticators to digitally sign one or more parts of the metadata of the object. The system according to claim 5.

7. The one or more processors verify one or more parts of the metadata in response to receiving a combination of the digital identification information and the digital signature of one or more parts of the metadata. The system according to claim 6.

8. The one or more processors determine an authentication agent of the object based on the capture event and a plurality of environmental information including at least one of the origin of the physical object, the category of the physical object, the value of the physical object, and the rarity of the physical object; collect authentication agent information associated with the authentication agent and including at least one of agent identification information, agent qualifications, field of agent expertise, authentication date and time, and agent notes; update the metadata object of the token to further include the authentication agent information using a private key corresponding to the digital wallet address of the wallet storage of the user device; The system according to claim 1, further configured to perform.

9. The content data set includes at least one or more captured images, videos, or sounds of the object, the capture event parameters include at least the date, time, location, related parties present or involved, and environmental conditions of the capture event, and generating the token includes minting a non-fungible token (NFT) using the metadata of the object. The system according to claim 1.

10. The one or more processors The system according to claim 1, further configured to present the 3D object file including adjustable content via an application of the user device, and when a part of the adjustable content is selected, the application is configured to adjust one or more features of the 3D object file.

11. Broadcasting comprises encoding the 3D object file, the content dataset, and the capture event parameters, signing the encoded 3D object file, content dataset, and capture event parameters with a private key corresponding to a digital wallet address of a wallet storage of the user device, transmitting the signed 3D object file, content dataset, and capture event parameters to a network of nodes participating in the distributed ledger, wherein the nodes independently verify the 3D object file, content dataset, capture event parameters, and the associated signature to confirm authenticity, integrity, and compliance with the consensus rules of the network of the nodes, incorporating the token into a new exchange block, wherein the new block is added to an existing blockchain within the distributed ledger, The system according to claim 1, comprising.

12. A method of modeling an object, comprising receiving, by one or more processing circuits, from an application of a user device, a content dataset of an object and capture event parameters of a capture event of the object, wherein the content dataset includes duplicate content of the captured object and associated metadata of the object, generating, by the one or more processing circuits, a three-dimensional (3D) object file based on the content dataset, wherein the 3D object file is a digital twin of the object and corresponds to one or more characteristics of the object, Storing the 3D object file and the capture event parameters in a data repository by the one or more processing circuits; Generating a token including a metadata object by the one or more processing circuits based on broadcasting the 3D object file, the content data set, and the capture event parameters to a distributed ledger, wherein the metadata object embeds the metadata of the object, a pointer to the capture event parameters, and a pointer to the 3D object file in the token; Storing the token in a digital wallet address of the wallet storage of the user device by the one or more processing circuits; A method comprising: "Claim 13" In response to receiving a transfer request on the distributed ledger, calculating, by the one or more processing circuits, an amount of payment associated with the curator's royalty according to the metadata object of the token; Allocating, by the one or more processing circuits, the payment to a curator wallet address associated with the curator according to the amount of payment, further comprising the method according to claim 12. "Claim 14" Extracting, by the one or more processing circuits, the metadata of the object based on analyzing the content data set and the capture event parameters, wherein the metadata includes history data, origin data, authentication data, and authentication data, and the metadata is stored in the metadata object of the token as a digital signature linking the metadata to the 3D object file, further comprising the method according to claim 12. "Claim 15" Determining, by the one or more processing circuits, additional processing to be performed on the 3D object file based on one or more 3D object file parameters, wherein the 3D object file parameters include at least one of resolution, detail level, file format compatibility, texture mapping, or surface normal adjustment; Regenerating the 3D object file of the object by applying the additional processing to the 3D object file by the one or more processing circuits; The method according to claim 12, further comprising.

16. Receiving, by the one or more processing circuits, a verifiable authentication information request associated with an authenticator from a third-party computing system; Granting authority to the authenticator by the one or more processing circuits based on analyzing the information of the authenticator and cross-referencing it with at least one of the metadata of the object or the capture event; Generating, by the one or more processing circuits, digital identification information linked to the identification information of the authenticator; Generating, by the one or more processing circuits, verifiable authentication information corresponding to the digital identification information, wherein the verifiable authentication information includes verifiable data of the metadata of the object or the capture event; Embedding, by the one or more processing circuits, the verifiable authentication information into the 3D object file; Broadcasting, by the one or more processing circuits, the verifiable authentication information to the distributed ledger; Providing, by the one or more processing circuits, the digital identification information to the third-party computing system; The method according to claim 12, further comprising.

17. Each of the plurality of digital identification information is uniquely assigned to each of the plurality of authenticators, encrypted and protected, and each of the plurality of digital identification information is configured to enable each of the plurality of authenticators to digitally sign one or more parts of the metadata of the object. The method according to claim 16.

18. Determining, by the one or more processing circuits, an authentication agent of the object based on the capture event and a plurality of environmental information including at least one of the origin of the physical object, the category of the physical object, the value of the physical object, and the rarity of the physical object; By the one or more processing circuits, collecting authentication agent information associated with the authentication agent and including at least one of agent identification information, agent qualifications, fields of agent expertise, authentication date and time, and agent notes; By the one or more processing circuits, using a private key corresponding to the digital wallet address of the wallet storage of the user device to update the metadata object of the token to further include authentication agent information; The method according to claim 12, further comprising. **Claim 19** A non-transitory computer-readable medium including one or more instructions stored thereon, Receiving, from an application of a user device, a content data set of an object and capture event parameters of the capture event of the object, wherein the content data set includes duplicate content of the captured object and associated metadata of the object; Generating a three-dimensional (3D) object file based on the content data set, wherein the 3D object file is a digital twin of the object and corresponds to one or more characteristics of the object; Storing the 3D object file and the capture event parameters in a data repository; Generating a token including a metadata object based on broadcasting the 3D object file, the content data set, and the capture event parameters to a distributed ledger, wherein the metadata object embeds the metadata of the object, a pointer to the capture event parameters, and a pointer to the 3D object file in the token; Storing the token at a digital wallet address of the wallet storage of the user device; A non-transitory computer-readable medium executable by at least one processor to perform. **Claim 20** Additional instructions are stored thereon, In response to receiving a transfer request on the decentralized ledger, calculating an amount to be paid associated with the curator's royalty according to the metadata object of the token; Allocating the payment to a curator wallet address associated with the curator according to the amount to be paid; The non-transitory computer-readable medium according to claim 19, which is executable by the at least one processor to further perform the above.

Images