Systems and methods for managing digital asset functionality based on achievement of a benchmark

Abstract

A system and method for managing digital asset functionality based on achievement of a criterion are disclosed. An exemplary implementation requires or instructs that a user receive from a digital asset distribution platform a collectible digital asset within the user's digital wallet, where the collectible digital asset is correlated with an entity, determine whether a condition is met, and upon determining that the condition is not met, prevent the acquisition of the collectible digital asset by the digital wallet or restrict a set of rights to the correlated entity, and upon determining that the condition is met, permit the acquisition of the collectible digital asset or permit the set of rights.

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the priority benefit of U.S. Provisional Patent Application No. 63 / 339,147, entitled "SYSTEMS AND METHODS TO MANAGE DIGITAL ASSET FUNCTIONALITY BASED ON FULFILLMENT OF CRITERIA", filed on May 6, 2022. The subject matter of this related application is incorporated herein by reference.

[0002] This disclosure relates to systems and methods for managing digital asset functionality based on fulfillment of criteria.

Background Art

[0003] Existing methods of distributing digital assets, such as non - fungible tokens, correlated with an entity, cannot facilitate a dynamic, meaningful, and legally enforceable relationship between the original content creator of the correlated entity and the user who collects the collectible digital asset. Such deficiencies can expose content creators to unnecessary liabilities and / or can prevent additional features that can be added to the correlated entity.

Summary of the Invention

[0004] One aspect of the present disclosure relates to a system configured to manage digital asset functionality based on the achievement of criteria. The system may determine whether criteria are met before authorizing a user to acquire collectible digital assets associated with an entity or before permitting a set of rights to an entity associated with already acquired collectible digital assets. The criteria may include owning a specialized digital asset representing consent to an agreement, an established connection with one or more external member systems, completion of a task (e.g., viewing all movies in a collection), and / or other criteria. When it is determined that the criteria are met, permission may be granted to acquire the collectible digital asset or set of rights. By enforcing the achievement of criteria, a content creator or provider may identify which entity (e.g., content) associated with the collectible digital asset is authorized for additional feature updates. Further, by enforcing the achievement of criteria, the exchange of collectible digital assets among users may be restricted and regulated.

[0005] The system may include one or more hardware processors, electronic storage, and / or corresponding components configured by machine-readable instructions. The machine-readable instructions may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of an indication receiving component, a wallet determination component, an acquisition managing component, an interface presentation component, a rights managing component, and / or other instruction components.

[0006] The receiving component may be configured to receive from the digital asset distribution platform an indication that the user requests to obtain collectible digital assets within the digital wallet associated with the user. The collectible digital assets may be correlated with an entity. The digital wallet may correspond to an address tracked by a decentralized ledger.

[0007] The wallet determination component may be configured to determine whether the digital wallet contains dedicated digital assets. The dedicated digital assets may represent a contract and / or other information for holding a set of rights related to the correlated entity. The contract may be between a given user and the original holder of the set of rights.

[0008] When it is determined that the digital wallet does not contain dedicated digital assets, the acquisition management component may be configured to send a prevention indication to the digital asset distribution platform to prevent the acquisition of collectible digital assets by the digital wallet.

[0009] When it is determined that the digital wallet contains dedicated digital assets, the acquisition management component may be configured to send an authorization indication to the digital asset distribution platform that the digital wallet is permitted to acquire collectible digital assets.

[0010] In some implementations, one or more functions of the instruction component may be performed by smart contracts recorded on a decentralized ledger. In some implementations, in addition to, or as an alternative to, determining whether a digital wallet includes a dedicated digital asset, a determination of whether one or more conditions are met may be performed by a smart contract. Upon determining that one or more conditions are met, the smart contract may send an authorization instruction to the digital asset distribution platform. Upon determining that one or more conditions are not met, the smart contract may send a prevention instruction to the digital asset distribution platform.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 4

Figure 5

DETAILED DESCRIPTION OF THE INVENTION

[0012] FIG. 1 shows a system 100 configured to manage digital asset functions based on the achievement of criteria by one or more implementations. In some implementations, system 100 may include one or more servers 102. Server 102 may be configured to communicate with one or more client computing platforms 104 according to a client / server architecture and / or other architectures. Client computing platform 104 may be configured to communicate with other client computing platforms via server 102 and / or according to a peer-to-peer architecture and / or other architectures. A user may access system 100 via client computing platform 104.

[0013] As used herein, the term "digital asset" may refer to a serial code tracked on one or more permanent registries. A digital asset may be uniquely identified and / or uniquely identifiable. As used herein, rights regarding a digital asset may be tracked, recorded, and / or registered on one or more permanent registries. Thus, an individual digital asset may be a registry-tracked digital asset.

