System and method for authenticated digital asset transfer

Abstract

Systems and methods for digital asset transfer are disclosed. First authentication data is generated by authenticating an identity of a first user of a first device. Transaction data is generated associated with transfer of a digital asset. The transaction data and the first authentication data are transmitted to a second device associated with a second user. Second authentication data associated with the second user is received. A transaction record is caused to be recorded to a distributed ledger, the transaction record comprising the transaction data, the first authentication data, and the second authentication data. In various embodiments, an access object configured to provide access to the digital asset is generated, which can include metadata to restrict the access to the digital asset based on a time and / or a location.

Description

P320505.W0.01SYSTEM AND METHOD FOR AUTHENTICATED DIGITAL ASSET TRANSFERCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 689,519, filed August 30, 2024, entitled “SYSTEM AND METHOD FOR AUTHENTICATED DIGITAL ASSET TRANSFER,’' which is incorporated by reference herein, in the entirety and for all purposes.FIELD

[0002] The described embodiments relate generally to systems and methods for secure and authenticated transfer of digital assets.BACKGROUND

[0003] Existing technologies for transferring digital content include limited security features, such as basic digital signature applications and radio-frequency identification (RFID)-based systems. Such systems, however, lack robust security features and are, as a result, susceptible to forgery and unauthorized access. Such systems further do not generally provide a way to authenticate the identity of individuals involved in such a transfer or to verity the integrity of such a transfer. Moreover, such systems may not provide functionality to regulate access to a transferred digital asset.SUMMARY

[0004] In an embodiment, a computer-implemented method of authenticated transfer of a digital asset is disclosed. First authentication data is generated by authenticating an identity of a first user of a first device. Transaction data is generated associated with transfer of a digital asset. The transaction data and the first authentication data are transmitted to a second device associated with a second user. Second authentication data is received associated with the second user. A transaction record is caused to be recorded to a distributed ledger, the transaction record comprising the transaction data, the first authentication data, and the second authentication data.

[0005] In some implementations, the transaction data comprises access information for the digital asset and metadata associated with the transfer of the digital asset.

[0006] In some implementations, the second device comprises or is coupled to a passive electronic device, and the method further includes communicating, from the second device, the transaction data to a third device associated with the second user using the passive electronic device.P320505.W0.01

[0007] In some implementations, the method further includes generating and / or transmitting an access object configured to provide access to the digital asset. In these and other implementations, the access object includes metadata to restrict the access to the digital asset based on a time, a location, or both.

[0008] In some implementations, authenticating the identity of the first user of the first device includes capturing, using the first device, biometric data associated with the first user.

[0009] In another embodiment, a computer-implemented method of providing access to a digital asset is disclosed. Transaction data and authentication data, having been generated in association with transfer of a digital asset, are received. The authentication data includes an indication of an identity of a first user associated with a first device and a second user associated with a second device. A transaction record is generated for the transfer of the digital asset, the transaction record including the transaction data and the authentication data. The transaction record for the transfer of the digital asset is caused to be recorded at a distributed ledger, and access is provided to the digital asset.

[0010] In some implementations, the transaction data comprises access information for the digital asset and metadata associated with the transfer of the digital asset.

[0011] In some implementations, at least a portion of the transaction data, the authentication data, or both are generated using a passive electronic device coupled to the first device or the second device.

[0012] In some implementations, an access object configured to provide access to the digital asset is generated. The access object may be generated, for example, by a server computer, by the first device, or by the second device. In these and other implementations, the access object comprises metadata to restrict the access to the digital asset based on a time, a location, or both.

[0013] In another embodiment, one or more computer-readable media are disclosed carrying instructions that, when executed, cause performance of one or more methods and / or operations described herein. The one or more computer-readable media may be non-transitory.

[0014] In another embodiment, a system is disclosed comprising at least one processor and at least one memory earning instructions that, when executed, cause performance of one or more methods and / or operations described herein.

[0015] Additional embodiments and features are set forth in part in the following description and will become apparent to those skilled in the art upon examination of the present disclosure and may be learned by the practice of the disclosed subject matter. A further understanding of the nature and advantages of the present disclosure may be realized by reference to the remaining portions of the specification and the drawings, which form a part of this disclosure. One of skill in the art will understand that each of the various aspects and features of the disclosure mayP320505.W0.01 advantageously be used separately in some instances, or in combination with other aspects and features of the disclosure in other instances.BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The description will be more fully understood with reference to the following figures in which components are not draw n to scale, which are presented as various examples of the present disclosure and should not be construed as a complete recitation of the scope of the disclosure, characterized in that:

[0017] FIG. 1 is a block diagram illustrating an example system for transferring digital assets in accordance with various embodiments of the disclosure.

[0018] FIG. 2A is a block diagram illustrating example components for transferring digital assets using passive electronic devices in accordance with various embodiments of the disclosure.

[0019] FIG. 2B is a block diagram illustrating example components for transferring digital assets using a passive electronic device and an active electronic device in accordance with various embodiments of the disclosure.

[0020] FIG. 2C is a block diagram illustrating example components for transferring digital assets using an active electronic device and a passive electronic device in accordance with various embodiments of the disclosure.

[0021] FIG. 2D is a block diagram illustrating example components for transferring digital assets using active electronic devices in accordance with various embodiments of the disclosure.

[0022] FIG. 3 is a block diagram illustrating an example computing system used in various examples of the disclosure.

[0023] FIG. 4 is a flow diagram illustrating a process for transferring digital assets using systems and methods described herein.

[0024] FIG. 5 is a flow diagram illustrating a process for authenticated transfer of a digital asset.

[0025] FIG. 6 is a flow diagram illustrating a process for providing access to a digital asset.DETAILED DESCRIPTION

[0026] Systems and methods for secure transfer of digital assets are disclosed herein. Certain details are set forth below to provide a sufficient understanding of embodiments of the disclosure. However, embodiments of the disclosure may be practiced without these particular details. Moreover, the particular embodiments are provided by way of example and should not be construed as limiting. In other instances, well-known circuits, control signals, timing protocols, and software operations have not been shown in detail to avoid unnecessarily obscuring the disclosed embodiments.P320505.W0.01

