Decentralized programmed digital asset creation in augmented reality applications

Abstract

Example implementations include methods, apparatuses, and computer readable media for decentralized programmed digital asset creation including receiving a first request application to create a digital asset from an application executing augmented reality effects on a computing device, where the first request includes an identifier associated with a user of the application. Implementations additionally include generating the digital asset and metadata for the digital asset, wherein the metadata includes information about characteristics of the digital asset and ownership of the user to the digital asset. In addition, the implementation additionally includes storing the metadata on the blockchain. In addition, the implementation additionally includes receiving a second request from the application to access the digital asset. Furthermore, the implementations additionally include, in response to verifying the identifier associated with the user in the second request, transmitting metadata stored on the blockchain to the application for rendering.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. application serial number 17 / 737,569, filed on May 5, 2022, and entitled “DECENTRALIZED PROCEDURAL DIGITAL ASSET CREATION IN AUGMENTED REALITY APPLICATIONS,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The aspects relate to distributed ledger systems. Background Art

[0004] Aspects of the present disclosure relate generally to distributed ledger systems and, more particularly, to decentralized programmatic digital asset creation in augmented reality applications.

[0005] Collaboration and social interaction drive creativity in the modern world. However, with traditional tokens / assets, which are non-interchangeable and typically handcrafted by artists into 2D images, the creation process stops once the asset is produced. This is because such assets remain largely unchanged. Apart from the transfer of ownership of the asset, not much happens once the asset is created (e.g., no modifications). The creation of assets is also not easy for the average person who is not familiar with smart contracts and distributed ledgers. Therefore, a more accessible method is needed to create assets that can be modified to promote creativity and provide efficient storage of the modified assets. Summary of the invention

[0006] A brief summary of one or more aspects is presented below to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] Example aspects include a method for decentralized programmatic digital asset creation, including receiving a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application. The method also includes generating a digital asset and metadata for the digital asset, wherein the metadata includes information about characteristics of the digital asset and ownership of the digital asset by the user. In addition, the method also includes storing the metadata on a blockchain. In addition, the method also includes receiving a second request from the application to access the digital asset. In addition, the method also includes transmitting and storing the metadata on the blockchain to the application for rendering in response to verifying the identifier associated with the user in the second request.

[0008] Another example aspect includes an apparatus for decentralized programmatic digital asset creation, comprising a memory and a processor, the processor being communicatively coupled to the memory. The processor is configured to receive a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application. The processor is also configured to generate a digital asset and metadata for the digital asset, wherein the metadata includes information about the characteristics of the digital asset and the user's ownership of the digital asset. In addition, the processor is further configured to store the metadata on a blockchain. In addition, the processor is further configured to receive a second request to access the digital asset from the application. In addition, the processor is further configured to transmit the metadata stored on the blockchain to the application for rendering in response to verifying the identifier associated with the user in the second request.

[0009] Another example aspect includes an apparatus for decentralized programmatic digital asset creation, including a first request component for receiving a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application. The apparatus also includes a component for generating a digital asset and metadata for the digital asset, wherein the metadata includes information about the characteristics of the digital asset and the user's ownership of the digital asset. In addition, the apparatus also includes a component for storing the metadata on a blockchain. In addition, the apparatus also includes a component for receiving a second request from the application to access the digital asset. In addition, the apparatus also includes a component for sending the metadata stored on the blockchain to the application for rendering in response to verifying the identifier associated with the user in the second request.

[0010] Another example aspect includes a computer-readable medium having stored thereon instructions for decentralized programmatic digital asset creation, wherein the instructions are executable by a processor to receive a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application. The instructions are further executable to generate a digital asset and metadata for the digital asset, wherein the metadata includes information about characteristics of the digital asset and the user's ownership of the digital asset. Further, the instructions are further executable to store the metadata on a blockchain. Further, the instructions are further executable to receive a second request from the application to access the digital asset. Further, the instructions are further executable to transmit the metadata stored on the blockchain to the application for rendering in response to verifying the identifier associated with the user in the second request.

[0011] To accomplish the foregoing and related ends, one or more aspects include features fully described hereinafter and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more example aspects of the disclosure and, together with the detailed description, serve to explain the principles and implementations thereof.

[0013] Figure 1 A diagram depicting multiple screens of an augmented reality application as a user interacts with a digital asset according to an exemplary aspect of the present disclosure.

[0014] Figure 2 A diagram depicting a system for decentralized programmatic digital asset creation according to an exemplary aspect of the present disclosure.