[0014] Individual digital assets can be associated with and / or correlated to another entity (sometimes referred to as a “correlating entity”) by technologies (including but not limited to smart contracts and / or other executable code on one or more persistent registries) provided and / or supported by one or more persistent registries on which rights regarding the individual digital assets are tracked. Thus, rights regarding a digital asset can correlate to one or more terms of rights (such as access) relating to the correlating entity (such as control and / or other accessibility). Transactions relating to digital assets recorded on a persistent registry can correlate to a transaction (or modification) of a correlating entity, and / or vice versa.

[0015] Including but not limited to, various types and / or combinations of correlating entities are envisioned within the scope of this disclosure, including physical objects and / or virtual objects, content, items, rights, memberships, grants, etc. The use of the singular “entity” or “correlating entity” is not intended to be limiting as multiple different objects, content, items, rights, memberships, grants, etc. can be correlated to a single digital asset. By way of non-limiting example, correlating entities can be physical items (such as artworks, tickets to an event), a subscription to certain media content, content, etc. Content can include images, videos, graphic image files, famous person signatures, sound bytes of audio files, audio files, and / or other content. In some implementations, correlating entities can refer to any item or object related to art and entertainment that a user can own, sell, trade, lend, discard, and / or cause to be issued using ownership, access, or control (including exchange through challenge) over it.

[0016] If a digital asset cannot be functionally and / or physically distinguished from other digital assets, the digital asset may be fungible. If a digital asset is unique or one-of-a-kind, the digital asset may be fungible. For example, a particular individual may be non-fungible. If there is a limited set of similar but distinguishable digital assets, the digital asset may be semi-fungible. For example, a limited quantity of images of a sports team for a particular year may be semi-fungible. For example, digital tickets for shows, concerts, exhibitions, and / or other events may be semi-fungible. Semi-fungible digital assets are considered to be unique, "not fungible," or non-fungible digital assets. In some implementations, digital assets may include non-fungible tokens, fungible tokens, semi-fungible tokens, and / or other digital assets.

[0017] In some implementations, a persistent registry, or decentralized ledger 117, may be implemented by a registry server or a decentralized database server. The terms "persistent registry" and "decentralized ledger" may be used interchangeably herein. The terms "registry server" and "decentralized database server" may be used interchangeably herein. In some implementations, one or more persistent registries may be a decentralized registry and / or an immutable registry. In some implementations, one or more persistent registries may be one or more databases in which rights regarding individual digital assets are tracked and / or recorded. In some implementations, a blockchain is maintained by a distributed computing platform (not shown in FIG. 1). In some implementations, the distributed computing platform may be implemented by, or be the same as, client computing platform 104 and / or a server (e.g., including one or more registry servers). The distributed computing platform may support virtual machines (not shown in FIG. 1). The distributed computing platform and / or the virtual machine may form a runtime environment for smart contracts and / or other executable code. The distributed computing platform may include electronic storage configured to store some or all of an individual blockchain. For example, a smart contract may be stored on one or more blockchains and / or another persistent registry. In some implementations, the distributed computing platform may be an EOSIO platform. In some implementations, the distributed computing platform may be similar to, or based on, the EOSIO platform. In some implementations, the distributed computing platform may be Ethereum. In some implementations, the distributed computing platform may be similar to, or based on, Ethereum. In some implementations, the virtual machine may be a distributed and / or decentralized virtual machine.

[0018] In some implementations, at least one of the persistent registries can be a private - permissioned persistent registry (e.g., a private - permissioned blockchain). A private - permissioned persistent registry can be configured to record information and / or track addresses (e.g., corresponding to digital wallets, smart contracts, etc.). The recorded information can include rights regarding digital assets. For example, ownership and / or other accessibilities can be modified. In some implementations, ownership and / or other rights can be indicated by an address tracked by a persistent registry corresponding to a user's digital wallet. In some implementations, a digital asset can be removed from one persistent registry and added or recorded on another persistent registry. In some implementations, at least one of the persistent registries implemented by a registry server is a public persistent registry (e.g., a public blockchain). A public persistent registry can be configured as part of any of the EOSIO mainnet, the Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 configured to perform transactions of Ether (ETH) between accounts, or a derivative of EOSIO configured to perform transactions of EOS between different accounts.

[0019] Elements of a blockchain or another persistent registry can be grouped together in units called blocks. For example, an individual block can include one or more digital assets and one or more transactions. For example, an individual block can be linked to one or more other individual blocks. Individual blocks can be linked or chained together to form a structure of blocks and / or a hierarchy of blocks such as a chain of blocks. An individual block can include one or more digital assets, one or more transactions, smart contracts, and / or other information.