[0027] Recipients or purchasers of memorabilia have a need to verify authenticity of memorabilia. But conventional techniques for authenticating memorabilia are outdated and focused on tangible memorabilia, such as using a paper certificate, a scannable barcode, or the like to authenticate a signature on physical merchandise, a limited-edition physical item, or a similar asset. Accordingly, existing techniques are deficient for transferring and authenticating digital memorabilia, such as non-fungible tokens (NFTs), digital images, digital signatures (e.g., non-fungible autographs (NF As), non-fungible signatures (NFSs), digital audio, or the like. Even where existing technologies provide limited electronic security features, these features are ty pically only for providing basic digital signatures or RFID-based security .

[0028] Additionally, existing technologies do not allow for flexible or configurable transferring of digital assets. For example, existing technologies do not allow for fast and authenticated transfer of digital assets, such as transferring digital assets by simulcast and / or in real time (e.g., in seconds or less) to a large number of recipients (e.g., hundreds, thousands, hundreds of thousands). Additionally, existing technologies do not provide for flexible and authenticated access to digital assets, such as access that is restricted to a time and / or location as well as a specific recipient.

[0029] In various embodiments, the systems and related methods disclosed herein may include an exchange service that provides techniques for secure and verifiable capturing, storing, and exchanging of digital assets, such as machine-readable memorabilia, between a source and a recipient. For example, the exchange service described herein may utilize actor authentication (e.g., biometric verification such as fingerprints, facial recognition, or other means) to confirm a source identity. As used herein, “authentication” can refer to one or more operations to confirm, prove, and / or serve to prove the identity of a person. Transaction data generated by the exchange may further be stored on a distributed ledger (e.g.. a blockchain) offering an additional level of security and ability to verify such transactions. In an example implementation, a source uses a source device to generate a digital asset comprising a digital autograph and associated metadata, which may include time and location information. For example, the source may be a musician generating a digital autograph that is specific to a concert time and location. The metadata may also include authentication information, such as an indication of authentication of a source (e.g., using fingerprinting or facial recognition, a password or passcode, a personal identification number (PIN)). The generated digital asset may be transferred in real time to various recipient devices, such as smartphones of attendees of the concert. To facilitate the transfer, the recipients may be authenticated in a similar manner via respective devices. Additionally, the digital asset may comprise or be associated with an access object to restrict access to the digital asset, such as an access object encoded with metadata to only allow the digital asset to be received usingP320505.W0.01 recipient devices that are present at the concert location and during the concert time. Details of the transfer of the digital asset can be used to generate a transaction record, and the transaction record can be recorded to a distributed ledger to securely store the transaction information. In some examples, the exchange service is utilized to exchange digital assets comprising digital memorabilia, such as digital collectibles, authenticated signatures, photos, videos, audio messages, and the like. In such examples, a source may be a celebrity, athlete, or other source of such memorabilia.

[0030] Advantages of the disclosed technology include, without limitation, improved security for transferring digital assets, reliability7of documentation related to transferring digital assets, increased efficiency, improved flexibility of digital asset transfer, and improved user experience. For example, the use and documentation of authentication (e.g.. biometric authentication) allows digital assets to be transferred between known or verifiable parties and reduces fraud, such as fraudulent transfer of memorabilia that is counterfeited. Additionally, the use of blockchain technology allows for tamper-proof recording of digital asset information, including documentation of provenance, party identities, authentication data, and the like. Other advantages of the disclosed technology will be apparent to persons of skill in the art based on the present disclosure, including the drawings, and in view of the knowledge of a person skilled in the art.

[0031] While example embodiments are described with respect to exchange of digital memorabilia, it will be appreciated that the disclosed technology may be utilized for other types of exchange and authentication such as, for example, authentication of medical records, educational records, and other official records. In these and other embodiments, the disclosed technology can also be used for verifying or documenting oral contracts or authenticating parties to other kinds of interactions.

[0032] FIG. 1 is a block diagram illustrating an example system 100 for transferring digital assets in accordance with various embodiments of the disclosure. Various active devices 106a-b, which may be used for generating and transferring digital assets, communicate with an exchange service 102 and a distributed ledger 104 via a network 110 (e.g., the internet). Various passive devices 108a, 108b, 108c, which may be used for generating and transferring digital assets, communicate with active devices 106a-b, such that transfers completed using the passive devices 108a- 108c may be facilitated by the exchange service 102 and recorded on the distributed ledger 104. As used herein, a “passive device” can refer to one or more electronic components that can interact with a network-connected device (e.g., a smartphone, tablet computer, laptop, or other computing device, which may be wired or wireless) without its own power source. A passive device may rely on or use energy7transmitted from the network-connected device to performP320505.W0.01 tasks, such as data transmission or authentication. In various embodiments, a passive device does not actively initiate communication or processing. As used herein, an “active device’7can refer to a computing device with its own power source. An active device may be a network-connected device, such as a smartphone, tablet computer, laptop, or other computing device. An active device may perform tasks such as data transmission or authentication without relying on energy' received from an external source, and an active device may actively initiate communication and / or processing.

[0033] The exchange service 102 generally facilitates the exchange of digital assets between actors. The actors may be associated with various devices, including, for example, active devices 106a-b and passive devices 108a-c. As used herein, a passive device is distinguished from an active device in that the passive device may lack certain functionality of the active device, such as an on-device power source, cellular or WiFi communication, a display, or the like.

[0034] Passive devices 108a-c may be implemented as passive communication devices such as a near-field communication (NFC) chip or a RFID tag. For example, passive devices 108a-c may utilize NFC communication to transmit data between a passive device and a compatible reader. Passive devices 108a-c may be configured to provide secure forms of communication between such passive devices, active devices 106a-b, an exchange service 102, and a distributed ledger 104. The passive devices 108a-c may store data thereon such as a website address (uniform resource locator (URL)) for accessing a digital asset, information about a user associated with a device, and the like.

[0035] The passive devices 108a-c may include, be embedded in, or placed on an object including a portable card (e.g., plastic card), transceiver, badge, or appliance that can be easily carried by a user of the passive device. In various examples, passive devices 108a-c may not be associated with or may not include other computer or communication components, and the passive devices 108a-c may only be configured as having passive data transmission capabilities. Such passive devices may be possessed by any user of the exchange service 102. Digital assets or instructions to access digital assets may be stored on and transmitted by such passive devices 108a-c.

[0036] Active devices 106a-b in communication with the exchange service 102 may communicate with the passive devices 108a-c to record transactions performed using one or more passive devices and / or to conduct transactions directly with one or more of the passive devices 108a-c.

[0037] The active devices 106a-b may be possessed and utilized by a user of the exchange service 102, including users sending or receiving digital assets. Such devices may be implemented using any number of computing devices (e.g., user equipment) including, but notP320505.W0.01 limited to, a mobile phone or other mobile device, a computer, a laptop, wearable device (e.g., augmented reality (AR) / virtual reality (VR) headset, smart watch, smart glasses, or the like), portable, non-wearable devices, or other devices. Generally, the active devices 106a-b include one or more processors, such as central processing units (CPU) and / or graphics processing unit (GPU). The active devices 106a-b may generally perform operations by executing executable instructions (e.g.. software) using the processor(s).

[0038] In various embodiments, the active devices 106a-b and / or the passive devices 108a-c include one or more sensors or other input devices used for authenticating users. For example, one or more of the devices may include a fingerprint sensor for authenticating a user's identitybased on a fingerprint, and the devices may include a camera for authenticating a user's identity based on facial recognition. In a particular example, one or more of the passive devices 108a-c are configured as authentication devices for authenticating an actor or an authorized user involved in the exchange of the digital asset, and the step of authentication using the one or more of the passive devices 108a-c may be required prior to providing access to the digital assets or instructions stored on the passive devices 108a-c and / or an associated active device 106a-b. In another example, one or more active devices 106a-b may be configured as the authentication device, and the step of authentication via one or more of the active devices 106a-b may be required prior to providing access to the digital assets or instructions stored on the active device 106a-b and / or associated passive devices 108a-c. In a further example, authentication via both the active devices 106a-b and passive devices 108a-c may be required prior to providing access to the digital assets stored on the active device 106a-b and / or associated passive devices 108a-c.

[0039] The exchange service 102, distributed ledger 104, and active devices 106a-b generally communicate via a network 110. The network 110 may be implemented using one or more of various systems and protocols for communications between computing devices. In various embodiments, the network 110 or various portions of the network 110 may be implemented using the Internet, a local area network (LAN), a wide area network (WAN), and / or other networks. In addition to traditional data networking protocols, in some embodiments, data may be communicated according to protocols and / or standards including NFC, Bluetooth, cellular connections, and the like.

[0040] In an example embodiment, a first active device 106a associated with a first user generates a digital asset, which can be a digital autograph. Various data (e.g., metadata) associated with the digital asset can also be captured, such as authentication data, user data, a timestamp, location information, and so forth. The exchange service 102 facilitates transfer of the generated digital asset to a second active device 106b associated with a second user. For example, the exchange sendee 102 may provide an application to the first active device 106a andP320505.W0.01 the second active device 106b, which is used to generate and transfer the digital asset. The second active device 106b captures additional data, such as authentication data associated with the second user, user data, time information, location information, and so forth. In some examples, payment information may be provided via one or more of the active devices, such as the second active device 106b. At least a portion of the data captured via the first active device 106a and the second active device 106b is used to generate a transaction record. For example, the transaction record may include authentication data for the first and second user and data associated with a transaction for transfer of the digital asset, such as an identifier for the digital asset, time information, location information, and so forth. The transaction record can be generated, for example, by the first active device 106a, the second active device 106b, and / or the exchange service 102. The transaction record is recorded to the distributed ledger 104 to document the transfer of the digital asset. In some implementations, an access object is generated and provided (e.g., by the exchange service 102 or the first active device 106a), which allows the digital asset to be accessed based on associated conditions. As used herein, an “access object” can refer to a secure digital construct that governs one or more conditions under which a digital asset can be accessed (e.g., by a user device). An access object can encapsulate permissions (e.g., user or device permissions), time-based access constraints, location-based access constraints, and the like, effectively serving as a gatekeeper of the digital asset. An access object goes beyond simple functionality of a digital key and provides security and conditional-access functions. In some examples, the access object includes a URL or other identifier indicating a location. In some examples, the access object is encoded with metadata to provide access to the digital asset only when a device is determined to be at a particular location and / or only at a particular time. The location may be determined based on global positioning system (GPS) technology. For example, the access object may be provided for the second active device 106b, and a software component operating on the second active device 106b and / or the first active device 106a, and / or on the exchange service 102 may be configured to determine a current location and / or time, such that the access object provides access to the digital asset when the current location and / or time match an expected location and / or time. In various embodiments, at least a portion of the operations described herein can additionally or alternatively be performed using one or more passive devices 108a-c.

[0041] As used herein, “location” can refer to a physical and / or geographic location of one or more devices and / or users determined by any technique, technology, or system, or any combination of techniques, technologies, or systems, known or as yet unknown, for determining location parameters. Examples of such techniques, technologies, or systems may useP320505.W0.01 communication networks, such as global position system (GPS), satellite positioning system (SPS), or local positioning system (LPS) technology.

[0042] Advantageously, provenance and / or authenticity of the digital asset can be documented with enhanced security' using the distributed ledger 104, which is resistant to tampering or fraud because the transaction record is recorded in a distributed manner. This may improve user experience and encourage adoption of digital asset technologies (e.g.. digital memorabilia), for example, because users and / or collectors of digital assets will have evidence that a digital asset is authentic and is verified as having been received from a known source. Additionally, recording data related to a digital asset to the distributed ledger 104 may allow' for a public and reliable chain of title to be established, in the event that the digital asset is later transferred to subsequent recipients, such that a specific digital asset can be traced back to a specific source, such as to show that a digital autograph was in fact provided by a specific celebrity. Additional details about the digital asset and / or the transfer of the digital asset can also be documented on or using the distributed ledger 104, such as a specific time and / or place where the digital asset w as generated or transferred.

[0043] Components of the system 100 are illustrated as examples and may vary' in some embodiments. For example, in some embodiments, the exchange sendee 102 may be distributed across multiple computing elements, such that components of the exchange service 102 communicate with one another through the network 110. Further, the exchange service 102 may configure and / or instruct jobs to run on other computing devices, including various serverless jobs, configuration of containers, and the like. Further, in some embodiments, computing resources dedicated to the exchange service 102 may vary' over time based on various factors such as usage of the exchange service 102. In some embodiments, additional computing devices (including active devices, passive devices, or other types of computing devices) may communicate with the exchange sendee 102 and / or the distributed ledger 104.

[0044] While example operations described herein may relate to a transfer of a digital asset from a first user to a second user, e.g., sequentially, it will be appreciated that other implementations are possible. For example, the system 100 can be used to transfer a digital asset simultaneously, e.g., in parallel, to a large number of users (e.g., hundreds, thousands, hundreds of thousands) of devices 106a-b, 108a-c and in real time, such as to provide an item of digital memorabilia to attendees of a concert or other large event (e.g., in-person event, AR / VR event).

[0045] FIG. 2A is a block diagram illustrating example components for transferring digital assets using passive electronic devices in accordance with various embodiments of the disclosure. In the illustrated example, a digital asset is transferred using a first passive device 208a associated with a source 212 (e.g., a first user) and a second passive device 208b associated with a recipientP320505.W0.01214 (e.g., a second user). The passive devices 208a and 208b can be, for example, respective passive devices of the passive devices 108a-c of FIG. 1.

[0046] A digital asset associated with the source 212 is generated. For example, the digital asset may be generated using the passive device 208a, using a different device associated with the source 212 (not shown), or using the exchange service 202 (e.g., 102 of FIG. 1). The digital asset can be, for example, digital memorabilia (e.g.. a digital autograph, NFT, image, audio content). The digital asset is stored on or associated with the passive device 208a.

[0047] To initiate the transfer of the digital asset, a communication is initiated between the first passive device 208a and the second passive device 208b. In an example embodiment, the first passive device 208a and the second passive device 208b use NFC technology to communicate with one another, such that data can be exchanged, including authentication data and transaction data. For example, first authentication data regarding an authenticated identity of the source 212 can be communicated from the first passive device 208a to the second passive device 208b, and second authentication data regarding an authenticated identity of the recipient 214 can be communicated from the second passive device 208b to the first passive device 208a.Additionally, one or both of the first passive device 208a or the second passive device 208b may capture and transmit transaction data including information about the digital asset (e.g., one or more identifiers, a description, a copy or representation of the digital asset), time information (e.g., a timestamp), location information, and / or other data or metadata characterizing or documenting the digital asset or the transfer of the digital asset. In some implementations, digital asset data is provided from the first passive device 208a to the second passive device 208b, which may include an address (e.g., a URL) or other location (e.g., physical or virtual location) where the digital asset can be accessed. In these and other implementations, the digital asset data may additionally or alternatively be provided by the exchange service 202.

[0048] In some implementations, the first passive device 208a and / or the second passive device 208b may authenticate a respective user, such as by performing biometric authentication, while in these and other implementations authentication may be performed using a different device (e.g., the active device 206a), and an indication of the authentication may be provided to a respective passive device. While the illustrated example uses NFC technology, other communication technologies may be additionally or alternatively used, such as Bluetooth, WiFi, barcode scanning, or the like.

[0049] A transaction record is generated, for example, by the first passive device 208a. the second passive device 208b. the active device 206a. or the exchange service 202 (e.g., on a server). For example, after authentication information is exchanged between the first passive device 208a and the second passive device 208b, a transaction record can be generated thatP320505.W0.01 includes the first authentication data, the second authentication data, the transaction data, and / or other data (e.g., metadata) associated with the transfer of the digital asset.

[0050] One of devices (e.g., first passive device 208a, second passive device 208b, active device 206a, exchange service 202) may cause the transaction record to be recorded to the distributed ledger 204.

[0051] Upon completion of the transaction, the access to the digital asset can be provided via the second passive device 208b and / or the active device 206a. For example, the exchange service 202 may provide access to the digital asset based on the transaction record and via the network 210 using one or more of WiFi, cellular communications, Bluetooth, NFC, or the like. In some implementations, providing the access to the digital asset may include providing an access object, such as an object that includes metadata to restrict access to the digital asset (e.g.. to a particular user or device, in a particular place, at a particular time). For example, the digital asset may include various multimedia elements, such as images, messages, AR / VR experiences, or the like that may be accessed only at specific times and locations, and the access object can be provided to the active device 206a and / or the passive device 208b to provide the restricted access to the digital asset under the specified conditions. In these and other embodiments, the access object may be configured to block access or discontinue access to the digital asset when one or more conditions are not met, such as when a device requesting access to the digital object does not provide expected location information or when a present time does not match an expected time during which the digital asset is accessible.

[0052] FIG. 2B is a block diagram illustrating example components for transferring digital assets using a passive electronic device and an active electronic device in accordance with various embodiments of the disclosure. In the illustrated example, a digital asset is transferred using the first passive device 208a associated with the source 212 (e.g.. the first user) and the active device 206a associated with the recipient 214 (e.g., the second user). The passive device 208a can be, for example, one of passive devices 108a-c of FIG. 1, and the active device 206a can be one of active devices 106a-b of FIG. 1.

[0053] As in the example of FIG. 2A, the digital asset associated with the source 212 is generated. For example, the digital asset may be generated using the passive device 208a, using a different device associated with the source 212 (not shown), or using the exchange service 202 (e.g., 102 of FIG. 1). The digital asset can be, for example, digital memorabilia (e.g., a digital autograph, NFT, image, audio content). The digital asset is stored on or associated with the passive device 208a.

[0054] To initiate the transfer of the digital asset, a communication is initiated between the active device 206a and the first passive device 208a. In an example embodiment, the first passiveP320505.W0.01 device 208a and the active device 206a use NFC technology to communicate with one another, such that data can be exchanged, including authentication data and transaction data. For example, first authentication data regarding an authenticated identity of the source 212 can be communicated from the first passive device 208a to the active device 206a, and second authentication data regarding an authenticated identity of the recipient 214 can be communicated from the active device 206a to the first passive device 208a. Additionally, one or both of the first passive device 208a or the active device 206a may capture and transmit transaction data including information about the digital asset (e.g., one or more identifiers, a description, a copy or representation of the digital asset), time information (e.g., a timestamp), location information, and / or other data or metadata characterizing or documenting the digital asset or the transfer of the digital asset. In some implementations, digital asset data is provided from the first passive device 208a to the active device 206a, which may include an address (e.g., a URL) or other location (e.g., physical or virtual location) where the digital asset can be accessed. In these and other implementations, the digital asset data may additionally or alternatively be provided by the exchange service 202.

[0055] In some implementations, the first passive device 208a and / or the active device 206a may authenticate a respective user, such as by performing biometric authentication, while in these and other implementations authentication may be performed using a different device, and an indication of the authentication may be provided to a respective device associated with a respective user. While the illustrated example uses NFC technology, other communication technologies may be additionally or alternatively used, such as Bluetooth, WiFi, barcode scanning, or the like.

[0056] A transaction record is generated, for example, by the first passive device 208a. the active device 206a, or the exchange service 202 (e.g., on a server). For example, after authentication information is exchanged between the first passive device 208a and the active device 206a, a transaction record can be generated that includes the first authentication data, the second authentication data, the transaction data, and / or other data (e.g., metadata) associated with the transfer of the digital asset.

[0057] One or more of the devices (e.g., first passive device 208a, active device 206a, exchange service 202) may cause the transaction record to be recorded to the distributed ledger 204.

[0058] Upon completion of the transaction, the access to the digital asset can be provided via the active device 206a. For example, the exchange service 202 may provide access to the digital asset based on the transaction record and via the network 210 using one or more of WiFi, cellular communications, Bluetooth, NFC, or the like. In some implementations, providing the access to the digital asset may include providing an access object, such as an object that includes metadataP320505.W0.01 to restrict access to the digital asset (e.g., to a particular user or device, in a particular place, at a particular time). For example, the digital asset may include various multimedia elements, such as images, messages, AR / VR experiences, or the like that may be accessed only at specific times and locations, and the access object can be provided to the active device 206a to provide the restricted access to the digital asset under the specified conditions. In these and other embodiments, the access object may be configured to block access or discontinue access to the digital asset when one or more conditions are not met, such as when a device requesting access to the digital object does not provide expected location information or when a present time does not match an expected time during which the digital asset is accessible.

[0059] FIG. 2C is a block diagram illustrating example components for transferring digital assets using an active electronic device and a passive electronic device in accordance with vanous embodiments of the disclosure. In the illustrated example, a digital asset is transferred using an active device 206b associated with the source 212 (e.g., the first user) and the passive device 208b coupled to the active device 206a associated with the recipient 214 (e.g., the second user). The passive device 208b can be, for example, one of passive devices 108a-c of FIG. 1, and the active devices 206a & 206b can be respective ones of active devices 106a-b of FIG. 1.

[0060] As in the example of FIGs. 2A & 2B, the digital asset associated with the source 212 is generated. For example, the digital asset may be generated using the active device 206b associated with the source 212 or using the exchange service 202 (e.g., 102 of FIG. 1). The digital asset can be, for example, digital memorabilia (e.g., a digital autograph, NFT, image, audio content). The digital asset is stored on or associated with the active device 206b.

[0061] To initiate the transfer of the digital asset, a communication is initiated between the active device 206b and the passive device 208b. In an example embodiment, the active device 206b and the passive device 208b use NFC technology to communicate with one another, such that data can be exchanged, including authentication data and transaction data. For example, first authentication data regarding an authenticated identity of the source 212 can be communicated from the active device 206b to the passive device 208b, and second authentication data regarding an authenticated identity of the recipient 214 can be communicated from the passive device 208b to the active device 206b. Additionally, one or both of the passive device 208b or the active device 206b may capture and transmit transaction data including information about the digital asset (e.g., one or more identifiers, a description, a copy or representation of the digital asset), time information (e.g., a timestamp), location information, and / or other data or metadata characterizing or documenting the digital asset or the transfer of the digital asset. In some implementations, digital asset data is provided from the active device 206b to the passive device 208b, which may include an address (e.g., a URL) or other location (e.g., physical or virtualP320505.W0.01 location) where the digital asset can be accessed. In these and other implementations, the digital asset data may additionally or alternatively be provided by the exchange service 202.

[0062] In some implementations, the active device 206b and / or the passive device 208b may authenticate a respective user, such as by performing biometric authentication, while in these and other implementations authentication may be performed using a different device (e g., active device 206a). and an indication of the authentication may be provided to a respective device associated with a respective user. While the illustrated example uses NFC technology, other communication technologies may be additionally or alternatively used, such as Bluetooth, WiFi, barcode scanning, or the like.

[0063] A transaction record is generated, for example, by the active devices 206a-b, the passive device 208b, or the exchange service 202 (e.g., on a server). For example, after authentication information is exchanged between the active device 206b and the passive device 208b, a transaction record can be generated that includes the first authentication data, the second authentication data, the transaction data, and / or other data (e.g., metadata) associated with the transfer of the digital asset.

[0064] One or more of the devices (e.g., active device 206b, passive device 208b, active device 206a, exchange service 202) may cause the transaction record to be recorded to the distributed ledger 204.

[0065] Upon completion of the transaction, the access to the digital asset can be provided via the active device 206a and / or the passive device 208b. For example, the exchange service 202 may provide access to the digital asset based on the transaction record and via the network 210 using one or more of WiFi, cellular communications, Bluetooth, NFC, or the like. In some implementations, providing the access to the digital asset may include providing an access object, such as an object that includes metadata to restrict access to the digital asset (e.g.. to a particular user or device, in a particular place, at a particular time). For example, the digital asset may include various multimedia elements, such as images, messages, AR / VR experiences, or the like that may be accessed only at specific times and locations, and the access object can be provided to the active device 206a to provide the restricted access to the digital asset under the specified conditions. In these and other embodiments, the access object may be configured to block access or discontinue access to the digital asset when one or more conditions are not met, such as when a device requesting access to the digital obj ect does not provide expected location information or when a present time does not match an expected time during which the digital asset is accessible.

[0066] FIG. 2D is a block diagram illustrating example components for transferring digital assets using active electronic devices in accordance with various embodiments of the disclosure. In theP320505.W0.01 illustrated example, a digital asset is transferred using the active device 206b associated with the source 212 (e.g., the first user) and the active device 206a associated with the recipient 214 (e.g.. the second user). The active devices 206a & 206b can be respective ones of active devices 106a- b of FIG. 1.

[0067] As in the example of FIGs. 2A, 2B, and 2C, the digital asset associated with the source 212 is generated. For example, the digital asset may be generated using the active device 206b associated with the source 212 or using the exchange service 202 (e.g., 102 of FIG. 1). The digital asset can be, for example, digital memorabilia (e.g., a digital autograph, NFT, image, audio content). The digital asset is stored on or associated with the active device 206b.

[0068] To initiate the transfer of the digital asset, a communication is initiated between the active device 206b and the active device 206a. In an example embodiment, the active device 206b and the active device 206a use NFC technology to communicate with one another, such that data can be exchanged, including authentication data and transaction data. For example, first authentication data regarding an authenticated identity of the source 212 can be communicated from the active device 206b to the active device 206a. and second authentication data regarding an authenticated identity of the recipient 214 can be communicated from the active device 206a to the active device 206b. Additionally, one or both of the active device 206a or the active device 206b may capture and transmit transaction data including information about the digital asset (e.g., one or more identifiers, a description, a copy or representation of the digital asset), time information (e.g., a timestamp), location information, and / or other data or metadata characterizing or documenting the digital asset or the transfer of the digital asset. In some implementations, digital asset data is provided from the active device 206b to the active device 206a, which may include an address (e.g., a URL) or other location (e.g., physical or virtual location) where the digital asset can be accessed. In these and other implementations, the digital asset data may additionally or alternatively be provided by the exchange service 202.

[0069] In some implementations, the active device 206b and / or the active device 206a may authenticate a respective user, such as by performing biometric authentication, while in these and other implementations authentication may be performed using a different device, and an indication of the authentication may be provided to a respective device associated with a respective user. While the illustrated example uses NFC technology7, other communication technologies may be additionally or alternatively used, such as Bluetooth, WiFi, barcode scanning, or the like.

[0070] A transaction record is generated, for example, by the active devices 206a-b or the exchange service 202 (e.g., on a server). For example, after authentication information is exchanged between the active device 206b and the active device 206a, a transaction record canP320505.W0.01 be generated that includes the first authentication data, the second authentication data, the transaction data, and / or other data (e.g., metadata) associated with the transfer of the digital asset.

[0071] One or more of the devices (e.g., active device 206b, active device 206a, exchange service 202) may cause the transaction record to be recorded to the distributed ledger 204.

[0072] Upon completion of the transaction, the access to the digital asset can be provided via the active device 206a. For example, the exchange service 202 may provide access to the digital asset based on the transaction record and via the network 210 using one or more of WiFi, cellular communications, Bluetooth, NFC, or the like. In some implementations, providing the access to the digital asset may include providing an access object, such as an object that includes metadata to restrict access to the digital asset (e.g., to a particular user or device, in a particular place, at a particular time). For example, the digital asset may include various multimedia elements, such as images, messages, AR / VR experiences, or the like that may be accessed only at specific times and locations, and the access object can be provided to the active device 206a to provide the restricted access to the digital asset under the specified conditions. In these and other embodiments, the access object may be configured to block access or discontinue access to the digital asset when one or more conditions are not met, such as when a device requesting access to the digital object does not provide expected location information or when a present time does not match an expected time during which the digital asset is accessible.

[0073] FIG. 3 is a block diagram illustrating an example computing system 300 used in various examples of the disclosure. For example, in various embodiments, components of the exchange service 102 and / or computing devices in communication with the exchange service 102 may be implemented by one or several computing systems 300. This disclosure contemplates any suitable number of computing systems 300. For example, the computing system 300 may be a server, a desktop computing system, a mainframe, a mesh of computing systems, a laptop or notebook computing system, a tablet computing system, an embedded computer system, a system-on-chip, a single-board computing system, or a combination of two or more of these. Where appropriate, the computing system 300 may include one or more computing systems; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks.

[0001] Computing system 300 includes a bus 310 (e.g., an address bus and a data bus) or other communication mechanism for communicating information, which interconnects subsystems and devices, such as processor 308, memory7302 (e.g., RAM), static storage 304 (e.g., ROM), dynamic storage 306 (e.g., magnetic or optical), communications interface 316P320505.W0.01(e.g., modem, Ethernet card, a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network, a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network), input / output (I / O) interface 320 (e.g., keyboard, keypad, mouse, microphone). In particular embodiments, the computing system 300 may include one or more of any such components.

[0002] In particular embodiments, processor 308 includes hardware for executing instructions, such as those making up a computer program. For example, a processor 308 may execute instructions for various components of a biomarker analysis system. The processor 308 circuity includes circuitry for performing various processing functions, such as executing specific software for performing specific calculations or tasks. In particular embodiments, I / O interface 320 includes hardware, software, or both, providing one or more interfaces for communication between computing system 300 and one or more I / O devices. Computing system 300 may include one or more of these I / O devices, where appropriate. One or more of these I / O devices may enable communication between a person and computing system 300.

[0003] In particular embodiments, the communications interface 316 includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) between computing system 300 and one or more other computer systems or one or more networks. One or more memory' buses (which may each include an address bus and a data bus) may couple processor 308 to memory' 302. Bus 310 may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor 308 and memory 302 and facilitate accesses to memory' 302 requested by processor 308. In particular embodiments, bus 310 includes hardware, software, or both coupling components of computing system 300 to each other.