[0015] Figure 3 A block diagram of a computing device executing a digital asset management component according to an exemplary aspect of the present disclosure.

[0016] Figure 4 A flowchart illustrating a method of generating a digital asset and storing metadata of the digital asset on a blockchain according to an exemplary aspect of the present disclosure.

[0017] Figure 5 A flowchart illustrating a method of modifying a digital asset and storing metadata of the modified digital asset on a blockchain according to an exemplary aspect of the present disclosure.

[0018] Figure 6A flowchart illustrating a method of transferring ownership of a digital asset and storing ownership metadata of the digital asset on a blockchain according to an exemplary aspect of the present disclosure. DETAILED DESCRIPTION

[0019] Various aspects are now described with reference to the accompanying drawings. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it is clear that such aspects can be practiced without these specific details.

[0020] The present disclosure provides a new method for generating a potentially infinite collection of 2D or 3D digital assets, storing their metadata on a distributed ledger (e.g., a blockchain), and allowing the assets to be dynamically modified if the creator so chooses. The systems and methods of the present disclosure enable users to make new program-generated digital assets in a virtual environment (e.g., a graphical user interface of an augmented reality (AR) application, a virtual reality application, or a 2D graphics creation application). When a user interacts and modifies a digital asset, the commands made by the user are sent to a smart contract that is configured to generate metadata that encapsulates a storage-efficient representation of the modified digital asset, and stores the metadata on the blockchain. Storage efficiency is important because storing images or 3D models in a distributed ledger is expensive. The metadata method of the present disclosure reduces costs by storing only the necessary parameters to the generation algorithm.

[0021] Subsequently, the rendering client (e.g., an AR application) can retrieve the metadata from the blockchain and deserialize the metadata to render the digital asset. In some aspects, if the digital asset creator adds functionality to the digital asset, the user can complete actions in the virtual environment that can update the state of the digital asset (such as changing the appearance, destroying, transferring, or generating a new digital asset).

[0022] Figure 1 A diagram depicting multiple screens of an AR application when a user interacts with digital assets on a computing device according to an exemplary aspect of the present disclosure. Application 102 may be, but is not limited to, a social media application with AR features executed on a computing device. For example, application 102 may be a social media application where users create and share visual content such as videos, photos, filters, etc. Screens 100, 110, 120, and 130 may be screenshots of application 102 as user 104 interacts with application 102 over a period of time.

[0023] Screen 100 depicts an image of user 104 generated when the user activates the selfie camera on his / her computing device (e.g., a smart phone). Interface buttons 106 may be selectable options that enable user 104 to access different types of visual content. For example, interface buttons 106 may be different AR modes. Suitable examples of different AR modes include, but are not limited to, graphics, emoticons, icons, and various overlay 2D, 3D, and / or AR effects, etc. If the user selects a specific button associated with a specific AR mode, the corresponding AR mode effect is initialized. For example, in screen 110, user 104 has selected button 112 to activate AR effect 114. In this example of screen 110, AR effect 114 generates an overlay of flowers along the edge of screen 110. It should be noted that although an example of flowers is provided in the present disclosure, AR effect 114 may relate to or depict any object (e.g., an animal, a person, a cartoon, a vehicle, etc.) and the digital asset generated by AR effect 114 may also be any object.

[0024] Subsequently, user 104 may then interact with the floral overlay. For example, user 104 may click on the floral overlay, and this may produce an animation of a new flower sprouting as the edges fade away. It should be noted that user 104 may interact with AR effect 114 in any manner based on the functionality of AR effect 114. For example, AR effect 114 may prompt user 104 to select a flower from a plurality of flowers shown in the floral overlay, causing the selected flower to be generated on screen 120. In another example, AR effect 114 may prompt user 104 to pull all flowers in the floral overlay to the center of screen 110, which results in the generation of a new flower shown on screen 120.

[0025] In screen 120, user 104 has generated a digital asset 122 (i.e., a new flower). In this disclosure, a digital asset is defined as a visual object generated by interacting with an AR effect. In some aspects, a digital asset is a non-interchangeable token. Figure 1104 , the digital asset 122 is a flower that can be customized according to the functions programmed into the flower by the digital asset creator (e.g., the developer of AR effect 114). For example, the user may be able to change the size, color, transparency, and physical features of the flower (i.e., digital asset 122) in screen 120. In this case, for example, such changes may include adding more flowers, removing petals, enlarging petals, reducing the size of the core, adding leaves, etc. The customization capabilities are endless, as the digital asset creator may even program the digital asset 122 to change according to the user's use of application 102 (e.g., the frequency with which the user accesses features of application 102 determines the size / color of the flower). For example, in screen 130, user 104 adjusts digital asset 122 by adding additional flowers. Such modifications may occur by clicking on the flower to add a new flower or by following a prompt on the AR application indicating how to add a flower. Thus, in this case, digital asset 132 is a modified version of digital asset 122.