[0020] In some implementations, one or more persistent registries implemented by a registry server may be publicly accessible. In some implementations, for example, one or more databases may be accessible via a mobile application or website. In some implementations, one or more persistent registries implemented by a registry server may be private and / or permissioned. In some implementations, one or more persistent registries implemented by a registry server may be append-only. In some implementations, existing blocks of one or more persistent registries implemented by a registry server cannot be substantially modified or deleted unless multiple copies are modified. This is unlikely to occur provided that multiple copies are stored on different computing platforms at different geographical locations. The persistent registry may preferably be replicated on multiple computing platforms at multiple different geographical locations. Further, individual blocks may be linked to each other in a tamper-proof manner, such as by using hash chains and / or digital signatures. Specifically, a hash value may be generated using a fixed-output-length one-way hashing function that takes a variable-length input, and the hash value may be substantially impossible to reverse (or at least computationally infeasible). Thus, the hashing function may implement one-way encryption. By way of non-limiting example, the hashing function may be SHA-256, BLAKE2, SHAKE256, and / or another hashing function. The contents of individual blocks, transactions, and / or articles may be digitally signed in a manner that proves integrity and / or prevents tampering, such as by providing authentication and non-repudiation.

[0021] Server 102 may be configured by machine-readable instructions 106. The machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of an instruction receiving component 108, a wallet determination component 110, an acquisition management component 112, an interface presentation component 114, a rights management component 116, and / or other instruction components.

[0022] The receiving component 108 can be configured to receive from the digital asset distribution platform an indication that the user is requesting to obtain collectible digital assets within a digital wallet associated with the user. The collectible digital assets can be a specific type of digital assets that the user collects or digital assets from a specific distributor or creator. The digital asset distribution platform can facilitate the user to perform transactions such as purchase, sale, trading, lending, and / or other transactions related to digital assets. Obtaining collectible digital assets can include purchasing, trading, receiving as a loan, receiving as a gift, and / or other acquisitions of collectible digital assets. The collectible digital assets can be correlated with an entity. When obtaining the collectible digital assets, the user can receive and / or hold a set of rights. The set of rights can include the right to trade the collectible digital assets, the right to lend the collectible digital assets, the right to view the correlated entity, the right to present the correlated entity, the right to sell the collectible digital assets, the right to share the correlated entity, and / or other rights. The digital wallet can correspond to an address tracked by the decentralized ledger 117. The original holder of the set of rights can be the creator of the correlated entity. In some implementations, the creator of the correlated entity may have created the collectible digital assets such that the collectible digital assets are recorded on the decentralized ledger 117. In some implementations, the creator of such collectible digital assets can be recorded on the decentralized ledger 117 as its owner until a subsequent acquisition.As used herein, the term "create" or variations thereof may refer to the process, transaction, procedure, operation, and / or steps of performing, initiating, and / or executing to bring about the instantiation of a given digital asset, including the establishment of ownership, the recording of ownership on the decentralized ledger 117, the definition of the appearance of a given digital asset (e.g., a selected representative image, default image), and the correlation of a given digital asset to a set of rights within the electronic storage 120. In some implementations, creating a given digital asset may include constructing an executable program that instantiates the given digital asset. The executable program may be sent to a decentralized computing platform capable of executing the program. In some implementations, the execution of the program by the decentralized computing platform may display a contract on the decentralized platform.

[0023] The wallet determination component 110 can be configured to determine whether a digital wallet associated with a user includes a dedicated digital asset. In some implementations, the dedicated digital asset can be a member of a dedicated collection. That is, the dedicated digital asset can be a particular type of digital asset. For example, the dedicated digital asset can be directly created or established by a particular service by utilizing a dedicated smart contract. The dedicated smart contract can be stored on the decentralized ledger 117. The dedicated digital asset may require or represent consent to a contract between i) a given user who will hold a set of rights associated with the associated entity and ii) the original holder of the set of rights, and / or may require completion of other preconditions. In some implementations, the dedicated digital asset is associated with an entity, i.e., the associated entity. The associated entity of the dedicated digital asset can be different from the associated entity of the collectible digital asset. As a non-limiting example, the associated entity of the dedicated digital asset can include a digital membership card, a key graphic, a magic wand graphic, and / or other entities. In some implementations, a dedicated digital asset established by a particular service utilizing a dedicated smart contract may not have an owner recorded on the decentralized ledger 117. In some implementations, a dedicated digital asset established by a particular service utilizing a dedicated smart contract may have a particular service as the owner recorded on the decentralized ledger 117.