[0004] According to particular embodiments, computing system 300 performs specific operations by processor 308 executing one or more sequences of one or more instructions contained in memory 302. For example, instructions for various portions of the methods described herein may be contained in memory 302 and may be executed by the processor 308. Such instructions may be read into memory 302 from another computer readable / usable medium, such as static storage 304 or dynamic storage 306. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions. Thus, particular embodiments are not limited to any specific combination of hardware circuitry and / or software. In various embodiments, the term “logic” means any combinationP320505.W0.01 of software or hardware that is used to implement all or part of particular embodiments disclosed herein.

[0005] The term “computer readable medium” or “computer usable medium” as used herein refers to any medium that participates in providing instructions to processor 508 for execution. Such a medium may take many forms, including but not limited to, nonvolatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as static storage 304 or dynamic storage 306. Volatile media includes dynamic memory, such as memory 302.

[0074] Computing system 300 may transmit and receive messages, data, and instructions, including program, e.g., application code, through communications link 318 and communications interface 316. Received program code may be executed by processor 308 as it is received, and / or stored in static storage 304 or dynamic storage 306, or other storage for later execution. A database 314 may be used to store data accessible by the computing system 300 by way of data interface 312. In various examples, a communications link 318 may communicate with computing components within a network.

[0075] FIG. 4 is a flow diagram illustrating a process 400 for transferring digital assets using systems and methods described herein. For example, the process 400 can be performed using at least a portion of the system 100 of FIG. 1 and / or using one or more computing systems 300 of FIG. 3.