[0026] Figure 2 A diagram of a system 200 for decentralized programmatic digital asset creation according to exemplary aspects of the present disclosure is depicted. System 200 includes a rendering client 202, which may be any application such as application 102, and / or any device capable of presenting content on a user interface. Rendering client 202 enables a user to make and / or update digital assets by providing the user interface with the option to make and / or update digital assets. For example, a user may interact with AR effect 114 to generate digital assets 112. Requests / commands involved in the interaction are transmitted to bridge server 204 by rendering client 202, which routes the requests / commands from client 202 to smart contract 206. Bridge server 204 may be a computing device having a memory, a processor, and a communication interface. In particular, because digital assets 122 are generated by user interaction with AR effect 114, the corresponding requests / commands are considered to be requests to make digital assets.

[0027] Smart contract 206 may be a software program stored on blockchain 208 that runs when certain predetermined conditions are met. Such conditions include receiving a request to generate a digital asset, modify a digital asset, change ownership of a digital asset, delete a digital asset, etc. Smart contract 206 is specifically configured to generate digital asset metadata based on requests / commands made by a user and store the metadata on blockchain 208.

[0028] For example, the user 104 may interact with the AR effect 114 and request the generation of the digital asset 122. The rendering client 202 may send a request to the bridge server 204, which identifies the smart contract 206 associated with the AR effect 114. The bridge server 204 may additionally provide a unique identifier associated with the user 104 (e.g., an address of a computing device where the application 102 is installed). The smart contract 206 may verify that the request is from the user (e.g., by verifying the unique identifier), and in response to determining that the request is from the user, the smart contract 206 may execute the request to manufacture the digital asset 122. The smart contract 206 may additionally generate metadata 210, which is a representation of the digital asset 122, and store the metadata 210 in block 1 of the blockchain 208.

[0029] In some aspects, the metadata 210 may be any representation of the digital asset 122 that may be used to recreate the digital asset 122 on the rendering client 202. The metadata 210 may include information about the digital asset 122 in a data structure (e.g., a vector) or a mathematical formula (e.g., a polynomial representation) (e.g., the number, size, color, etc. of petals). Because storing the digital asset itself on the blockchain 208 is inefficient in terms of storage usage, storing the metadata allows the digital asset to be recreated on the rendering client 202 upon request without taking up too much storage space.

[0030] After generating digital asset 122, the user can modify digital asset 122. The request to modify digital asset 122 is again conveyed to smart contract 206 via bridge server 204. In response to verifying that the modification is authorized based on the unique identifier of user 104, smart contract 206 can generate digital asset 132 and metadata 212 that details the modifications made to digital asset 122 to create digital asset 132. For example, metadata 212 can indicate an updated number of petals. Smart contract 206 stores metadata 212 in block 2 of blockchain 208.

[0031] In other words, when a user changes a digital asset 122 or 132, smart contract 208 populates blockchain 208. For example, blockchain 208 may extend up to block N, where N is an integer, and where each block includes information about the modifications made by the user.

[0032] refer to Figure 3 and Figure 4 In operation, computing device 300 may perform method 400 of decentralized programmatic digital asset creation, such as via execution of digital asset management component 315 via processor 305 and / or memory 310 .

[0033] At block 402, method 400 includes receiving a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or receiving component 320 may be configured to or may include means for receiving a first request to create a digital asset 122 from application 102 executing an AR effect 114 on the computing device, wherein the first request includes an identifier associated with user 104 of application 102.

[0034] In some aspects, the first request includes at least one user identifier unique to the user 104 and an action list including commands / requests from the interaction between the user 104 and the AR effect 114 on the rendering client 202. In some aspects, the user identifier is a combination of characters unique to the user 104. For example, the user identifier may be a wallet address of a wallet in which assets owned by the user are stored. A wallet is a software program or physical device that enables the storage of digital assets such as digital assets 122. The wallet may additionally include private and public encryption keys, wherein the public key is derived from the private key and may be a wallet address for exchanging digital assets. For example, the wallet address may be a combination of alphanumeric characters unique to the user 104.