[0024] A given user may need to agree to a contract and / or complete other preconditions before receiving the dedicated digital assets within the user's digital wallet. In some implementations, it may be permitted to obtain dedicated digital assets from a digital asset distribution platform upon receiving the user's agreement to the contract. By way of non-limiting example, the contract may specify that the associated entity is made available to the holder of the collectible digital asset, certain transfer and use restrictions, that the holder does not own the associated entity itself, and / or other information. The contract may include a set of rights specifying such availability, transfer restrictions, and user restrictions. In some implementations, a dedicated smart contract that creates dedicated digital assets may be encoded to restrict the transfer of dedicated digital assets between different users' digital wallets and / or to restrict transfers between the same user's digital wallets. In some implementations, the acquisition of dedicated digital assets may include a set of restrictions on the dedicated digital assets. The set of restrictions may restrict the user from transferring, trading, lending, selling, or surrendering to another user. Thus, the dedicated smart contract can ensure that a user can only hold the dedicated digital assets within their digital wallet upon agreeing to the contract, and cannot hold user-dedicated digital assets unless the user agrees to the contract.

[0025] In some implementations, the digital asset distribution platform may be associated with an existing known decentralized ledger. Thus, the collectible digital assets referred to herein may be exclusive to the dedicated digital assets. That is, a collection smart contract that creates collectible digital assets may be encoded to specify that the collectible digital assets are dependent on the dedicated digital assets. Thus, the set of rights regarding the collectible digital assets and their associated entities may depend on the ownership of the dedicated digital assets rather than any other digital assets in circulation. The collection smart contract may be stored on the decentralized ledger 117.

[0026] In some implementations, the digital asset distribution platform can be a new decentralized ledger. Thus, the dependency of collectible digital assets on a dedicated digital asset can be built into all transactions recorded on this decentralized ledger. Therefore, there is no need to encode the collectible digital assets to be exclusive to the dedicated digital asset during establishment.

[0027] The acquisition management component 112 can be configured to send an authorization instruction to the digital asset distribution platform when it determines that the digital wallet contains a dedicated digital asset. The authorization instruction can convey that the digital wallet is permitted to acquire collectible digital assets. That is, as a non-limiting example, the user accepts a contract and thus the digital wallet has a dedicated digital asset. Therefore, the user is permitted to purchase, trade, or acquire collectible digital assets via the digital asset distribution platform.

[0028] The acquisition management component 112 can be configured to send a prevention instruction to the digital asset distribution platform to prevent the acquisition of collectible digital assets by the digital wallet when it determines that the digital wallet does not contain a dedicated digital asset. The prevention instruction can convey that the digital wallet is not permitted to acquire collectible digital assets. That is, the user has not accepted a contract and the digital wallet does not contain a dedicated digital asset.

[0029] In some implementations, when it is determined that the digital wallet does not include dedicated digital assets, the interface presentation component 114 may be configured to effectuate the presentation of an interface to the digital asset distribution platform. The presentation of the interface may facilitate the user's acceptance of the agreement and / or the completion of other preconditions. In some implementations, effectuating the presentation of the interface may include sending an interface instruction to the digital asset distribution platform. The interface instruction may require the digital asset distribution platform to provide an interface that enables the user to view the agreement, accept the agreement, and / or complete other preconditions and then obtain dedicated digital assets within the digital wallet.

[0030] In some implementations, the acquisition management component 112 may be configured to receive a contract instruction from the digital asset distribution platform. The contract instruction may convey that the user has accepted the contract and / or completed other preconditions via the interface and / or other platforms, and then the digital wallet has obtained dedicated digital assets. Accordingly, the digital wallet may be permitted to obtain collectible digital assets.

[0031] In some implementations, a user may be permitted to acquire collectible digital assets via a digital asset distribution platform, but when it is determined that the digital wallet does not contain dedicated digital assets, the set of rights to the associated entities is restricted and may remain restricted until the user accepts a contract and acquires dedicated digital assets. Accordingly, in some implementations, the instruction receiving component 108 may be configured to receive from the digital asset distribution platform an instruction that the digital wallet associated with the user has acquired collectible digital assets. In some implementations, the determination as to whether the digital wallet contains dedicated digital assets may be performed by the wallet determination component 110 in response to receiving an instruction that the digital wallet associated with the user has acquired collectible digital assets.

[0032] When it is determined that the digital wallet does not contain dedicated digital assets, the rights management component 116 may be configured to restrict the set of rights to the associated entities of the collectible digital assets and / or the collectible digital assets themselves. Conversely, when it is determined that the digital wallet contains dedicated digital assets, the rights management component 116 may be configured to permit the set of rights to the associated entities of the collectible digital assets and / or the collectible digital assets themselves. Permitting the set of rights may include generating and executing a set of instructions to record on the decentralized ledger 117 the user's address and thus that the user is identified as the holder of the set of rights.