[0076] At block 402, an identity of a first user is authenticated at a first device (e.g., 106a-b, 108a-c of FIG. 1). The first user may be a source of a digital asset, and the identity of the first user may be authenticated using various techniques described herein, such as biometric authentication, password or PIN authentication, or the like.

[0077] Transaction data associated with transfer of a digital asset is generated at block 404. The transaction data can include, for example, information about the digital asset, such as an identifier, time information, location information, user information, a copy or representation of the digital asset, and so forth. At least a portion of the transaction data can be generated by the first device.

[0078] At block 406, the transaction data is transferred to a second device (e.g., 106a-b, 108a-c of FIG. 1) associated with a second user. The second user may be a recipient of the digital asset, and the transaction data is received at the second device to transfer the digital asset.

[0079] The transfer of the digital asset is recorded at a distributed ledger at block 408. For example, the transaction data and / or captured authentication data can be recorded to the distributed ledger, and one or both of the first device or the second device may cause the recordation of the data. In some embodiments, both devices cause the data to be recorded to theP320505.W0.01 distributed ledger, and the recorded data is compared to confirm that the data recorded from the respective devices match.

[0080] At block 410, the digital asset is delivered to a location associated with the second user. For example, a URL can be provided to the second device, and the URL can be accessed to receive the digital asset.