[0035] Receiving at block 402 may involve the smart contract 206 receiving the action list and the user's wallet address via the bridge server 204. For example, the user 104 may select a flower on the floral overlay of the AR effect 114, and the selected action is recorded by the rendering client 202 and sent to the bridge server 204 in an action list. The bridge server 204 may forward the action list to the smart contract 206.

[0036] The receiving component 320 can be a function or module of the smart contract 206 that determines when to trigger the function of the smart contract 206. For example, the receiving component 320 can determine that the action list includes a request / command to generate a digital asset, and therefore the receiving component 320 advances the method 400 to 402.

[0037] At block 404, method 400 includes generating a digital asset and metadata for the digital asset, wherein the metadata includes information about the characteristics of the digital asset and the user's ownership of the digital asset. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or generation component 325 may be configured to or may include components for generating digital assets 122 and metadata 210 for digital assets 122, wherein metadata 210 includes information about the characteristics of the digital asset and the user's ownership of the digital asset 210. In some aspects, metadata 210 is generated by untrusted code in smart contract 206, which includes all information required for a client to render digital asset 122.

[0038] In some aspects, the generation component 325 can also be a function or module of the smart contract 206. The generation component 325 can generate metadata 210, which can be a data structure that includes the following information about the digital asset 112: creation date, user identifier of the creator and / or owner of the digital asset 112 (e.g., wallet address of the user 104, IP / MAC address of the computing device on which the rendering client 202 is installed, name, location, email address, username, password, phone number, etc.), and visual details of the digital asset 122 (e.g., number of petals, size of petals, size of stem, size of leaves, number of leaves, color of leaves, animated motion such as swaying, position, etc.).

[0039] At block 406, method 400 includes storing the metadata on the blockchain. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or storage component 330 may be configured to or may include components for storing metadata 210 on blockchain 208.

[0040] In some aspects, storage component 330 is a function or module of smart contract 206. In one example, storage component 330 can store metadata 210 in block 1 of blockchain 208. Block 1 can be a genesis block indicating the creation of digital asset 122.

[0041] At block 408, method 400 includes receiving a second request from the application to access the digital asset. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or receiving component 320 may be configured to or may include components for receiving a second request from application 102 to access digital asset 122.

[0042] Assume that after generating the digital asset 122, the user 104 closes the application 102 on his / her computing device. Later, the user 104 may request to access the digital asset 122. The interaction that the user 104 may have with the AR effect 114 for accessing the already existing digital asset 122 may be different from the interaction that the user 104 may have for generating a new digital asset. For example, there may be a button for the AR effect 114 that enables the user to render a pre-existing digital asset. When the user 104 selects the button, a second request may be sent from the rendering client 202 to the bridge server 204. The bridge server 204 may route the second request to the smart contract 206. Typically, each decentralized digital asset has its own smart contract with a unique address on the blockchain. The bridge server 204 is configured to point to the unique address and send messages back and forth accordingly. The receiving component 320 of the smart contract 206 receives this second request.

[0043] At block 410, method 400 includes transmitting metadata stored on the blockchain to the application for rendering in response to verifying the identifier associated with the user in the second request. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or sending component 335 may be configured to or may include components for transmitting and storing metadata 210 on blockchain 208 to application 102 for rendering in response to verifying the identifier associated with user 104 in the second request.

[0044] Each request received by the smart contract 206 includes at least one user identifier (e.g., a wallet address). Because each user identifier is unique, the smart contract 206 verifies whether the request to access, generate, modify, transfer, delete, etc. originates from an authorized user. In some aspects, the authorized user may be the creator of the digital asset. In some aspects, the authorized user may be the owner of the digital asset (if ownership has changed since the creation of the digital asset).

[0045] In response to determining that the user identifier in the second request matches the user identifier on the blockchain 208 (e.g., the wallet address in the second request matches the wallet address in the metadata 210 stored in block 1 of the blockchain 208), the smart contract 206 can send the metadata 210 to the rendering client 202. The rendering client 202 then uses the metadata 210 to render the digital asset 122. For example, the metadata 210 can include visual details that enable the rendering client 202 to replicate the visual appearance of the digital asset 122.

[0046] refer to Figure 5In an optional aspect, at block 502, the method 400 may further include receiving a third request to modify the digital asset from the application executing the augmented reality effect. For example, in one aspect, the computing device 300, the processor 305, the memory 310, the digital asset management component 315, and / or the receiving component 320 may be configured to or may include components for receiving a third request to modify the digital asset 122 from the application 102 executing the AR effect 114.