[0033] In some implementations, some or all of the functionality of components 108, 110, 112, 114, and / or 116 may be implemented by client computing platform 104, i.e., a distributed computing platform, configured by smart contract 124 to perform such functionality. That is, smart contract 124 may be configured to receive from the digital asset distribution platform an indication that the user is requesting to obtain collectible digital assets within a digital wallet associated with the user. In some implementations, some or all of the functionality of smart contract 124 may be implemented by components 108, 110, 112, 114, and / or 116.

[0034] Smart contract 124 may be configured to determine whether one or more conditions regarding the digital wallet are met. The conditions may include a first condition, a second condition, and / or other conditions. By way of non-limiting example, the condition may require that the digital wallet be coupled to an account associated with an external member system. The external member system may include a streaming service, a subscription service, a club membership, an identification system, and / or other external membership systems. In some implementations, the external member system may be the creator of an entity associated with the collectible digital asset. The account may be associated with the user. In some implementations, upon determining that the digital wallet is not coupled to any account associated with an external member system associated with the user, smart contract 124 may be configured to enable the user to create an account. In some implementations, the user may have an account and smart contract 124 may be configured to enable the user to couple the digital wallet to the account. For example, smart contract 124 may implement a presentation of a user interface to the external member system for the user to input information and record it within the external member system.

[0035] Another condition may require that the digital wallet include dedicated digital assets. When it is determined that the digital wallet does not include dedicated digital assets, smart contract 124 may be configured to perform the same or a similar function as interface presentation component 114. That is, smart contract 124 may be configured to perform or instigate the presentation of an interface to the digital asset distribution platform. The presentation may facilitate the user's acceptance of the contract and / or completion of other preconditions, and subsequent acquisition of dedicated digital assets within the digital wallet via the digital asset distribution platform. Performing the presentation of the interface may include smart contract 124 sending an interface instruction to the digital asset distribution platform. Other conditions may be contemplated, such as creating other digital assets, holding such digital assets within the digital wallet, performing another smart contract by initiating a transaction, and / or other conditions.

[0036] In some implementations, when smart contract 124 determines that one or more conditions are met, smart contract 124 may be configured to send an authorization instruction to the digital asset distribution platform that the digital wallet is permitted to acquire collectible digital assets. Further, when smart contract 124 determines that one or more conditions are not met, smart contract 124 may be configured to send a prevention instruction to the digital asset distribution platform to prevent the digital wallet from acquiring collectible digital assets.

[0037] In some implementations, a user may be permitted to acquire digital assets that are collectible via a digital asset distribution platform, but the set of rights to the associated entities may be restricted when it is determined that one or more conditions are not met. Thus, in some implementations, smart contract 124 may be configured to receive an indication that a digital wallet associated with the user has acquired a collectible digital asset. In some implementations, smart contract 124 may be configured to perform the same or a similar function as rights management component 116. That is, when smart contract 124 determines that one or more conditions are not met, smart contract 124 may be configured to restrict the set of rights with respect to the associated entities. Further, when smart contract 124 determines that one or more conditions are met, smart contract 124 may be configured to permit the set of rights with respect to the collectible digital assets.

[0038] In some implementations, the smart contract 124 can be configured to determine whether additional conditions within an external member system are met by an account and thus by a user. The conditions can include such additional conditions. For example, the additional conditions can include watching all movies in a collection, watching an entire television series, completing all levels of a game, and / or other additional conditions. When determining the achievement of the additional conditions, the entity associated with the collectible digital asset held by the user's digital wallet can be modified. For example, the modification to the associated entity can include revealing new details in a movie poster graphic, unlocking new features in a game, adding extended scenes, sending a new piece for a physical item to the user, and / or other modifications to the entity associated with the collectible digital asset. When determining that the additional conditions are not met, the entity associated with the collectible digital asset may not be modified or portions of the associated entity may be obscured.

[0039] In some implementations, the wallet determination component 110, smart contract 124, and / or other components may be configured to determine the achievement of one or more conditions to enable additional functionality by a user or a digital wallet associated with the user. That is, in some implementations, the authorization instruction may convey that, in addition to the digital wallet being permitted to participate in a particular transaction and create digital assets, and / or the user associated with the digital wallet being permitted to acquire collectible digital assets, a particular action may be performed and / or a particular right may be retained. Thus, upon determination that one or more conditions are achieved, the authorization instruction may be further transmitted to one or more other platforms. For example, achievement of one or more conditions may trigger transmission of an authorization instruction to an admission platform that permits or sells admission to an event and / or location, and thus permits the user to go to the event and / or a set of particular amusement parks.