[0081] FIG. 5 is a flow diagram illustrating a process 500 for authenticated transfer of a digital asset. For example, the process 500 can be performed using at least a portion of the system 100 of FIG. 1 and / or using one or more computing systems 300 of FIG. 3. The process 500 may be initiated by a source user device or a recipient user device. Additionally or alternatively, the process 500 may be initiated by the exchange service of the disclosed technology. For example, a user of the disclosed system may initiate the process 500 to cause transfer of a digital asset from or associated with a source device to one or more recipient devices.

[0082] The process 500 begins at block 510, where first authentication data is generated. Generating the first authentication data can include authenticating an identity of a first user of a first device (e.g., 106a-b. 108a-c of FIG. 1). For example, the first user can be a source of a digital asset, and the first device can be a computing device associated with the first user. The first authentication data can be an indication that the identity of the first user has been authenticated, such as by using biometric authentication data (e g., fingerprint scanning, iris scanning, facial recognition) and / or other authentication techniques (e.g., passwords, PINs).

[0083] The process 500 proceeds to block 520, where transaction data associated with transfer of a digital asset is generated. At least a portion of the transaction data can be generated by the first device associated with the first user. The transaction data can include data associated with a digital asset, such as an identifier, description, and / or copy or thumbnail of the digital asset. Transaction data can additionally or alternatively include identifying information of a source and a recipient of the digital asset, information associated with generating or capturing the digital asset (e.g., location information, time information), or the like.