[0047] For example, the third request may include a user identifier of user 104 and a list of actions to be taken in order to modify digital asset 122. Assume that user 104 interacts with AR effect 114 and activates a feature of AR effect 114 that adds an additional flower to digital asset 122. The commands / actions involved in the interaction are included in the list of actions. For example, the modification may result in digital asset 132.

[0048] In this optional aspect, at block 504, method 400 may further include generating additional metadata in response to verifying the identifier, the identifier being associated with the user, wherein the additional metadata includes information about the modified characteristics of the digital asset. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or generation component 325 may be configured to or may include components for generating metadata 212 in response to verifying the identifier associated with user 104, wherein metadata 212 includes information about the modified characteristics of digital asset 132.

[0049] The generation component 325 can verify that the user identifier in the third request matches the user identifier of the owner / creator according to the latest block in the blockchain 208. In response to verifying the user identifier, the generation component 325 can generate metadata 212. For example, the metadata 212 can indicate that the number of petals has changed from 10 to 16.

[0050] In this optional aspect, at block 506, method 400 may further include storing the additional metadata on the blockchain. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or storage component 330 may be configured to or may include components for storing metadata 212 on blockchain 208 (e.g., in block 2).

[0051] In alternative or additional aspects, the metadata is stored on a first block of the blockchain and the additional metadata is stored on a second block of the blockchain.

[0052] refer to Figure 6In an optional aspect, at block 602, method 400 may further include receiving a third request to transfer ownership of the digital asset to a different user, wherein the third request includes a different identifier of the different user. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or receiving component 320 may be configured to or may include components for receiving a third request to transfer ownership of digital asset 122 to a different user, wherein the third request includes a different identifier of the different user.

[0053] For example, the different identifiers may be wallet addresses of wallets belonging to different users.

[0054] In this optional aspect, at block 604, method 400 may further include generating additional metadata in response to the identifier associated with the user in the verification third request, wherein the additional metadata includes information about the transfer of ownership from the user to a different user. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or ownership metadata component 350 may be configured to or may include instructions for generating additional metadata in response to the identifier associated with user 104 in the verification third request, wherein the additional metadata includes information about the transfer of ownership from the user to a different user.

[0055] For example, ownership metadata component 350 can be a function or module of smart contract 206. Ownership metadata component 350 can determine that the user identifier of user 104 in the third request matches the user identifier in metadata 210 stored in block 1 of blockchain 208. In response to verifying the user identifier (i.e., confirming that user 104 is authorized to transfer ownership because user 104 is the current owner), ownership metadata component 350 can generate additional metadata. The additional metadata can indicate that the previous owner was user 104, the new owner is a different user, the transfer date / time, and any other transaction details, such as the costs / fees involved.

[0056] In this optional aspect, at block 606, method 400 may further include storing the additional metadata on the blockchain. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or storage component 330 may be configured to or may include components for storing the additional metadata on blockchain 208 (e.g., block 2).

[0057] In this optional aspect, at block 608, the method 400 may further include receiving a fourth request to modify the digital asset from the application performing the augmented reality effect, wherein the fourth request is from a different user. For example, in one aspect, the computing device 300, the processor 305, the memory 310, the digital asset management component 315, and / or the receiving component 320 may be configured to or may include components for receiving a fourth request to modify the digital asset 122 from the application 102 performing the AR effect 114, wherein the fourth request is from a different user.

[0058] For example, a different user may interact with a digital asset on his / her application, and the interaction is sent as an action list to the bridge server 204. In this case, the fourth request includes a user identifier of the different user and the action list.

[0059] In this optional aspect, at block 610, method 400 may further include generating secondary metadata in response to verifying different identifiers associated with different users, wherein the secondary metadata includes information about the modified characteristics of the digital asset. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or modified metadata component 355 may be configured to or may include components for generating secondary metadata in response to verifying different identifiers associated with different users, wherein the secondary metadata includes information about the modified characteristics of the digital asset.

[0060] For example, the modify metadata component 355 can verify that the user identifier in the fourth request matches the user identifier of the new owner according to the blockchain 208 (ie, block 2). In response to verifying the user identifier, the smart contract 206 allows the modification and generates the secondary metadata.

[0061] In this optional aspect, at block 612, method 400 may further include storing the secondary metadata on the blockchain. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or storage component 330 may be configured to or may include components for storing the secondary metadata on blockchain 208 (e.g., in block N).