[0040] In some implementations, the server 102, client computing platform 104, and / or external resource 118 may be operably linked via one or more electronic communication links. For example, such electronic communication links may be established at least in part via a network 124 such as the Internet and / or other networks. It is not intended to be limiting, and it will be understood that the scope of the present disclosure includes implementations in which the server 102, client computing platform 104, and / or external resource 118 may be operably linked via any other communication medium.

[0041] A given client computing platform 104 may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform 104 to interface with the system 100 and / or external resources 118 and / or to provide other functionality attributable to the client computing platform 104 herein. By way of non-limiting example, a given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a netbook, a smartphone, a gaming console, and / or other computing platforms.

[0042] External resources 118 may include information sources external to the system 100, external entities participating with the system 100, and / or other resources. In some implementations, some or all of the functionality attributable to external resources 118 herein may be provided by resources included within the system 100.

[0043] The server 102 may include electronic storage 120, one or more processors 122, and / or other components. The server 102 may include communication lines, or ports, for enabling exchange of information with the network 124 and / or other computing platforms. The illustration of server 102 in FIG. 1 is not intended to be limiting. The server 102 may include a plurality of hardware, software, and / or firmware components that operate together to provide the functionality attributable to the server 102 herein. For example, the server 102 may be implemented by a cloud of computing platforms operating together as the server 102.

[0044] The electronic storage 120 may include a non-transitory storage medium that stores information electronically. The electronic storage medium of the electronic storage 120 may include system storage that is provided integrally with the server 102 (i.e., substantially non-removable), and / or removable storage that is removably connectable to the server 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). The electronic storage 120 may include one or more of an optically readable storage medium (e.g., an optical disk, etc.), a magnetically readable storage medium (e.g., a magnetic tape, a magnetic hard drive, a floppy drive, etc.), a charge-based storage medium (e.g., an EEPROM, a RAM, etc.), a solid-state storage medium (e.g., a flash drive, etc.), and / or other electronically readable storage media. The electronic storage 120 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and / or other virtual storage resources). The electronic storage 120 may store software algorithms, information determined by the processor 122, information received from the server 102, information received from the client computing platform 104, and / or other information that enables the server 102 to function as described herein.

[0045] Processor 122 may be configured to provide information processing functions within server 102. Accordingly, processor 122 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and / or other mechanisms for electronically processing information. In FIG. 1, processor 122 is shown as a single associated entity, but this is for illustrative purposes only. In some implementations, processor 122 may include multiple processing devices. Such processing devices may be physically located within the same device, or processor 122 may represent the processing functions of multiple devices operating in cooperation. Processor 122 may be configured to execute components 108, 110, 112, 114, and / or 116, and / or other components. Processor 122 may be configured to execute components 108, 110, 112, 114, and / or 116, and / or components by some combination of software, hardware, firmware, software, hardware, and / or firmware, and / or other mechanisms for configuring processing functions on processor 122. As used herein, the term "component" may refer to any component or set of components that implement the functions attributable to the component. This may include one or more physical processors during execution of processor-readable instructions, processor-readable instructions, circuits, hardware, storage media, or any other component.

[0046] In FIG. 1, components 108, 110, 112, 114, and / or 116 are shown as being implemented within a single processing device. However, in an implementation where processor 122 includes multiple processing devices, it should be understood that one or more of components 108, 110, 112, 114, and / or 116 may be implemented separately from other components. The descriptions of the functions provided by the different components 108, 110, 112, 114, and / or 116, which are described below, are for purposes of illustration and are not intended to be limiting. This is because any one of components 108, 110, 112, 114, and / or 116 may provide more or fewer functions than described. For example, one or more of components 108, 110, 112, 114, and / or 116 may be omitted, and some or all of their functions may be provided by another one of components 108, 110, 112, 114, and / or 116. As another example, processor 122 may be configured to execute one or more additional components that implement some or all of the functions that would otherwise be attributed to one of components 108, 110, 112, 114, and / or 116, which are described below.

[0047] Figure 3A shows that the system 100 (identical to FIG. 1) receives an instruction 302 from the digital asset distribution platform 300 requesting that the user associated with the digital wallet 304 acquire a collectible digital asset 306. The digital asset distribution platform 300 may distribute (e.g., sell and facilitate the transaction of) the collectible digital asset 306 and may distribute a dedicated digital asset 308. The system 100 may determine that the digital wallet 304 includes other digital assets 326 and does not include one of the dedicated digital assets 308 that represents consent to the contract 314. In response, the system 100 may send a prevention instruction 310 to the digital asset distribution platform 300 to prevent the digital wallet 304, and thus the user, from acquiring the collectible digital asset 306. Further, the system 100 may cause the user to be presented with a user interface 312 for the digital asset distribution platform 300 (e.g., via a client computing platform such as a desktop computer not shown). The user interface 312 may present the contract 314 and enable the user to consent to the contract 314. Upon the user's consent, a contract instruction 316 indicating the user's consent may be sent to the system 100.

