Encrypted digital asset architecture with selective locking dynamic evolution
By enabling dynamic evolution and selective locking of batch-minted cryptographic tokens, users gain control over their NFTs, transforming them into unique tokens with derived properties, enhancing engagement and desirability.
Patent Information
- Application Number
- CN202380034294.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-22
- Filing Date
- 2023-04-21
- Publication Date
- 2024-12-03
AI Technical Summary
Current NFTs are static in nature, offering limited interactivity and engagement beyond displaying graphic files, lacking opportunities for user participation and control over dynamic evolution.
Implementing batch-minted cryptographic tokens (BMCTs) with evolving attributes, allowing users to selectively lock their assets at various stages, converting them into unique cryptographic tokens (UCTs) with derived properties based on their evolved state, and enabling interactive experiences through external triggers and exchanges.
Enhances user engagement and ownership experience by providing dynamic, gamified interactions, increasing asset desirability and brand loyalty through customizable and evolving digital collectibles.
Smart Images

Figure CN119072690A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 334,082, filed on April 22, 2022, which is incorporated by reference in its entirety. Technical Field
[0003] The present disclosure generally relates to an architecture and method that allows users to interact with and selectively freeze dynamically evolving crypto assets / digital collectibles. Background Art
[0004] A non-fungible token (NFT) is a non-interchangeable (i.e., non-fungible) record that is stored digitally and can be sold or traded between different market participants. In many cases, an NFT can be used as a digital certificate of authenticity or proof of ownership in a corresponding digital or physical item. Records including NFTs are typically stored in / on an immutable digital ledger (such as a blockchain-type ledger), which can be distributed among many different nodes or ledger maintenance participants. Such a blockchain ledger will use certain cryptographic means to encode at least a portion of the record content, while also referencing previous blocks (in the blockchain) to provide continuity.
[0005] NFTs typically include resident data (metadata) stored directly on the blockchain that defines core aspects of the digital asset. The metadata itself may be limited due to the cost complexity associated with pushing large amounts of data through the blockchain transaction verification process, but may typically include one or more pointers or references to additional separate on-chain stored assets or off-chain data / digital files (such as photos, graphics, videos, and / or audio) that are cost-prohibitive to store on-chain. When the NFT is displayed, such as on a user's social media account or in a user's digital wallet, the associated software program can view the metadata and then digitally retrieve the associated photos from the referenced on-chain or off-chain file repository for display.
[0006] Two blockchain / smart contract standards have begun to dominate the current NFT space. Both rely on the Ethereum network and are elaborated based on community-adopted improvement proposals: ERC721 (also known as EIP-721); and ERC1155 (also known as EIP-1155). In a very general sense, ERC 721 provides a standard for creating unique (i.e., 1 / 1) digital assets and is most commonly associated with traditional NFTs. Each ERC721 token includes a token-specific smart contract and must be minted and transferred independently of any other ERC721 token. In contrast, ERC1155 provides a standard for batch creation of multiple substantially identical tokens through a single recorded smart contract. These batch-created tokens are serialized (e.g., token 1 / 100) and can be transferred between wallets individually or in batches.
[0007] Examples of assets that can be represented via ERC721 tokens include unique assets such as land, artwork, unique digital collectibles, etc. Examples of assets that can be represented via ERC1155 tokens include, for example, limited-edition trading cards, art prints, coupons, and general admission event tickets. At creation, each tokenized asset under an ERC1155 contract is essentially interchangeable with any other co-minted asset under that contract. For example, an ERC1155 contract can be used to batch mint 100 identical-looking trading cards that are completely interchangeable with each other (except for having unique token identification (ID) numbers). From the owner's point of view, multiple such cards can be traded together via a single market listing, with the value of any individual card determined by the market dynamics of the batch rather than any characteristics of the individual card / token.
[0008] In some embodiments, the ERC1155 contract may also provide a switching mechanism to transform a token from an initial fungible / semi-fungible state to a subsequent non-fungible state. This may be used in conjunction with general admission event tickets or coupons, where after use, the token loses its interchangeability with other tokens from the initial batch and takes on a more unique / non-fungible existence.
[0009] For the purposes of this disclosure, ERC721 tokens may be more generally referred to as unique cryptographic tokens ("UCTs"), while ERC1155 tokens may be referred to as batch-minted cryptographic tokens ("BMCTs"). Each UCT may be independently registered to a blockchain distributed ledger and may be the product of a separate smart contract, or multiple UCTs may be minted according to the same smart contract. Multiple BMCTs may all be derived together from a single smart contract registered to a blockchain distributed ledger. In summary, for the purposes of this disclosure, both UCTs and BMCTs are considered types of NFTs.
[0010] In the current market, most digital collectibles supported by UCT or BMCT are essentially static in nature and derive value from both the desirability of the collection to which the collectible belongs and from the scarcity of one or more asset-specific characteristics expressed in the token and / or referenced graphic files. In the current NFT environment, there is little opportunity to engage with digital collectibles other than loading a graphic file as a profile picture on social media or importing a collectible / asset into a third-party software application where it can be "used" by a character or used to affect game functionality. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 It is a schematic timeline progression of lock-in related to the evolution of crypto digital assets.
[0012] Figure 2 It is a schematic evolutionary progression of a cryptographic digital asset that evolves via one or more external triggering events.
[0013] Figure 3 It is a schematic evolutionary progression of a cryptographic digital asset that combines one or more external factors to promote the results of evolutionary lock.
[0014] Figure 4 is a schematic diagram of a base product being merged with a skin vial sub-asset of indeterminate outcome to produce any of six different outcomes.
[0015] Figure 5 is an illustrative progression of the evolution of a Skin Bottle asset with uncertain outcome that produces different outcomes after use / merging with a base asset, where the outcome depends at least in part on the evolution status of the evolving sub-assets.
[0016] Figure 6 is a schematic flow chart of a second, indeterminate Skin Bottle asset being merged with a previously skinned Base Asset to produce a new Skinned Base Asset and a newly minted Skin Bottle.
[0017] Fig. 7A is a schematic graphical display image providing a perspective view of a digital skin bottle asset that is integrated into a base level version of a digital collectible.
[0018] Figure 7B is shown inserted into Fig. 7A Digital collections of Fig. 7A A schematic graphic display image of an enlarged view of the bottle.
[0019] Figure 7C is a schematic graphical display image providing a side view of a digital skin that sweeps across a base level version of a digital collectible.
[0020] Fig.7D yes Figure 7CSchematic graphic display of the digital collection where the digital skin is fully applied. DETAILED DESCRIPTION
[0021] In summary, the concepts described herein provide for an enhanced level of interactivity and user engagement with digital collectibles and NFTs. Under this architecture / approach, limited-edition dynamic digital collectibles may be minted in batches, after which owners / holders of these collectibles may be given the option and / or ability to selectively lock copies of their collectibles at any stage in their dynamic evolution. In some embodiments, depending on when an asset is locked, different downstream opportunities / benefits / abilities may ensue.
[0022] By allowing users direct participation and control over evolving digital assets, the present technology may provide a more actively engaged ownership community that may create a more enjoyable user experience and increase desirability of asset ownership and brand engagement.
[0023] The method begins with batch creation and / or batch minting of multiple cryptographic tokens (BMCTs) via a single / common digital contract (i.e., a "smart contract," such as, for example, an ERC1155 contract) registered to a blockchain-type distributed ledger. At the time of minting, each cryptographic token / associated digital asset may be substantially identical to all other digital assets except for a token-specific ID number that varies. The smart contract and / or BMCT may include metadata that references an on-chain or off-chain file repository containing one or more data files and / or graphic files stored thereon. The file repository may be an Internet-connected server, a cloud-based computing platform, or a peer-to-peer / distributed file system, such as the InterPlanetary File System (IPFS) developed by Protocol Labs. The identified graphic files stored on the file repository may provide a graphical representation of the digital asset 32 (e.g., Figure 1 As shown), the graphical representation may be common to each BMCT minted via a registered smart contract. Once created, BMCT may be distributed to multiple different token holders, such as by requesting or instructing a transfer via an established blockchain protocol.
[0024] like Figure 1 to Figure 2 , a digital asset 32 may include at least one characteristic / attribute that is configured to dynamically evolve through a plurality of evolution stages over a period of time and / or in response to one or more events. These dynamically evolving characteristics may take various forms and / or may be implemented in a variety of different ways. For example, in some configurations, a characteristic may be a visual element 38 of a digital asset, while in other configurations, an evolving characteristic may include non-visual parameters 40, such as performance attributes that define how a digital object performs or affects other objects if / when the asset is imported into a video game type software application.
[0025] In embodiments where the evolving attribute is a visual element 38 of a digital asset, the visual element may include a complete graphical representation of the digital asset (an "image"), a portion of an image, a layer of an image, or even one or more elements that are added to the image only after a conditional event occurs. Examples of graphical attributes that may evolve include, for example, color, graphic stickers, decoration, attribute size, visual continuity, background, text identifier, state identifier, etc.
[0026] If the dynamically evolving characteristic is an element of a graphical representation of an asset and / or a graphic file, changes to the integrated visual element may require modifying a pointer to the graphic file (i.e., so that the token points to a different file or file location), or the original source file may simply be replaced on the file repository. In some embodiments, to more easily identify the evolving state of the dynamic characteristic, a digital record of the evolution and / or nature of the evolving characteristic may be stored in conjunction with the graphic file. For example, the digital record may be provided in an accompanying data file, in metadata associated with the graphic file, or even in a digital code provided within the image itself (e.g., a QR code represented on the graphic).
[0027] In embodiments where the evolution attribute is a non-visual parameter 40, the attribute may include a discrete alphanumeric identifier (e.g., level 1 (L1), level 2 (L2), level 3 (L3), level 4 (L4), etc.) that may be used as a qualitative or quantitative identifier of the magnitude of a characteristic such as level, experience, strength, or evolution stage, event ID, etc. Such dynamically evolving characteristics or attributes may be stored in a data file on a file repository, possibly in conjunction with a graphics file describing the digital asset. For example, such a data file may define one or more performance attributes that define how a digital object performs or affects other objects if / when the asset is imported into a video game type software application. Examples of such parameters may include, for example, strength, agility, health, level, or power boosts. Dynamic evolution of an asset may be used to randomly change one or more of these parameters, or may be used to simply increase / increase one or more of these parameters.
[0028] While in many embodiments, dynamic attributes may be an integrated aspect of the BMCT (i.e., inseparable from or identified directly within the data or graph associated with the BMCT), in other embodiments, the dynamic attribute may be its own discrete sub-asset that is referenced solely by the master digital asset / BMCT. More specifically, in some configurations, an evolving attribute may have its own tokenized existence identified within or referenced by the BMCT. In such a nested architecture, any evolving changes in the evolving attribute may occur only within the code or control of the second-layer attribute token. Further disclosure of such nested attribute concepts may be found in U.S. Patent Application No. 17 / 701,237, filed on March 22, 2022, issued as U.S. Patent No. 11,475,449, which is incorporated herein by reference in its entirety for all purposes.
[0029] Figure 1 Schematically depicted is an example of a digital asset 32 represented as a cubic container having an outer surface 42 configured to dynamically evolve from a substantially intact initial state 44A through a progression of subsequent evolutionary states 44B, 44C, 44D that gradually decompose and / or break apart. In this embodiment, the evolving visual attribute 38 is the visual continuity / integrity of the outer container structure. In addition, this example also provides non-visual parameters 40 (i.e., evolution levels) that accompany the asset 32 and evolve simultaneously with the gradual degradation of the visual outer surface 42.
[0030] Figure 2 A second example of a digital asset 32 represented as a shoe image (visual attributes 38) is schematically depicted, the shoe image being configured to dynamically evolve through a progression of evolution stages 50A, 50B, 50C. As further illustrated, the digital asset includes a plurality of non-visual parameters 40 that are also configured to evolve from one stage to another. As shown, these non-visual parameters 40 may include attributes that qualitatively define how the corresponding asset performs when imported into a digital video game-style environment and worn by an avatar of a user.
[0031] Attribute Evolution
[0032] Once a BMCT is defined and cast, one or more dynamic attributes may be evolved over time in a discrete or continuous manner. In a discrete or piecewise evolution, the attribute will progress through a plurality of perceptibly distinguishable evolutionary stages, where transitions are identifiable, and each stage is maintained for some perceptible period of time (e.g., days / weeks). In a continuous evolution, the attribute will progress through a large number of sufficiently small changes, where any two temporally adjacent states will be barely independently distinguishable (i.e., the total transition more closely resembles a gradual deformation). In practice, due to the limitations of modern computing, the difference between discrete and continuous may be only a matter of degree, where a discrete evolution has less than 1000, or less than 100, or less than 50, or less than 10 discrete evolutionary stages, while a continuous evolution may have greater than 1000, or greater than 5000, or greater than 10,000, or even greater than 100,000 discrete stages. Figure 1 and Figure 2 Examples of discrete progression are shown in . Other examples may involve incrementing the experience level of an asset by integer values from 0 to 50, or cycling the color of a visual attribute through the seven primary colors of the rainbow. Conversely, examples of continuous progression may involve incrementing the experience level every second or minute of the token's existence (since minted), or cycling the color of a visual attribute through the colors of the rainbow in increments of 5000 or more (as opposed to just 7 in the discrete examples).
[0033] Typically, the evolution of a dynamic property may occur in response to some predefined event, occurrence, condition, or action. In some configurations, the condition may simply be the passage of time (e.g., where a transition occurs in response to a clock incrementing, a new block being added to the blockchain, etc.). In other configurations, the condition may be a random number generator that outputs a number within a predefined range or a specific function that outputs some predefined result or sequence. In still other configurations, the evolution may be determined by an asset administrator (e.g., an administrator replacing a file on a file server).
[0034] In some configurations, a dynamic attribute can be directly responsive to one or more external triggering events (e.g., Figure 3Such trigger events may be outside the direct control and / or prediction of the smart contract and may rely on appropriate import filters, APIs, or blockchain oracles 64, or other similar mechanisms to detect and utilize. In some embodiments, these trigger events may have a probabilistic chance of occurring (e.g., the results of a sporting event or a semi-final / playoff performance, an athlete's game statistics or professional highlights, the results of an election, etc.) and may occur in the real / physical world or in a digital / virtual environment or gaming environment. In some embodiments, a suitable blockchain oracles 64, such as may be provided via the CHAINLINK blockchain protocol, may be used as a distributed knowledge source from which these trigger events may be derived.
[0035] The external triggering event that causes the evolution of the attribute can further involve the results of one or more activities that require (or encourage / motivate) the participation of the group / community. For example, in one instance, the dynamic attribute can evolve in response to the completion of one or more predefined group challenges by the community (e.g., the ownership group of the BMCT asset). This evolution model can help cultivate a greater sense of participation and interconnectedness within the ownership base, which can enhance ownership and brand loyalty. Examples of group challenges can include achieving a predefined total number of social media "likes" for respective assets, achieving a predefined number of uses / imports of assets in a social media digital platform or within one or more video game type software applications, achieving various collective milestones (e.g., asset valuation or ranking within a predefined pool of assets), and / or solving one or more particularly challenging puzzles, riddles, codes, etc.
[0036] Selective Evolution Lock
[0037] As described above, after creating these BMCTs with evolving properties, token holders may be provided with a mechanism to selectively freeze the asset in its current state, thereby preventing further evolution of the dynamic properties / features (such as in Figure 1 ). This action of freezing or locking the evolution may then enable the holder to maintain the asset (or equivalent) in that locked state indefinitely (e.g., corresponding to Figure 1 In some embodiments, the holder may be provided with a locked / copied locked token 72B, 72C, 72D based at least in part on the evolved state 44B, 44C, 44D of the BMCT at the time the locking request was made, or in some embodiments, one or more derivative assets / tokens 74A, 74B, 74C, 74D based at least in part on the evolved state of the BMCT at the time the locking request was made.
[0038] In one configuration, such a lock event may occur and / or may be provided within the standard for creating tokens. For example, if a BMCT holder (of multiple BMCT holders under a common contract) wants to freeze the state of their token, they can toggle a redemption feature that changes the token from having group-level properties (i.e., shared with multiple other batch-minted tokens) to token-specific properties (i.e., discrete properties, pointers to graph files, etc., that are uniquely identified on a token-by-token basis).
[0039] In another embodiment, to selectively lock or freeze the state of an evolving BMCT, a user may selectively exchange a BMCT for one or more unique cryptographic tokens (UCTs) and / or BMCTs corresponding to the exchanged BMCT (i.e., where the UCTs and / or BMCTs have one or more attributes or properties derived at least in part from the state of the evolving BMCT at the time of the exchange). To facilitate the exchange, a server or computing node may receive a request to facilitate the lock / exchange from the owner or holder of the BMCT. At this point, the server may examine the current parameter space of the evolving BMCT to identify which attributes have evolved since creation and to what extent they have evolved. Such an examination may involve contacting a file repository to examine the current state of the graphic file, any metadata associated with the graphic file, and / or other data files that may be associated with or referenced by the evolving BMCT.
[0040] Once the parameter space of the evolving BMCT is understood, the server may generate a UCT (such as an ERC721 token) and / or a BMCT (e.g., an ERC1155 token) that includes at least one parameter or property derived in part from the state of the evolving property in the BMCT at the time of the request. In some embodiments, the UCT may be an exact replica of the BMCT at the time the lock request was made. In other embodiments, the UCT may be visually distinct from a graphical representation of the evolving BMCT, but may have one or more aspects that are uniquely derived from the state of the dynamically evolving property. For example, for Figure 1In the illustrated embodiment, although the evolved BMCT may be represented as a cube object, after the exchange, a corresponding UCT digital shoe or BMCT digital skin bottle may be created by the server after the exchange. The digital skin bottle may be a property modification sub-asset that may be used to modify predefined properties of a higher-level asset such as the silhouette of a shoe or an unspecified version (e.g., color scheme, silhouette, decoration, laces, background, dynamic motion / animation, degree of cartoon rendering, etc.). The digital skin bottle may have varying states or design themes that are derived or created as a result of the state of the cube at the time of the request. Likewise, in some embodiments, instead of creating a derived property modification sub-asset UCT / BMCT (such as a bottle), the server may create a UCT of a higher-level / master asset (such as an entire uniquely designed shoe).
[0041] In some embodiments, multiple UCTs may be created after a request to exchange / lock. More specifically, the server need not adhere to a 1:1 create / exchange model, but may generate multiple UCTs in response to a request to lock a single evolved BMCT. In one embodiment, the server may create a first UCT (e.g., derivative assets 74A to 74D) derived from the evolved state of the BMCT at the time of the request, and may also create a second UCT (e.g., duplicate assets 72B to 72D) that is a copy of the BMCT at the time of the request. The first UCT may be a primary asset (e.g., a shoe, an article of clothing, a gaming tool, an accessory, or a weapon, etc.) or a sub-asset (a color, a feature, an overlay, a special ability, etc.), but at least one property / attribute may be derived from the evolved state of the BMCT at the time of the request.
[0042] In some embodiments, the server may also consider various auxiliary data when generating the UCT. For example, the server may rely on data from external sources, such as date / time, an oracle (or other repository of real-world data / events / knowledge), geospatial data (e.g., identifying the location where the request was made), or the presence of other registered assets (e.g., reinforced assets) within the owner's wallet or account. An example of using such auxiliary data may involve: if a lock request is made while physically present at a tournament basketball or football game, the server generates a sports-themed or commemorative UCT. Conversely, if a lock request is made elsewhere (although both requests are made simultaneously and the BMCT asset is in an evolving state), the server may generate a UCT with different properties.
[0043] In another example, such as Figure 3As shown, the BMCT digital asset 80 can be provided to each season ticket holder within a particular sports league at the beginning of the season or after the season. If the request occurs when participating in a game (as identified by the geographic location input 82), the server can only identify the request to lock the evolving state of the 70 token. Then one or more elements of the generated UCT 84 (i.e., generated by the server in response to the request for the lock 70) can correspond to the evolving state of the BMCT (i.e., where the dynamic evolution attribute can be a counter for identifying which game in the season or playoffs is currently the "live" game). In addition, other properties / attributes of the generated UCT can correspond to the important events of the game (e.g., scoring champions, player milestones, division / club / league championships, etc.), such as can be derived from an external repository of sports knowledge, a statistical database, or a blockchain oracle 64. This "game" of choosing when to exchange BMCTs can involve an element of chance as to whether to stick with a better or more noteworthy game or whether the current game presents a compelling reason to make a request / exchange.
[0044] After receiving the lock request and generating one or more corresponding UCTs, the server may instruct, request or otherwise cause the generated UCT 84 to be transferred to the wallet or account of the initial requester. In this way, from the user's point of view, the user can make a lock request and then receive one or more corresponding digital collectibles in return. In some embodiments, the original BMCT requested to be locked can be transformed into an inactive state (e.g., switched to a blank graphic file or designated as "destroyed" or "redeemed"), or can be transferred to an account or wallet associated with the server or content creator (i.e., where the wallet can only be used to collect redeemed BMCTs). In this way, users can effectively exchange their BMCTs for one or more UCTs based on BMCTs. In yet other instances, such as the above-mentioned sports instance, if the organizer's intention is to use BMCTs to promote gifts for certain categories of ticket holders (e.g., season ticket holders, ticket holders purchased directly from teams / leagues rather than from third-party markets, etc.), the original BMCTs may not be destroyed at all. In this case, lock requests can be made multiple times without affecting the underlying BMCT.
[0045] Downstream opportunities
[0046] While UCT itself may have some extrinsic value based on its collectibility, visual appearance, etc., in some embodiments, UCT may also provide some intrinsic value to its owner / holder by unlocking new opportunities or increasing the likelihood that certain opportunities are available. For example, in some embodiments, UCT may be exchanged for one or more physical products, including but not limited to: a physical item with a shape, appearance, or similarity that matches or is derived from a graphic file / image associated with the UCT; or a physical item of a more common character (e.g., limited production (approximately 100 to 5000 units)). In some embodiments, UCT may affect the likelihood of the owner receiving secondary benefits, such as a changing physical retail product supply, access to select events or pre-sale ticketing opportunities, digital access to unique experiences within a virtual or mixed reality environment, or the ability to receive or purchase changing third-level digital assets. For example, holding a certain UCT or a UCT with specific characteristics may increase your likelihood of winning a virtual draw for a limited-edition product supply, such as by increasing the number of entries you have in the draw, increasing the probability of selection, and / or improving your position within the virtual line. Further disclosure of such lottery-based product sales and virtual lines is provided in U.S. Patent No. 11,295,318, issued on April 5, 2022, which is incorporated by reference in its entirety.
[0047] In some embodiments, all UCTs generated from a common BMCT contract may belong to a common UCT set or have a common UCT genus. Therefore, there is an opportunity to "airdrop" or gift subsequent UCTs to any UCT holder within that set.
[0048] In one embodiment, the method may further include, when a request to freeze, lock or destroy (ie, destroy) the first BMCT is made, Figure 1 ) to the holder of the first BMCT. In this way, exchanging / locking the first BMCT may not terminate the game, but may continue user participation (possibly with diminishing returns for each subsequent exchange / lock). The digital image associated with the subsequent BMCT 90 may be the same as the original / pre-evolved version of the first BMCT. Alternatively, the second BMCT may have one or more qualities (e.g., color, character, style, etc.) that help visually distinguish it from the first BMCT.
[0049] Contour and skin
[0050] In one configuration, exchanging or locking the initially distributed BMCT may result in the token holder receiving a new BMCT or UCT that includes a digital image similar to an outline or other base-level version of the article, such as Figure 4 100 in . In some embodiments, the article may be an article of footwear, an article of clothing, a vehicle, a tool, or other similar article. Additionally or alternatively, a token holder may receive one or more UCTs representing sub-assets, skins, or skin bottles 102 that may be applied to the profile. Such sub-assets may include, for example, unique colors, textures, patterns, digital functionality (e.g., when imported into a video game), decorations, backgrounds, animations, features, visual overlays, etc. In some embodiments, a skin bottle may represent a combination of multiple potential skins or attributes. For example, Figure 4 As shown, the combination of base stage product 100 and skin bottle 102 may result in any of the six depicted results 104A, 104B, 104C, 104D, 104E, or 104F.
[0051] Once acquired (either through the original exchange or through subsequent independent purchases), a token holder may submit a request to combine one or more of the sub-assets with the profile / base version to create a unique or upgraded version of the base article. In some embodiments, combining a skin bottle (or similar item that does not externally define the end result) with a base-level version of an article may result in a final skinned version of the article that ultimately reveals itself to the user only after combination.
[0052] like Figure 5 In some configurations, a sub-asset (e.g., skin bottle 102) may be adapted to be used in conjunction with Figure 1 to Figure 2 In this embodiment, the evolution of the skin bottle 102 can occur primarily in a non-visual manner, but secondary visual attributes can also be modified to convey that evolution is occurring. Figure 5 As shown, as the skin bottle evolves through multiple evolutionary states 110A, 110B, 110C, and 110D, the result of merging with the base article 100 can result in different corresponding visual representations 112A, 112B, 112C, and 112D (i.e., different characteristics or visual appearances extracted or derived at least in part from the evolutionary states when the merging / use occurs).
[0053] This combination of base assets and skins can be performed in a predefined digital / computing environment that can link and combine these assets without any modification to the underlying tokens. In this configuration, the linking of assets can rely on, for example, a database registration or cross-reference mechanism. In another embodiment, the linking / combination can involve annotating the metadata of the main asset to reference the UCT representing the sub-asset, such as described in U.S. Patent Application No. 17 / 701,237.
[0054] In some configurations, multiple UCT sub-assets may be applied to a single base silhouette to create unique combinations or crosses between skin types. In this configuration, an associated server, digital engine, or virtual environment may perform a generative combination of sub-assets such that each sub-asset is represented on the silhouette in a complementary manner. Such combinations may be created in this manner to follow one or more predefined style guides or rules that may govern potential mergers. Alternatively, the combination may rely on a machine learning model to create a design from the provided skin that follows a pattern extracted from a predefined product portfolio. For example, in the example of a shoe, a machine learning model may be trained on historical product releases / designs from a particular manufacturer to understand how to best combine skins while adhering to the design language established by the manufacturer for that silhouette.
[0055] like Figure 6 As shown, in some embodiments, instead of creating a generation merge of skins, the second or subsequently applied skin vial 120 can be operable to re-skin the base article 100 previously skinned by the first skin vial 122. In some configurations, this re-skinning can result in a third skin vial 124 being cast and returned to the user as if it were the initially applied skin removed from the article. This third skin vial 124 can be identical or substantially the same as the first skin vial 122, and if the skin vial is embodied as a BMCT, the third skin vial 124 can even be cast by the same contract used to create the first skin vial 122.
[0056] FIG. 7A to FIG. 7D Schematically depicted is an embodiment of a graphical merge of a master asset (e.g., a base version of a shoe 140) and a sub-asset (e.g., a digital skin bottle 142). As discussed above, during the merge, the token embodying the bottle 142 may be destroyed, transferred to a destruction wallet, or nested into the code of the master asset (e.g., via a nested reference to the sub-asset token). Regardless of what occurs at the token level, in one configuration, the graphical representation of the bottle may be merged into the graphical representation of the higher-level asset (i.e., the shoe). As further illustrated, the skin 144 resulting from the bottle may also be applied to the shoe (potentially by swiping across the shoe, such as Figure 7C). This merge may be displayed to the user via a server operable to combine the assets, and in some embodiments, the server may further alter the graphics file of the master asset to include the sub-asset. In some embodiments, to facilitate easier de-skinning, the sub-asset may be applied in a masking layer on top of the existing shoe graphics (which may be maintained in an unchanged form in the base layer of the image). In embodiments where the sub-asset is destroyed or sent to a destruction wallet, the graphical representation of the skin and / or bottle may be saved by the server to a file repository, and the merged combination of the graphics may be integrated (or instructed to be written) into the metadata of the master asset, may overwrite the existing graphics file, or may be maintained privately by the server as a merged asset.
[0057] As described above, in some embodiments, a user may submit a request to have their upgraded / skinned profile available for retail in physical form. Similarly, upgraded / skinned articles may be incorporated into digital software applications / video games, such as generally described in U.S. Pat. No. 11,308,184, the entire contents of which are incorporated by reference in their entirety.
[0058] It should be understood that the above technology can be implemented in various forms. Although NFT technology is always referenced, the technology can be implemented through one or more public blockchains, private blockchains, and / or can be combined with one or more side chains, smart contracts, databases, etc.
[0059] In addition, it should be understood that this concept of locking evolution assets and / or creating derivative assets from evolution assets utilizes many possible forms. In one particular embodiment, the evolution ERC1155 collection can be locked / destroyed / exchanged for an ERC721 base product and / or one or more ERC1155 skin bottles, which are operable to modify existing ERC721 base products. The ERC1155 skin bottle can be configured to evolve dynamically, so that the application or merging of the skin bottle with the base product produces different results depending on the evolution state of the bottle. In addition, the bottle can have a set of potential skins to choose from (for example, applying the bottle to the base product can force a probabilistic selection of, for example, one of eight possible skins to apply). If the bottle is to evolve, it can evolve so that each of the potential skins or skin selections can also evolve in full, although they can evolve at different rates or to different degrees. Then, skinning the base product with the bottle can cause the bottle to be destroyed or transferred to a destruction wallet maintained by the content creator for this purpose. As described above, if an attempt is made to apply a subsequent bottle to the now skinned base article, the server can create a generated merged or descendant digital asset based on the combination of characteristics (such as described in U.S. Patent No. 10,505,726, which is incorporated by reference in its entirety), or the first bottle / skin can be extracted (the skin removed and the bottle recast) before the subsequent bottle is applied.
[0060] In other configurations, locking an evolved ERC1155 collection may result in the creation of a duplicate ERC721 collection that is based on or is an exact copy of the evolved ERC1155 collection at the time of locking. Additionally, other derivative ERC721 collections may be created / exchanged after locking that derive at least one property from the evolved state of the evolved ERC1155 collection, but are not identical. Finally, locking an ERC1155 collection may result in the holder receiving one or more other evolved ERC1155 collections in return, which may then be selectively locked in much the same manner as the original ERC1155 collection.
[0061] Although the previous disclosure has focused primarily on footwear, similar concepts may also be applied to articles of apparel, auxiliary items that can be used in video games, commemorative trading cards, sports tickets, concert tickets, event tickets, and the like.
[0062] This technology creates a new paradigm and use for NFT collections, whereby holders no longer need to simply own an image created by another person. Instead, this architecture and method of exchanging and locking NFT assets presents a gamified and interactive experience where they can participate in designing and collecting and changing their NFTs themselves. It provides end-user control, brand integration, and a better and more dynamic experience to a previously ordinary and static field.
[0063] In some embodiments, various aspects of the present disclosure can be implemented by computer executable instruction programs such as program modules, which are generally referred to as software applications or application programs, which are executed by any of the controllers described herein or controller variants. In non-limiting examples, software can include routines, programs, objects, components, and data structures that perform specific tasks or implement specific data types. The software can form an interface to allow the computer to react according to an input source. The software can also collaborate with other code segments to initiate various tasks in response to the data received together with the source of the received data. The software can be stored on any of various storage media, such as CD-ROM, disk, bubble memory, and semiconductor memory (e.g., various types of RAM or ROM).
[0064] In addition, the present disclosure can be implemented with various computer systems and computer network configurations, including multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, etc. In addition, the present disclosure can be implemented in a distributed computing environment, where tasks are performed by resident and remote processing devices linked by a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices. Therefore, the present disclosure can be implemented in combination with various hardware, software, or combinations thereof in a computer system or other processing system.
[0065] Any of the methods described herein may include machine-readable instructions for execution by: (a) a processor, (b) a controller, and / or (c) any other suitable processing device. Any algorithm, software, control logic, protocol, or method disclosed herein may be embodied as software stored on a tangible medium (such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard disk drive, a digital versatile disk (DVD), or other memory device). The entire algorithm, control logic, protocol, or method and / or portions thereof may alternatively be executed by a device other than a controller and / or embodied in firmware or dedicated hardware in a usable manner (e.g., implemented by an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic design (FPLD), discrete logic, etc.). In addition, although specific algorithms are described with reference to the flowcharts depicted herein, many other methods for implementing the example machine-readable instructions may be used alternatively.
[0066] Various aspects of the present disclosure have been described in detail with reference to the illustrated embodiments; however, those skilled in the art will recognize that many modifications may be made thereto without departing from the scope of the present disclosure. The present disclosure is not limited to the precise configurations and compositions disclosed herein; and any and all modifications, changes and variations apparent in the foregoing description are within the scope of the present disclosure as defined by the appended claims. Furthermore, the concepts of the present disclosure expressly include any and all combinations and sub-combinations of the foregoing elements and features.
[0067] The following clauses provide various and / or additional embodiments of the present technology. These clauses should be read and interpreted in light of the foregoing disclosure, and are intended to supplement the present disclosure rather than to limit it.
[0068] Clause 1. A method for selectively locking an encrypted digital asset, comprising: instructing or requesting the creation or minting of a plurality of first encrypted tokens via a first common digital contract registered to a distributed ledger, wherein each of the plurality of encrypted tokens defines a digital asset, and the digital asset includes properties that are operable to evolve or change through a plurality of evolutionary stages; instructing the transfer of the plurality of encrypted tokens to a plurality of token holders; receiving a request from a token holder among the plurality of token holders to selectively lock a digital asset defined by one of the plurality of encrypted tokens at one of the plurality of evolutionary stages; instructing or requesting the transfer of a second encrypted token to the token holder, the second encrypted token having at least one property derived at least in part from the evolutionary stage of the digital asset at the time of the request.
[0069] Clause 2. The method of clause 1, wherein the attribute is operable to evolve or change in response to an external triggering event.
[0070] Clause 3. A method according to clause 2, wherein the external triggering event is an event that occurs in the real / physical world or within a digital / virtual environment or a gaming environment.
[0071] Clause 4. The method according to Clause 2 also includes receiving an indication via a blockchain oracle that the external triggering event has occurred; and changing the attribute in response to the indication that the external triggering event has occurred.
[0072] Clause 5. A method according to any one of clauses 1 to 4, wherein the attribute is an element of a graphical representation of the digital asset or a discrete alphanumeric identifier.
[0073] Clause 6. A method according to any one of clauses 1 to 5, wherein the request from the token holder to selectively lock the digital asset includes a request to exchange the first cryptographic token for the second cryptographic token.
[0074] Clause 7. The method according to any one of clauses 1 to 6 further includes receiving an indication of the location of the token holder; and wherein an indication or request to transfer a second encrypted token to the token holder is only made when the location of the token holder is within a predefined distance of a predefined location.
[0075] Clause 8. The method according to Clause 7 further includes: receiving a request from a second token holder among the multiple token holders to selectively lock a digital asset defined by one of the multiple cryptographic tokens at one of the multiple evolution stages; receiving an indication of the location of the token holder, wherein the location of the token holder is within the predefined distance of the predefined location, and wherein the location of the second token holder is not within the predefined distance of the predefined location; instructing or requesting a transfer of a third cryptographic token to the second token holder, the third cryptographic token having at least one attribute derived at least in part from the evolution stage of the digital asset at the time of the request; and wherein the second cryptographic token and the third cryptographic token have at least one different attribute.
[0076] Clause 9. The method according to any one of clauses 1 to 8 further includes, after instructing or requesting the transfer of the second cryptographic token to the token holder, instructing or requesting the destruction or transfer of the first cryptographic token to a destruction wallet.
[0077] Clause 10. A method according to any one of clauses 1 to 9, wherein the second cryptographic token represents a sub-asset or skin; and wherein the sub-asset or skin is capable of being combined with a main digital asset to change the properties of the main digital asset.
[0078] Clause 11. A method according to any one of clauses 1 to 10, wherein the plurality of first cryptographic tokens are ERC1155 tokens created according to Ethereum Improvement Proposal EIP-1155, and the second cryptographic token is an ERC721 token created according to Ethereum Improvement Proposal EIP-721.
[0079] Clause 12. A method for managing digital assets represented by cryptographic tokens, comprising: instructing or requesting the creation or minting of multiple initial cryptographic tokens via a first common digital contract registered on a distributed ledger, each token representing a digital asset having at least one attribute that can evolve through multiple evolutionary stages; distributing the multiple initial cryptographic tokens to multiple token holders; monitoring one or more external triggering events that can affect the evolution of the at least one attribute; updating the at least one attribute of the digital asset in response to the external triggering event; receiving a lock request from a token holder to selectively lock a digital asset defined by one of the initial cryptographic tokens at a specific evolutionary stage; instructing or requesting the creation or minting of subsequent cryptographic tokens, the subsequent cryptographic token capturing the state of the digital asset at the specific evolutionary stage; and instructing or requesting the transfer of the subsequent cryptographic token to a digital wallet or account of the requesting token holder.
[0080] Clause 13. The method of clause 12, wherein the external triggering event is an event that occurs in the physical world, a digital or virtual environment, or a video game environment.
[0081] Clause 14. A method according to any one of clauses 12 to 13, wherein monitoring one or more external triggering events includes receiving input from a blockchain oracle to verify and process the occurrence of the external triggering event.
[0082] Clause 15. A method according to any one of clauses 12 to 14, wherein the at least one attribute of the digital asset comprises a visual or graphical representation, an alphanumeric identifier, or a combination thereof.
[0083] Clause 16. A method according to any one of clauses 12 to 15, wherein the lock request from the token holder comprises a request to exchange the initial cryptographic token for the subsequent cryptographic token.
[0084] Clause 17. The method according to any one of clauses 12 to 16 further includes: receiving an indication of the location of the token holder at the same time as receiving the lock request; and applying geographic restrictions on the transfer of subsequent encrypted tokens based on the location of the token holder relative to a predefined location.
[0085] Clause 18. The method according to any one of Clauses 12 to 17 further includes invalidating the initial crypto token by transferring the initial crypto token to a destruction wallet or marking the initial crypto token as inactive after transferring the subsequent crypto token to the requesting token holder.
[0086] Clause 19. A method according to any one of clauses 12 to 18, wherein the subsequent cryptographic token represents a digital sub-asset or a digital asset modifier that is capable of being combined with a primary digital asset to modify one or more properties of the primary digital asset.
[0087] Clause 20. A method according to any one of clauses 12 to 19, wherein the plurality of initial cryptographic tokens are ERC1155 tokens created according to Ethereum Improvement Proposal EIP-1155, and the subsequent cryptographic tokens are ERC721 tokens created according to Ethereum Improvement Proposal EIP-721.
[0088] Clause 21. An electronic computing system configured to perform the method of any one of clauses 1 to 20.
Claims
1. A method for selectively locking encrypted digital assets, comprising: instructing or requesting, via a first common digital contract registered to a distributed ledger, the creation or minting of a plurality of first cryptographic tokens, wherein each cryptographic token of the plurality of cryptographic tokens defines a digital asset comprising properties operable to evolve or change through a plurality of evolutionary stages; instructing the transfer of the plurality of cryptographic tokens to a plurality of token holders; receiving a request from a token holder of the plurality of token holders to selectively lock a digital asset defined by one of the plurality of cryptographic tokens at one of the plurality of evolution stages; Instructing or requesting transfer of a second cryptographic token to the token holder, the second cryptographic token having at least one property derived at least in part from the evolutionary stage of the digital asset at the time of the request.
2. A method according to claim 1, wherein the attribute is operable to evolve or change in response to an external triggering event.
3. The method of claim 2, wherein the external triggering event is an event occurring in the real / physical world or within a digital / virtual environment or a gaming environment.
4. The method of claim 2, further comprising receiving, via a blockchain oracle, an indication that the external triggering event has occurred; and The property is changed in response to the indication that the external triggering event has occurred.
5. The method of claim 1, wherein the attribute is an element of a graphical representation of the digital asset or a discrete alphanumeric identifier.
6. The method of claim 1, wherein the request from the token holder to selectively lock the digital asset comprises a request to exchange the first cryptographic token for the second cryptographic token.
7. The method of claim 1 , further comprising receiving an indication of a location of the token holder; and Wherein the transfer of the second encrypted token to the token holder is instructed or requested only when the location of the token holder is within a predefined distance of a predefined location.
8. The method according to claim 7, further comprising: receiving a request from a second token holder of the plurality of token holders to selectively lock a digital asset defined by one of the plurality of cryptographic tokens at one of the plurality of evolution stages; receiving an indication of a location of the token holder, wherein the location of the token holder is within the predefined distance of the predefined location, and wherein the location of the second token holder is not within the predefined distance of the predefined location; Instructing or requesting a transfer of a third cryptographic token to the second token holder, the third cryptographic token having at least one attribute derived at least in part from the evolutionary stage of the digital asset at the time of the request; and wherein the second cryptographic token and the third cryptographic token have at least one different attribute.
9. The method according to claim 1 also includes instructing or requesting that the first cryptographic token be destroyed or transferred to a destruction wallet after instructing or requesting that the second cryptographic token be transferred to the token holder.
10. The method of claim 1, wherein the second cryptographic token represents a sub-asset or a skin; and The sub-asset or skin can be combined with the main digital asset to change the properties of the main digital asset.
11. The method according to claim 1, wherein the plurality of first cryptographic tokens are ERC1155 tokens created according to Ethereum Improvement Proposal EIP-1155, and the second cryptographic tokens are ERC721 tokens created according to Ethereum Improvement Proposal EIP-721.
12. A method for managing digital assets represented by cryptographic tokens, comprising: Instructing or requesting, via a first common digital contract registered on a distributed ledger, the creation or minting of a plurality of initial cryptographic tokens, each token representing a digital asset having at least one property capable of evolving through a plurality of evolutionary stages; Distributing the plurality of initial cryptographic tokens to a plurality of token holders; monitoring one or more external triggering events capable of influencing the evolution of the at least one attribute; updating the at least one attribute of the digital asset in response to the external triggering event; receiving a lock request from a token holder to selectively lock a digital asset defined by one of the initial cryptographic tokens at a particular evolution stage; Instructing or requesting the creation or minting of a subsequent cryptographic token that captures the state of the digital asset at the particular stage of evolution; as well as Instructing or requesting the transfer of said subsequent cryptographic tokens to a digital wallet or account of the requesting token holder.
13. The method of claim 12, wherein the external triggering event is an event occurring in the physical world, a digital or virtual environment, or a video game environment.
14. The method of claim 12, wherein monitoring one or more external triggering events comprises receiving input from a blockchain oracle to verify and process the occurrence of the external triggering event.
15. The method of claim 12, wherein the at least one attribute of the digital asset comprises a visual or graphical representation, an alphanumeric identifier, or a combination thereof.
16. The method of claim 12, wherein the lock request from the token holder comprises a request to exchange the initial cryptographic token for the subsequent cryptographic token.
17. The method according to claim 12, further comprising: receiving an indication of a location of the token holder concurrently with receiving the lock request; as well as Based on the location of the token holder relative to a predefined location, geographic restrictions are applied to the transfer of subsequent encrypted tokens.
18. The method of claim 12 further comprises, after transferring the subsequent crypto token to the requesting token holder, invalidating the initial crypto token by transferring the initial crypto token to a destruction wallet or marking the initial crypto token as inactive.
19. The method of claim 12, wherein the subsequent cryptographic token represents a digital sub-asset or a digital asset modifier that can be combined with a primary digital asset to modify one or more properties of the primary digital asset.
20. The method of claim 12, wherein the plurality of initial cryptographic tokens are ERC1155 tokens created according to Ethereum Improvement Proposal EIP-1155, and the subsequent cryptographic tokens are ERC721 tokens created according to Ethereum Improvement Proposal EIP-721.