[0084] The process 500 proceeds to block 530, where the transaction data and the first authentication data are transmitted (e.g., by the first device) to a second device (e.g., 106a-b, 108a-c of FIG. 1) associated with a second user. In some embodiments, the transaction data and the first authentication data are communicated directly from the first device to the second device. In some implementations, the transaction data and the first authentication data are provided via the exchange service.

[0085] The process 500 proceeds to block 540, where second authentication data associated with the second user is received. For example, responsive to the transaction data and / or the first authentication data being provided to the second device, the second device may provide theP320505.W0.01 second authentication data to the first device. The second authentication data can be an indication that the identity of the second user has been authenticated, such as by using biometric authentication data (e.g., fingerprint scanning, iris scanning, facial recognition) and / or other authentication techniques (e.g., passwords, PINs).

[0086] The process 500 proceeds to block 550, where a transaction record is caused to be recorded to a distributed ledger. The transaction record can include the transaction data, the first authentication data, and the second authentication data.

[0087] In various embodiments, the transaction data can include access information for the digital asset and metadata associated with the digital asset. For example, the transaction data can include data related to the context in which the digital asset was generated and / or information about how the digital asset can be accessed.

[0088] In various embodiments, the second device can be (or can be coupled to) a passive electronic device. In these and other embodiments, the transaction data is communicated from the second device to a third device associated with the second user using the passive electronic device.