[0048] Subsequent to FIG. 3A, FIG. 3B shows that after the contract instruction 316 is sent to the system of FIG. 3A, the same digital wallet 304 as in FIG. 3A includes a dedicated digital asset 308a. The dedicated digital asset 308a may be one of the dedicated digital assets 308 of FIG. 3A. Thus, when the system 100 (identical to FIG. 3A) receives an instruction 318 from the digital asset distribution platform 300 that the user is requesting to acquire the collectible digital asset 306, the system 100 may send an authorization instruction 320 that the user may be permitted to acquire the collectible digital asset 306.

[0049] FIG. 4 shows that system 100 (same as FIG. 3A) receives an instruction 322 from digital asset distribution platform 300 (same as FIGS. 3A - 3B) indicating that a user associated with digital wallet 304 requests collectible digital asset 306. System 100 may determine whether one or more conditions are met, such as whether digital wallet 324 associated with the user is connected to external member system 350. For connection to external member system 350, system 100 may send an authorization instruction 326 indicating that digital wallet 324 is permitted to obtain collectible digital asset 306.

[0050] FIG. 5 shows that system 100 (same as FIG. 1) receives an acquisition instruction 328 from digital asset distribution platform 300 (same as FIGS. 3A - 3B and FIG. 4) indicating that digital wallet 334 associated with the user has obtained a collectible digital asset 306b, i.e., one of the collectible digital assets 306. System 100 may determine whether one or more conditions are met, such as whether digital wallet 334 is connected to external member system 350. Due to the lack of connection to external member system 350, system 100 may restrict a set of rights 330 for entity 332 associated with collectible digital asset 306b. Entity 332 and set of rights 330 may be stored in electronic storage 120 (same as FIG. 1).

[0051] FIG. 2 shows a method 200 for managing digital asset functionality based on achievement of a criterion by one or more implementations. The operations of method 200 presented below are exemplary. In some implementations, method 200 may involve one or more additional operations not described and / or may not involve one or more of the operations discussed. Further, the operations of method 200 are shown in FIG. 2, and the order described below is not intended to be limiting.

[0052] In some implementations, method 200 may be implemented on one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and / or other mechanism for electronically processing information). The one or more processing devices may include one or more devices that execute some or all of the operations of method 200 in response to instructions electronically stored on an electronic storage medium. The one or more processing devices may include one or more devices configured to be specifically designed for performing one or more executions of the operations of method 200 through hardware, firmware, and / or software.

[0053] Operation 202 may include receiving, from a digital asset distribution platform, an indication that a user is requesting acquisition of collectible digital assets within a digital wallet associated with the user. The collectible digital assets are associated with a correlated entity. The digital wallet may represent various digital assets owned or held by the user. The digital wallet may correspond to an address tracked by a decentralized ledger. According to one or more implementations, operation 202 may be performed by smart contract 124.

[0054] Operation 204 may include determining whether one or more conditions regarding the digital wallet are met. According to one or more implementations, operation 204 may be performed by smart contract 124.

[0055] Operation 206 may include sending, to the digital asset distribution platform, an authorization indication that acquisition of collectible digital assets by the digital wallet is permitted upon determination that one or more conditions are met. According to one or more implementations, operation 206 may be performed by smart contract 124.

[0056] Operation 208 may include sending a prevention instruction to the digital asset distribution platform to prevent the acquisition of collectible digital assets by the digital wallet when it is determined that one or more conditions are not met. According to one or more implementations, operation 208 may be performed by smart contract 124.

[0057] Based on what is currently considered to be the most realistic and preferred implementation for purposes of illustration, the present technology has been described in detail, but such details are for that purpose only and are not limited to the implementations in which the technology is disclosed. Rather, it is to be understood that modifications and equivalent configurations within the spirit and scope of the appended claims are intended to be encompassed. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation may be combined with one or more features of any other implementation.

Claims

1. A system configured to manage digital asset functions based on the achievement of criteria, receiving, from a digital asset distribution platform, an indication that a digital wallet associated with a user requests acquisition of collectible digital assets within the digital wallet associated with the user, wherein the collectible digital assets are correlated with an entity and the digital wallet corresponds to an address tracked by a decentralized ledger; determining whether one or more conditions regarding the digital wallet are met; when determining that the one or more conditions are met, sending, to the digital asset distribution platform, an authorization instruction that the acquisition of the collectible digital assets by the digital wallet is permitted; when determining that the one or more conditions are not met, sending, to the digital asset distribution platform, a prevention instruction to prevent the acquisition of the collectible digital assets by the digital wallet one or more processors configured by machine-readable instructions to perform A system comprising.