[0062] Although the foregoing disclosure discusses illustrative aspects and / or embodiments, it should be noted that various changes and modifications may be made herein without departing from the scope of the aspects and / or embodiments as defined by the appended claims. In addition, although elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Furthermore, unless otherwise stated, all or part of any aspect and / or embodiment may be used together with all or part of any other aspect and / or embodiment.

Claims

1. A method for decentralized programmatic digital asset creation, comprising: receiving a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application; generating the digital asset and metadata of the digital asset, wherein the metadata includes information about characteristics of the digital asset and ownership of the digital asset by the user; storing the metadata on a blockchain; receiving a second request from the application to access the digital asset; as well as In response to verifying the identifier associated with the user in the second request, transmitting the metadata stored on the blockchain to the application for rendering.

2. The method of claim 1 , wherein a smart contract is configured to generate the digital asset and the metadata, and store the metadata on the blockchain. 3 . The method of claim 1 , wherein the first request is generated by a user interaction with the augmented reality effect on the computing device.

4. The method according to claim 1, further comprising: receiving, from the application executing the augmented reality effect, a third request to modify the digital asset; generating additional metadata in response to verifying the identifier associated with the user, wherein the additional metadata includes information about the modified characteristics of the digital asset; as well as The additional metadata is stored on the blockchain.

5. The method of claim 1 , wherein the metadata is stored on a first block of the blockchain and the additional metadata is stored on a second block of the blockchain.

6. The method according to claim 1, further comprising: receiving a third request to transfer ownership of the digital asset to a different user, wherein the third request includes a different identifier of the different user; generating additional metadata in response to verifying the identifier associated with the user in the third request, wherein the additional metadata includes information regarding the transfer of ownership from the user to the different user; as well as The additional metadata is stored on the blockchain.

7. The method according to claim 6, further comprising: receiving a fourth request from the application executing the augmented reality effect to modify the digital asset, wherein the fourth request is from the different user; generating secondary metadata in response to verifying the different identifier associated with the different user, wherein the secondary metadata includes information about the modified characteristics of the digital asset; as well as The secondary metadata is stored on the blockchain.

8. An apparatus for decentralized programmatic digital asset creation, comprising: Memory; as well as a processor communicatively coupled to the memory and configured to: receiving a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application; generating the digital asset and metadata of the digital asset, wherein the metadata includes information about characteristics of the digital asset and ownership of the digital asset by the user; storing the metadata on a blockchain; receiving a second request from the application to access the digital asset; as well as In response to verifying the identifier associated with the user in the second request, transmitting the metadata stored on the blockchain to the application for rendering.

9. The apparatus of claim 8, wherein a smart contract is configured to generate the digital asset and the metadata, and store the metadata on the blockchain.

10. The apparatus of claim 8, wherein the first request is generated by a user interaction with the augmented reality effect on the computing device.

11. The apparatus of claim 8, wherein the processor is further configured to: receiving, from the application executing the augmented reality effect, a third request to modify the digital asset; In response to verifying the identifier associated with the user, generating additional metadata, wherein the additional metadata includes information about the modified characteristics of the digital asset; and The additional metadata is stored on the blockchain.

12. The apparatus of claim 8, wherein the metadata is stored on a first block of the blockchain and the additional metadata is stored on a second block of the blockchain.

13. The apparatus of claim 8, wherein the processor is further configured to: receiving a third request to transfer ownership of the digital asset to a different user, wherein the third request includes a different identifier of the different user; generating additional metadata in response to verifying the identifier associated with the user in the third request, wherein the additional metadata includes information regarding the transfer of ownership from the user to the different user; and The additional metadata is stored on the blockchain.

14. The apparatus of claim 13, wherein the processor is further configured to: receiving a fourth request from the application executing the augmented reality effect to modify the digital asset, wherein the fourth request is from the different user; generating secondary metadata in response to verifying the different identifier associated with the different user, wherein the secondary metadata includes information about the modified characteristics of the digital asset; as well as The secondary metadata is stored on the blockchain.

15. A computer-readable medium having stored thereon instructions for decentralized programmatic digital asset creation, wherein the instructions are executable by a processor to: receiving a first request to create a digital asset from an application executing an augmented reality effect on a computing device, wherein the first request includes an identifier associated with a user of the application; generating the digital asset and metadata of the digital asset, wherein the metadata includes information about characteristics of the digital asset and ownership of the digital asset by the user; storing the metadata on a blockchain; receiving a second request from the application to access the digital asset; as well as In response to verifying the identifier associated with the user of the second request, transmitting the metadata stored on the blockchain to the application for rendering.

Images