[0089] In various embodiments, the process 500 further includes generating and transmitting an access object configured to provide access to the digital asset. The access object can include metadata to restrict the access to the digital asset based on at least one of a time or a location.

[0090] In various embodiments, authenticating the identity of the first user of the first device includes capturing, using the first device, biometric data associated with the first user. For example, a fingerprint of the first user can be captured and used to perform the authentication, or a facial image of the first user can be captured and used to perform the authentication.

[0091] FIG. 6 is a flow diagram illustrating a process 600 for providing access to a digital asset. For example, the process 600 can be performed using at least a portion of the system 100 of FIG. 1 and / or using one or more computing systems 300 of FIG. 3. In an embodiment, at least a portion of the process 600 is performed by a server computer of the exchange sendee of the disclosed technology.

[0092] The process 600 begins at block 610, where transaction data and authentication data are received, the transaction data and authentication data having been generated in association with transfer of a digital asset. The authentication data includes an indication of an identity of a first user associated with a first device (e.g., 106a-b, 108a-c of FIG. 1) and a second user associated with a second device (e.g., 106a-b. 108a-c of FIG. 1). The respective devices may authenticate respective users, and an indication of the authentication can be generated and provided to a server computer. The transaction data relates to a transfer of a digital asset, and may include information about the digital asset and / or the parties to the transfer. In various embodiments, theP320505.W0.01 transaction data includes access information for the digital asset and metadata associated with the transfer of the digital asset. In various embodiments, at least a portion of the transaction data, the authentication data, or both are generated using a passive electronic device coupled to the first device or the second device.