2. The acquisition of the collectible digital assets includes a set of rights, the set of rights including the right to trade the collectible digital assets, the right to lend the collectible digital assets, the right to view the correlated entity, the right to present the correlated entity, and / or the right to sell the collectible digital assets. The system according to claim 1.

3. The one or more conditions include a first condition and a second condition, the first condition being that the digital wallet includes dedicated digital assets, the second condition being that the digital wallet is coupled to an account associated with an external member system, the account being associated with the user, and the one or more processors being further configured by the machine-readable instructions to enable the user to create the account and / or couple the digital wallet to the account when determining that the digital wallet is not coupled to any account associated with the external member system associated with the user. The system according to claim 1.

4. The system according to claim 3, wherein the dedicated digital asset represents a contract for holding a set of rights associated with the associated entity, and the contract is between a given user and the original holder of the set of rights.

5. When it is determined that the digital wallet does not include the dedicated digital asset, the one or more processors, by the machine-readable instructions, present an interface to the digital asset distribution platform to facilitate acceptance of the contract by the user and subsequent acquisition of the dedicated digital asset by the digital wallet. The system according to claim 4, further configured as such.

6. The one or more processors, by the machine-readable instructions, receive, from the digital asset distribution platform, a contract instruction that the user accepts the contract and that the dedicated digital asset exists within the digital wallet. The system according to claim 4, further configured as such.

7. A system configured to manage digital asset functionality based on achievement of criteria, receiving, from a digital asset distribution platform, an instruction that a digital wallet associated with a user has acquired a collectible digital asset, the collectible digital asset being correlated with an entity and the digital wallet corresponding to an address tracked by a decentralized ledger; determining, in response to the instruction, whether one or more conditions regarding the digital wallet are met; restricting a set of rights regarding the associated entity when it is determined that the one or more conditions are not met; and permitting the set of rights regarding the associated entity when it is determined that the one or more conditions are met. One or more processors configured by machine-readable instructions to perform the above. A system comprising the above.

8. The system according to claim 7, wherein the one or more conditions include a first condition, and the first condition is that the digital wallet includes a dedicated digital asset.

9. A method for managing digital asset functionality based on achievement of criteria, Receiving, from a digital asset distribution platform, an instruction that a user is requesting acquisition of collectible digital assets within a digital wallet associated with the user, wherein the collectible digital assets are associated with a correlated entity, and the digital wallet corresponds to an address tracked by a decentralized ledger, Determining whether one or more conditions regarding the digital wallet are met, When it is determined that the one or more conditions are met, sending, to the digital asset distribution platform, an authorization instruction that acquisition of the collectible digital assets by the digital wallet is permitted, When it is determined that the one or more conditions are not met, sending, to the digital asset distribution platform, a prevention instruction to prevent acquisition of the collectible digital assets by the digital wallet, A method comprising the above.

10. The method according to claim 9, wherein the acquisition of the collectible digital assets includes a set of rights, and the set of rights includes the right to trade the collectible digital assets, the right to lend the collectible digital assets, the right to view a correlated entity, the right to present the correlated entity, and / or the right to sell the collectible digital assets.

11. The one or more conditions include a first condition and a second condition. The first condition is that the digital wallet includes dedicated digital assets. The second condition is that the digital wallet is linked to an account associated with an external member system, and the account is associated with the user. When it is determined that the digital wallet is not linked to any account associated with the external member system associated with the user, enabling the user to create the account and / or link the digital wallet to the account. The method according to claim 9, further comprising the above.

12. The method according to claim 11, wherein the dedicated digital assets represent a contract for holding a set of rights associated with the correlated entity, and the contract is between a given user and the original holder of the set of rights.

13. When it is determined that the digital wallet does not contain the dedicated digital asset, present an interface to the digital asset distribution platform to facilitate acceptance of the contract by the user via the digital asset distribution platform and subsequent acquisition of the dedicated digital asset by the digital wallet The method according to claim 12, further comprising.

14. Receiving, from the digital asset distribution platform, a contract instruction that the user accepts the contract and that the digital wallet contains the dedicated digital asset The method according to claim 12, further comprising.

15. A method for managing digital asset functions based on achievement of criteria, comprising: Receiving, from a digital asset distribution platform, an instruction that a digital wallet associated with a user has acquired a collectible digital asset, wherein the collectible digital asset is associated with an associated entity and the digital wallet corresponds to an address tracked by a decentralized ledger; Determining, in response to the instruction, whether one or more conditions regarding the digital wallet are met; Restricting a set of rights regarding the associated entity when it is determined that the one or more conditions are not met; Permitting the set of rights regarding the associated entity when it is determined that the one or more conditions are met A method comprising.

Images