[0093] The process 600 proceeds to block 620, where a transaction record for the transfer of the digital asset is generated. The transaction record includes the transaction data and the authentication data.

[0094] The process 600 proceeds to block 630, where the transaction record for the transfer of the digital asset is caused to be recorded at a distributed ledger. For example, a server computer and / or one or more user devices may cause the transaction record to be recorded to a blockchain.

[0095] The process 600 proceeds to block 640, where access to the digital asset is provided. In various embodiments, the server may transmit access information to a user device to provide access to the digital asset. The access information may include a URL or other location information.

[0096] In various embodiments the process 600 further includes generating an access object configured to provide access to the digital asset. The access object can be generated, for example, by a server computer, by the first device, or by the second device. The access object can include metadata to restrict the access to the digital asset based on at least one of a time or a location.

[0097] The processes 400, 500, and 600 can be performed in a different order while maintaining a similar functionality. Additionally, one or more operations of the processes 400, 500, or 600 can be repeated, and one or more operations can be performed in parallel.

[0098] The technology described herein may be implemented as logical operations and / or modules in one or more systems. The logical operations may be implemented as a sequence of processor-implemented steps directed by software programs executing in one or more computer systems and as interconnected machine or circuit modules within one or more computer systems, or as a combination of both. Likewise, the descriptions of various component modules may be provided in terms of operations executed or effected by the modules. The resulting implementation is a matter of choice, dependent on the performance requirements of the underlying system implementing the described technology. Accordingly, the logical operations making up the embodiments of the technology described herein are referred to variously as operations, steps, objects, or modules. Furthermore, it should be understood that logical operations may be performed in any order, unless explicitly claimed otherwise or a specific order is inherently necessitated by the claim language.P320505.W0.01

[0099] In some implementations, articles of manufacture are provided as computer program products that cause the instantiation of operations on a computer system to implement the procedural operations. One implementation of a computer program product provides a non- transitory computer program storage medium readable by a computer system and encoding a computer program. It should further be understood that the described technology may be employed in special purpose devices independent of a personal computer.

[0100] The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments of the invention as defined in the claims. Although various embodiments of the claimed invention have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, it is appreciated that numerous alterations to the disclosed embodiments without departing from the spirit or scope of the claimed invention may be possible. Other embodiments are therefore contemplated. It is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative only of particular embodiments and not limiting. Changes in detail or structure may be made without departing from the basic elements of the invention as defined in the following claims.

Claims

P320505.W0.01CLAIMSWhat is claimed is:

1. A computer-implemented method comprising: generating first authentication data by authenticating an identity of a first user of a first device; generating transaction data associated with transfer of a digital asset; transmitting the transaction data and the first authentication data to a second device associated with a second user; receiving second authentication data associated with the second user; and causing a transaction record to be recorded to a distributed ledger, the transaction record comprising the transaction data, the first authentication data, and the second authentication data.

2. The computer-implemented method of claim 1, wherein the transaction data comprises access information for the digital asset and metadata associated with the transfer of the digital asset.

3. The computer-implemented method of claim 1, wherein the second device comprises or is coupled to a passive electronic device, and wherein the method further comprises communicating, from the second device, the transaction data to a third device associated with the second user using the passive electronic device.

4. The computer-implemented method of claim 1, further comprising: generating and transmitting an access object configured to provide access to the digital asset.

5. The computer-implemented method of claim 4, wherein the access object comprises metadata to restrict the access to the digital asset based on at least one of a time or a location.

6. The computer implemented method of claim 1, wherein authenticating the identity of the first user of the first device includes capturing, using the first device, biometric data associated with the first user.

7. A computer-implemented method comprising:P320505.W0.01 receiving transaction data and authentication data having been generated in association with transfer of a digital asset, wherein the authentication data comprises an indication of an identity of a first user associated with a first device and a second user associated with a second device; generating a transaction record for the transfer of the digital asset, wherein the transaction record includes the transaction data and the authentication data; causing the transaction record for the transfer of the digital asset to be recorded at a distributed ledger; and providing access to the digital asset.

8. The computer-implemented method of claim 7, wherein the transaction data comprises access information for the digital asset and metadata associated with the transfer of the digital asset.

9. The computer-implemented method of claim 7, wherein at least a portion of the transaction data, the authentication data, or both are generated using a passive electronic device coupled to the first device or the second device.

10. The computer implemented method of claim 7, further comprising: generating an access object configured to provide access to the digital asset.

11. The computer-implemented method of claim 10, wherein the access object is generated by a server computer.

12. The computer-implemented method of claim 10, wherein the access object is generated by the first device or the second device.

13. The computer-implemented method of claim 10. wherein the access object comprises metadata to restrict the access to the digital asset based on at least one of a time or a location.

14. One or more non-transitory computer-readable media carrying instructions which, when executed by one or more processors, cause a computing system to perform operations comprising:P320505.W0.01 generate first authentication data by authenticating an identity of a first user of a first device; generate transaction data associated with transfer of a digital asset; transmit the transaction data and the first authentication data to a second device associated with a second user; receive second authentication data associated with the second user; and cause a transaction record to be recorded to a distributed ledger, the transaction record comprising the transaction data, the first authentication data, and the second authentication data.

15. The one or more non-transitory computer-readable media of claim 14. wherein the transaction data comprises access information for the digital asset and metadata associated with the transfer of the digital asset.

16. The one or more non-transitory computer-readable media of claim 14. wherein the first device, the second device, or both are coupled to a passive electronic device.

17. The one or more non-transitory computer-readable media of claim 14, wherein the operations further comprise: generate and transmit an access object configured to provide access to the digital asset.

18. The one or more non-transitory computer-readable media of claim 17, wherein the access object comprises metadata to restrict the access to the digital asset based on at least one of a time or a location.

19. The one or more non-transitory computer readable media of claim 14, wherein authenticating the identity of the first user of the first device includes capturing, using the first device, biometric data associated with the first user.

20. The one or more non-transitory computer readable media of claim 14, w herein the transaction record is caused to be recorded to the distributed ledger by both the first device and the second device.

Images