System and method for managing digital asset functionality based on satisfaction of criteria

Abstract

Systems and methods for managing digital asset functionality based on satisfaction of criteria are disclosed. An exemplary implementation may include receiving, from a digital asset distribution platform, an indication that a user is requesting to acquire a collectable digital asset in a digital wallet of the user or that the user has acquired the collectable digital asset, the collectable digital asset being associated with an entity; determining whether the condition (s) is satisfied; upon determining that the condition (s) are not satisfied, preventing the digital wallet from acquiring the collectable digital asset or limiting a set of permissions of related entities; and upon determining that the one or more conditions are satisfied, allowing acquisition of the collectable digital assets or allowing the set of permissions.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority to 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. Technical Field

[0003] The present invention relates to systems and methods for managing digital asset functionality based on satisfaction of standards. Background Art

[0004] Existing methods of distributing digital assets associated with an entity, such as non-fungible tokens, fail to facilitate dynamic, meaningful, and legally enforceable relationships between the original content creators of the associated entity and the users who collect the collectible digital assets. This shortcoming may expose content creators to unnecessary liability and / or hinder other functionality that could be added to the associated entity. Summary of the invention

[0005] One aspect of the present invention relates to a system configured to manage digital asset functionality based on the satisfaction of criteria. The system can determine whether criteria are met before authorizing a user to acquire a collectible digital asset associated with an entity, or before allowing an entity a set of permissions associated with an acquired collectible digital asset. The criteria can include possession of a dedicated digital asset (indicating agreement), a connection established with one or more external member systems, completion of a task (e.g., watching all movies in a collection), and / or other criteria. Upon determining that the criteria are met, authorization to acquire the collectible digital asset or the set of permissions can be allowed. By enforcing that the criteria are met, content creators or providers can identify which entities (e.g., content) associated with the collectible digital asset are authorized to update additional functionality. In addition, by enforcing that the criteria are met, the exchange of collectible digital assets between users can be restricted and regulated.

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

[0007] The indication receiving component may be configured to receive an indication from a digital asset distribution platform that a user is requesting to obtain a collectible digital asset in a digital wallet associated with the user. The collectible digital asset may be associated with an entity. The digital wallet may correspond to an address tracked by a decentralized ledger.

[0008] The wallet determination component may be configured to determine whether the digital wallet includes a dedicated digital asset. The dedicated digital asset may represent an agreement to hold a set of permissions and / or other information associated with a related entity. The agreement may be an agreement between a given user and the original holder of the set of permissions.

[0009] The acquisition management component may be configured to, upon determining that the digital wallet does not include the dedicated digital asset, send a prevention indication to the digital asset distribution platform preventing the digital wallet from acquiring the collectible digital asset.

[0010] The acquisition management component may be configured to, upon determining that the digital wallet does include the dedicated digital asset, send an authorization indication to the digital asset distribution platform allowing the digital wallet to acquire the collectible digital asset.

[0011] In some implementations, one or more functions of the instruction component may be performed by (one or more) 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, the (one or more) smart contracts may perform a determination of whether one or more conditions are satisfied. Upon determining that the one or more conditions are satisfied, the (one or more) smart contracts may send an authorization instruction to the digital asset distribution platform. Upon determining that the one or more conditions are not satisfied, the (one or more) smart contracts may send a prevention instruction to the digital asset distribution platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1

[0013] Systems configured to manage digital asset functionality based on satisfaction of criteria in accordance with one or more implementations are shown.

[0013] Figure 2

[0013] Methods of managing digital asset functionality based on satisfaction of standards in accordance with one or more implementations are shown.

[0014] Figure 3A An example implementation of a system configured to determine lack of possession of a dedicated digital asset and present an agreement to which a user can agree and subsequently obtain the dedicated digital asset in accordance with one or more implementations is shown.

[0015] Figure 3B

[0013] An example implementation of a system configured to enable a user to acquire a collectible digital asset based on possession of a dedicated digital asset in accordance with one or more implementations is shown.

[0016] Figure 4 Example implementations of a system configured to determine satisfaction of one or more conditions and responsively enable a user to obtain a collectible digital asset in accordance with one or more implementations are shown.

[0017] Figure 5 An example implementation of a system configured to determine that one or more conditions are not satisfied and, in response, enable a user to obtain a collectible digital asset with restricted rights in accordance with one or more implementations is shown. DETAILED DESCRIPTION

[0018] Figure 1 A system 100 configured to manage digital asset functionality based on satisfaction of standards according to one or more implementations is shown. In some implementations, the system 100 may include one or more servers 102. The server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client / server architecture and / or other architectures. The client computing platform(s) 104 may be configured to communicate with other client computing platforms through the server(s) 102 and / or according to a peer-to-peer architecture and / or other architectures. A user may access the system 100 through the client computing platform(s) 104.

[0019] As used herein, the term "digital asset" may refer to a serial code that is tracked on one or more permanent registries. A digital asset may be uniquely identified and / or uniquely identifiable. As used herein, rights associated with a digital asset may be tracked, recorded, and / or otherwise registered on one or more permanent registries. Thus, a personal digital asset may be a digital asset that is tracked by a registry.

[0020] Due to the technology provided and / or supported by one or more persistent registries (on which permissions associated with personal digital assets are tracked), personal digital assets can be associated and / or related to another entity (which may be referred to as a "related entity") (including but not limited to smart contracts and / or other executable code on one or more persistent registries). Therefore, permissions associated with digital assets can be related to the provision (e.g., control and / or other accessibility) of one or more permissions (e.g., accessibility) with respect to the related entity. Transactions involving digital assets recorded on the persistent registry can be related to certain transactions (or modifications) of the related entity, and vice versa.

[0021] Various types and / or combinations of related entities are contemplated within the scope of the present invention, including, but not limited to, physical and / or virtual objects, content, items, permissions, memberships, authorizations, and the like. The use of the singular "entity" or "related entity" is not intended to be limiting, as multiple different objects, content, items, permissions, memberships, authorizations, and the like may be associated with a single digital asset. As non-limiting examples, a related entity may be a physical object (e.g., a work of art, an event ticket), a subscription to certain media content, content, and the like. Content may include images, videos, graphic image files, signatures of notoriety, sound clips of audio files, audio files, and / or other content. In some implementations, a related entity may refer to any item or object related to art and entertainment for which a user may use, own, sell, trade, loan, destroy, and / or otherwise effect a change in ownership, access, or control (including changes through challenges).

[0022] A digital asset may be fungible if it is functionally and / or physically indistinguishable from another digital asset. A digital asset may be non-fungible if it is unique or one-of-a-kind. For example, a specific individual may be non-fungible. A digital asset may be semi-fungible if there is a limited number of similar but distinguishable digital assets. For example, a limited number of sports team images from a particular year may be semi-fungible. For example, digital tickets for performances, concerts, exhibitions, and / or other events may be semi-fungible. Semi-fungible digital assets are considered unique, "non-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.

[0023] In some implementations, the permanent registry or (one or more) distributed ledgers 117 can be implemented by a registry server or a distributed database server. The terms "permanent registry" and "distributed ledger" can be used interchangeably herein. The terms "registry server" and "distributed database server" can be used interchangeably herein. In certain implementations, the one or more permanent registries can be decentralized and / or immutable registries. In some implementations, the one or more permanent registries can be one or more databases on which permissions related to personal digital assets are tracked and / or recorded. In some implementations, the blockchain can be implemented by a distributed computing platform ( Figure 1In some implementations, the distributed computing platform may be implemented by or may be the same as (one or more) client computing platforms 104 and / or servers (including, for example, one or more registry servers). The distributed computing platform may support virtual machines ( Figure 1 ). The distributed computing platform and / or virtual machine may form a runtime environment for smart contracts and / or other executable code. The distributed computing platform may include an electronic storage configured to store part or all of each blockchain. For example, the smart contract may be stored on one or more blockchains and / or another permanent 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.

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

[0025] Elements of a blockchain or another permanent registry may be grouped together in units called blocks. For example, a single block may include one or more digital assets and one or more transactions. For example, a single block may be linked to one or more other single blocks. Multiple single blocks may be linked or connected together to form a block structure and / or a block hierarchy, such as a block chain. A single block may include one or more digital assets, one or more transactions, smart contracts, and / or other information.

[0026] In some implementations, one or more permanent registries implemented by a registry server may be publicly accessible. For example, in some implementations, one or more databases may be accessed through a mobile application or a website. In some implementations, one or more permanent registries implemented by a registry server may be private and / or licensed. In some implementations, one or more permanent registries implemented by a registry server may only be appended. In some implementations, existing blocks of one or more permanent registries implemented by a registry server cannot be changed or deleted substantially unless multiple copies are changed. If multiple copies are stored on different computing platforms, such as in different geographic locations, this is unlikely to happen. The permanent registry may be replicated on multiple computing platforms, preferably in multiple different geographic locations. In addition, multiple individual blocks may be linked together in a tamper-proof manner, such as by using a hash chain and / or a digital signature. In particular, hash values ​​may be generated using one-way hash functions with fixed output lengths (these functions take variable length inputs) and may be virtually impossible (or at least computationally infeasible) to reverse. Therefore, a hash function may provide one-way encryption. As non-limiting examples, the hash function may be SHA-256, BLAKE2, SHAKE256, and / or another hash function. The contents of each block, transaction, and / or article may be digitally signed in a manner that proves integrity and / or prevents tampering, such as by providing authentication and non-repudiation.

[0027] The server(s) 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 indication receiving component 108, a wallet determining component 110, an acquisition management component 112, an interface presentation component 114, a rights management component 116, and / or other instruction components.

[0028] The indication receiving component 108 may be configured to receive an indication from a digital asset distribution platform that a user is requesting to obtain a collectible digital asset in a digital wallet associated with the user. The collectible digital asset may be a specific type of digital asset, or a digital asset from a specific distributor or creator of a user's collection. The digital asset distribution platform may facilitate users to purchase, sell, trade, lend, and / or other transactions related to digital assets. Acquiring collectible digital assets may include purchasing collectible digital assets, trading collectible digital assets, receiving collectible digital assets as a loan, receiving collectible digital assets as a gift, and / or otherwise acquiring collectible digital assets. Collectible digital assets may be associated with an entity. After obtaining the collectible digital asset, a user may receive and / or hold a set of permissions. The set of permissions may include trading collectible digital assets, lending collectible digital resources, viewing related entities, presenting related entities, selling collectible digital assets, sharing permissions of related entities, and / or other permissions. A digital wallet may correspond to an address tracked by (one or more) decentralized ledgers 117. The original holder of the set of permissions may be the creator of the related entity. In some implementations, the creator of the relevant entity may have minted the collectible digital asset so that the collectible digital asset is recorded on the (one or more) distributed ledgers 117. In some implementations, the creator of such a collectible digital asset may be recorded as its owner on the (one or more) distributed ledgers 117 until a subsequent acquisition. As used herein, the term "minting" or variations thereof may refer to the conduct, initiation, and / or execution of (one or more) processes, (one or more) transactions, (one or more) procedures, (one or more) operations, and / or (one or more) steps that lead to the instantiation of a given digital asset, including the establishment of ownership, the recording of ownership on the (one or more) distributed ledgers 117, the definition of the appearance of a given digital asset (e.g., a selected representative image, a default image), and the association of a given digital asset with a set of permissions in the electronic storage 120. In some implementations, minting a given digital asset may include building an executable program that instantiates the given digital asset. The executable program may be transmitted to (one or more) distributed computing platforms capable of executing the program. In some implementations, the distributed computing platform execution of the program may display the protocol on the distributed platform.

[0029] The wallet determination component 110 may be configured to determine whether a digital wallet associated with a user includes a dedicated digital asset. In some implementations, a dedicated digital asset may be a member of a dedicated collection. That is, a dedicated digital asset may be a specific type of digital asset. For example, a dedicated digital asset may be directly minted or established by a specific service using a dedicated smart contract. A dedicated smart contract may be stored on (one or more) centralized ledgers 117. A dedicated digital asset may require prior consent or otherwise represent an agreement between i) a given user holding a set of permissions associated with a related entity and ii) the original holder of the set of permissions, and / or require the completion of other prerequisites. In some implementations, a dedicated digital asset may be associated with an entity, i.e., a related entity. The related entity of a dedicated digital asset may be different from the related entity of a collectible digital asset. As a non-limiting example, the related entity of a dedicated digital asset may include a digital membership card, a key graphic, a wand graphic, and / or other entities. In some implementations, a dedicated digital asset established by a specific service using a dedicated smart contract may not have an owner recorded on (one or more) decentralized ledgers 117. In some implementations, a dedicated digital asset created by a specific service using a dedicated smart contract may record the specific service as the owner on the decentralized ledger(s) 117 .

[0030] Before receiving a dedicated digital asset in a given user's digital wallet, a given user may be required to agree to the agreement and / or complete other prerequisites. In some implementations, after receiving the user's agreement to the agreement, it may be allowed to obtain the dedicated digital asset from the digital asset distribution platform. As a non-limiting example, the agreement may specify that the related entity is available to the holder of the collectible digital asset, specific transfer and use restrictions, the holder does not own the related entity itself, and / or other information. The agreement may include a set of rights that specify such availability, transfer restrictions, and user restrictions. In some implementations, a dedicated smart contract for casting dedicated digital assets can be encoded to limit the transfer of dedicated digital assets between different users' digital wallets and / or limit the transfer 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 asset. The set of restrictions may limit the user from transferring, buying, selling, lending, selling, or otherwise handing over to another user. Therefore, the dedicated smart contract can ensure that users can only hold dedicated digital assets in their digital wallets after agreeing to the agreement, and unless the user agrees to the agreement, they may not hold dedicated digital assets.

[0031] In some implementations, the digital asset distribution platform may be associated with a known and existing decentralized ledger. Thus, the collectible digital assets referred to herein may be unique to the dedicated digital asset. That is, the collection smart contract that mints the collectible digital asset may be encoded to specify that the collectible digital asset is dependent on the dedicated digital asset. Thus, the set of rights associated with the collectible digital asset and its related entities may be dependent on the possession of the dedicated digital asset, rather than any other digital asset in circulation. The collection smart contract may be stored on (one or more) decentralized ledgers 117.

[0032] In some implementations, the digital asset distribution platform may be a new decentralized ledger. Thus, the dependency of the collectible digital asset on the dedicated digital asset may be built into all transactions recorded on the decentralized ledger. Thus, during the build process, the collectible digital asset does not need to be encoded as unique to the dedicated digital asset.

[0033] The acquisition management component 112 can be configured to send an authorization indication to the digital asset distribution platform after determining that the digital wallet does include the dedicated digital asset. The authorization indication can convey that the digital wallet is allowed to acquire the collectible digital asset. That is, as a non-limiting example, the user accepts the agreement, and therefore the digital wallet has the dedicated digital asset. Therefore, the user is allowed to purchase, sell, or otherwise acquire the collectible digital asset through the digital asset distribution platform.

[0034] The acquisition management component 112 can be configured to send a prevention instruction to the digital asset distribution platform to prevent the digital wallet from acquiring the collectible digital asset when it is determined that the digital wallet does not include the dedicated digital asset. The prevention instruction can convey that the digital wallet is not allowed to acquire the collectible digital asset. That is, the user has not accepted the agreement, and therefore the digital wallet does not include the dedicated digital asset.

[0035] In some implementations, after determining that the digital wallet does not include a dedicated digital asset, the interface presentation component 114 can be configured to implement presentation of an interface to the digital asset distribution platform. Presentation of the interface can facilitate the user to accept the agreement and / or complete other prerequisites. In some implementations, implementing presentation of the interface can include sending an interface indication to the digital asset distribution platform. The interface indication can request the digital asset distribution platform to provide an interface that enables the user to view the agreement, accept the agreement, and / or complete other prerequisites, and then obtain the dedicated digital asset in the digital wallet.

[0036] In some implementations, the acquisition management component 112 can be configured to receive an agreement indication from the digital asset distribution platform. The agreement indication can convey that the user accepted the agreement and / or completed other prerequisites through the interface and / or other platform, and then the digital wallet acquired the dedicated digital asset. Therefore, the digital wallet can be allowed to acquire the collectible digital asset.

[0037] In some implementations, a user may be allowed to acquire collectible digital assets through a digital asset distribution platform, but upon determining that a digital wallet does not include a dedicated digital asset, the set of permissions of the associated entity may be restricted and remain restricted until the user accepts the agreement and acquires the dedicated digital asset. Thus, in some implementations, the indication receiving component 108 may be configured to receive an indication from the digital asset distribution platform that a digital wallet associated with the user acquired a collectible digital asset. In some implementations, in response to receiving an indication that a digital wallet associated with the user acquired a collectible digital asset, the determination of whether the digital wallet includes a dedicated digital asset may be performed by the wallet determining component 110.

[0038] Upon determining that the digital wallet does not include a dedicated digital asset, the rights management component 116 can be configured to restrict the set of rights for entities related to the collectible digital asset and / or the collectible digital resource itself. Conversely, upon determining that the digital wallet does include a dedicated digital asset, the rights management component 116 can be configured to allow the set of rights for entities related to the collectible digital asset and / or the collectible digital resource itself. Allowing the set of rights can include generating and executing a set of instructions to record the user's address on (one or more) distributed ledgers 117, so that the user is identified as the holder of the set of rights.

[0039] In some implementations, some or all of the functions of components 108, 110, 112, 114, and / or 116 may be performed by (one or more) client computing platforms 104 (i.e., distributed computing platforms), which are configured by (one or more) smart contracts 124 to perform these functions. That is, (one or more) smart contracts 124 may be configured to receive an indication from a digital asset distribution platform that a user is requesting to obtain a collectible digital asset in a digital wallet associated with the user. In some implementations, some or all of the functions of (one or more) smart contracts 124 may be performed by components 108, 110, 112, 114, and / or 116.

[0040] (One or more) smart contracts 124 may be configured to determine whether one or more conditions associated with a digital wallet are satisfied. The conditions may include a first condition, a second condition, and / or other conditions. As a non-limiting example, a condition may require that a digital wallet be connected to an account of 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 member systems. In some implementations, the external member system may be the creator of a related entity of a collectible digital asset. The account may be associated with a user. In some implementations, when it is determined that the digital wallet is not connected to any account associated with the user of the external member system, (one or more) smart contracts 124 may be configured to enable the user to generate an account. In some implementations, the user may have the account, and (one or more) smart contracts 124 may be configured to enable the user to connect the digital wallet to the account. For example, (one or more) smart contracts 124 may implement presenting a user interface to an external member system for the user to enter information to log in to the external member system.

[0041] Another condition may require that the digital wallet include a dedicated digital asset. After determining that the digital wallet does not include a dedicated digital asset, (one or more) smart contracts 124 may be configured to perform the same or similar functions as the interface presentation component 114. That is, (one or more) smart contracts 124 may be configured to implement or initiate the presentation of an interface to the digital asset distribution platform. The presentation may facilitate the user to accept the agreement and / or complete other prerequisites, and then obtain the dedicated digital asset in the digital wallet through the digital asset distribution platform. Implementing the presentation of the interface may include (one or more) smart contracts 124 sending interface instructions to the digital asset distribution platform. Other conditions may be envisioned, such as casting other digital assets and holding these digital assets in the digital wallet, implementing other smart contracts by initiating transactions, and / or other conditions.

[0042] In some implementations, when the (one or more) smart contracts 124 determine that the one or more conditions are satisfied, the (one or more) smart contracts 124 may be configured to send an authorization instruction to the digital asset distribution platform to allow the digital wallet to obtain the collectible digital asset. In addition, when the (one or more) smart contracts 124 determine that the one or more conditions are not satisfied, the (one or more) smart contracts 124 may be configured to send a prevention instruction to the digital asset distribution platform to prevent the digital wallet from obtaining the collectible digital asset.

[0043] In some implementations, a user may be allowed to acquire collectible digital assets through a digital asset distribution platform, but when it is determined that one or more conditions are not met, the set of permissions of the associated entity may be restricted. Therefore, in some implementations, (one or more) smart contracts 124 may be configured to receive an indication that a digital wallet associated with a user has acquired a collectible digital asset. In some implementations, (one or more) smart contracts 124 may be configured to perform the same or similar functions as the rights management component 116. That is, when (one or more) smart contracts 124 determine that one or more conditions are not met, (one or more) smart contracts 124 may be configured to restrict the set of permissions of the associated entity. In addition, when (one or more) smart contracts 124 determine that one or more conditions are met, (one or more) smart contracts 124 may be configured to allow the set of permissions for collectible digital assets.

[0044] In some implementations, (one or more) smart contracts 124 may be configured to determine whether an account satisfies additional conditions within an external member system, thereby determining whether the user satisfies these conditions. The conditions may include these additional conditions. For example, the additional conditions may include watching all movies in a collection, watching an entire television series, completing all levels of a game, and / or other additional conditions. When it is determined that the additional conditions are met, the associated entities of the collectible digital assets held by the user's digital wallet may be modified. For example, modifications to the associated entities may include revealing new details in a movie poster graphic, unlocking new features in a game, adding an extended scene, sending a new clip of a physical object to the user, and / or other modifications to the associated entities of the collectible digital assets. When it is determined that the additional conditions are not met, the associated entities of the collectible digital assets may not be modified, or a portion of the associated entity may be hidden.

[0045] In some implementations, the wallet determination component 110, the (one or more) smart contracts 124, and / or other components may be configured to determine the satisfaction of one or more conditions to enable a user or a digital wallet associated with a user to add functionality. That is, in some implementations, an authorization indication may convey that a digital wallet is permitted to participate in a particular transaction, mint digital assets, and / or that a user associated with a digital wallet is permitted to perform a particular action and / or hold a particular permission in addition to obtaining permission to obtain collectible digital assets. Thus, upon determining that one or more conditions are satisfied, the authorization indication may additionally be sent to one or more other platforms. For example, satisfaction of one or more conditions may result in an authorization indication being sent to an admission platform that allows or sells admission to an event and / or location, thereby allowing the user to go to a set of events and / or a particular amusement park.

[0046] In some implementations, server(s) 102, client computing platform(s) 104, and / or external resources 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 should be understood that this is not intended to be limiting, and the scope of the present invention includes implementations in which server(s) 102, client computing platform(s) 104, and / or external resources 118 may be operably linked via some other communication medium.

[0047] 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 a given client computing platform 104 to interact with the system 100 and / or external resources 118, and / or to provide other functionality attributed herein to the client computing platform(s) 104. As non-limiting examples, 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 smart phone, a gaming console, and / or other computing platforms.

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

[0049] Server(s) 102 may include electronic storage 120, one or more processors 122, and / or other components. Server(s) 102 may include communication links or ports to enable information exchange with network 124 and / or other computing platforms. Figure 1 The illustration of the server(s) 102 in FIG. 1 is not intended to be limiting. The server(s) 102 may include multiple hardware, software, and / or firmware components operating together to provide the functionality attributed herein to the server(s) 102. For example, the server(s) 102 may be implemented as a computing platform cloud operating together with the server(s) 102.

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

[0051] Processor(s) 122 may be configured to provide information processing capabilities in server(s) 102. Thus, processor(s) 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. Figure 1108, 110, 112, 114, and / or 116, and / or other components. The processors 122 may be configured to execute components 108, 110, 112, 114, and / or 116 and / or other components by: software; hardware; firmware; some combination of software, hardware, and / or firmware; and / or other mechanisms for configuring the processing capabilities on the processors 122. As used herein, the term "component" may refer to any component or set of components that perform the functions attributed to the component. This may include one or more physical processors, processor-readable instructions, circuits, hardware, storage media, or any other components during the execution of processor-readable instructions.

[0052] It should be understood that although Figure 1 108, 110, 112, 114, and / or 116 are implemented within a single processing unit, but in implementations where the processor(s) 122 include multiple processing units, one or more of the components 108, 110, 112, 114, and / or 116 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, 112, 114, and / or 116 described below is for illustrative purposes and is not intended to be limiting, as any of the components 108, 110, 112, 114, and / or 116 may provide more or less functionality than described. For example, one or more of the components 108, 110, 112, 114, and / or 116 may be removed, and some or all of their functionality may be provided by other components in the components 108, 110, 112, 114, and / or 116. As another example, processor(s) 122 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108 , 110 , 112 , 114 , and / or 116 .

[0053] Figure 3A The system 100 (with Figure 1306). The system 100 may receive an indication 302 from a digital asset distribution platform 300 that a user associated with a digital wallet 304 is requesting to obtain (one or more) collectible digital assets 306. The digital asset distribution platform 300 may distribute (e.g., sell, facilitate the sale of) (one or more) collectible digital assets 306, and distribute a dedicated digital asset 308. The system 100 may determine that the digital wallet 304 includes (one or more) other digital assets 326 and does not include one of the dedicated digital assets 308 indicating consent to an agreement 314. In response, the system 100 may send a prevention indication 310 to the digital asset distribution platform 300 to prevent the digital wallet 304, thereby preventing the user from obtaining (one or more) collectible digital assets 306. In addition, the system 100 may cause a user interface 312 of the digital asset distribution platform 300 to be presented to the user (e.g., via a client computing platform, such as a desktop computer, not shown). The user interface 312 may present an agreement 314 and enable the user to agree to the agreement 314. After the user agrees, an agreement indication 316 indicating the user's agreement may be sent to the system 100.

[0054] As Figure 3A Continue, Figure 3B shows that the protocol indication 316 is sent to Figure 3A After the system in Figure 3A The same digital wallet 304 in FIG. 1 includes a dedicated digital asset 308a. The dedicated digital asset 308a may be Figure 3A Thus, in the system 100 (with Figure 3A When receiving an indication 318 from the digital asset distribution platform 300 that a user is requesting to obtain (one or more) collectible digital assets 306 ), the system 100 may send an authorization indication 320 allowing the user to obtain (one or more) collectible digital assets 306 .

[0055] Figure 4 The system 100 (with Figure 1 same as in the above) from the digital asset distribution platform 300 (with Figure 3A-3B 306) receives an indication 322 that a user associated with a digital wallet 304 is requesting to obtain (one or more) collectible digital assets 306. The system 100 can determine whether one or more conditions are satisfied, such as whether the digital wallet 324 associated with the user is connected to an external member system 350. Due to the connection with the external member system 350, the system 100 can send an authorization indication 326 indicating that the digital wallet 324 is allowed to obtain (one or more) collectible digital assets 306.

[0056] Figure 5 The system 100 (with Figure 1same as in the above) from the digital asset distribution platform 300 (with Figure 3A-3B and Figure 4 Receive an acquisition indication 328 that a digital wallet 334 associated with a user has acquired a collectible digital asset 306b, i.e., one of the collectible digital assets 306b. The system 100 may determine whether one or more conditions are satisfied, such as whether the digital wallet 334 is connected to an external member system 350. Since there is no connection to the external member system 350, the system 100 may limit a set of permissions 330 of the entity 332 associated with the collectible digital asset 306b. The entity 332 and the set of permissions 330 may be stored in the electronic storage 120 (with Figure 1 Same as in ().

[0057] Figure 2 A method 200 for managing digital asset functionality based on satisfaction of standards according to one or more implementations is shown. The operations of the method 200 presented below are intended to be illustrative. In some implementations, the method 200 may be implemented with one or more additional operations not described and / or without one or more of the operations discussed. In addition, Figure 2 The order in which the operations of method 200 are illustrated and described below is not intended to be limiting.

[0058] In some implementations, the method 200 may be implemented in one or more processing devices (e.g., digital processors, analog processors, digital circuits designed to process information, analog circuits designed to process information, state machines, and / or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices that perform some or all of the operations of the method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured by hardware, firmware, and / or software that are specifically designed to perform one or more operations of the method 200.

[0059] Operation 202 may include receiving an indication from a digital asset distribution platform that a user is requesting to obtain a collectible digital asset in a digital wallet associated with the user. The collectible digital asset may be associated with a related entity. The digital wallet may indicate 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 (one or more) smart contracts 124.

[0060] Operation 204 may include determining whether one or more conditions associated with the digital wallet are satisfied. According to one or more implementations, operation 204 may be performed by (one or more) smart contracts 124.

[0061] Operation 206 may include sending an authorization indication to the digital asset distribution platform to allow the digital wallet to obtain the collectible digital asset when it is determined that the one or more conditions are satisfied. According to one or more implementations, operation 206 may be performed by (one or more) smart contracts 124.

[0062] Operation 208 may include sending a prevention instruction to the digital asset distribution platform to prevent the digital wallet from acquiring the collectible digital asset when it is determined that the one or more conditions are not satisfied. According to one or more implementations, operation 208 may be performed by (one or more) smart contracts 124.

[0063] Although the present technology is described in detail based on what is currently considered to be the most practical and preferred implementations for the purpose of illustration, it should be understood that these details are only for that purpose and that the technology is not limited to the disclosed implementations, but rather, the technology is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.

Claims

1. A system configured to manage digital asset functionality based on satisfaction of a standard, the system comprising: One or more processors configured by machine-readable instructions to: receiving an indication from a digital asset distribution platform that a digital wallet associated with a user is requesting to obtain a collectible digital asset in a digital wallet associated with the user, wherein the collectible digital asset is associated with an entity, wherein the digital wallet corresponds to an address tracked by a decentralized ledger; determining whether one or more conditions associated with the digital wallet are satisfied; Upon determining that the one or more conditions are satisfied, sending an authorization indication to the digital asset distribution platform allowing the digital wallet to acquire the collectible digital asset; Upon determining that the one or more conditions are not satisfied, a prevention instruction is sent to the digital asset distribution platform to prevent the digital wallet from acquiring the collectible digital asset.

2. The system according to claim 1, wherein: Acquiring the collectible digital asset includes a set of permissions, including permissions to buy and sell the collectible digital asset, lend the collectible digital asset, view related entities, present the related entities, and / or sell the collectible digital asset.

3. The system according to claim 1, wherein: The one or more conditions include a first condition and a second condition, wherein the first condition is that the digital wallet includes dedicated digital assets, wherein the second condition is that the digital wallet is linked to an account of an external member system, wherein the account is associated with the user, and wherein the one or more processors are also configured by the machine-readable instructions to enable the user to generate the account and / or link the digital wallet to the account upon determining that the digital wallet is not linked to any account of the external member system associated with the user.

4. The system according to claim 3, wherein: The dedicated digital asset represents an agreement to hold a set of rights associated with the relevant entity, the agreement being an agreement between a given user and an original holder of the set of rights.

5. The system according to claim 4, wherein: Upon determining that the digital wallet does not include the dedicated digital asset, the one or more processors are further configured by the machine-readable instructions to: Presenting an interface to the digital asset distribution platform is achieved to facilitate the user to accept the agreement and then obtain the dedicated digital asset through the digital wallet.

6. The system according to claim 4, wherein: The one or more processors are further configured by the machine-readable instructions to: An agreement indication is received from the digital asset distribution platform that the user accepts the agreement and that the dedicated digital asset is present in the digital wallet.

7. A system configured to manage digital asset functionality based on satisfaction of a standard, the system comprising: One or more processors configured by machine-readable instructions to: receiving, from a digital asset distribution platform, an indication that a digital wallet associated with a user has acquired a collectible digital asset, wherein the collectible digital asset is associated with an entity, wherein the digital wallet corresponds to an address tracked by a decentralized ledger; In response to the indication, determining whether one or more conditions associated with the digital wallet are satisfied; Upon determining that the one or more conditions are not satisfied, restricting a set of permissions of the related entity; and Upon determining that the one or more conditions are satisfied, the set of permissions for the related entity is allowed.

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

9. A method for managing digital asset functionality based on satisfaction of standards, the method comprising: receiving, from a digital asset distribution platform, an indication that a user is requesting to obtain a collectible digital asset in a digital wallet associated with the user, wherein the collectible digital asset is associated with a related entity, wherein the digital wallet corresponds to an address tracked by a decentralized ledger; determining whether one or more conditions associated with the digital wallet are satisfied; Upon determining that the one or more conditions are satisfied, sending an authorization indication to the digital asset distribution platform allowing the digital wallet to acquire the collectible digital asset; and Upon determining that the one or more conditions are not satisfied, a prevention instruction is sent to the digital asset distribution platform to prevent the digital wallet from acquiring the collectible digital asset.

10. The method according to claim 9, wherein: Acquiring the collectible digital asset includes a set of permissions, including permissions to buy and sell the collectible digital asset, lend the collectible digital asset, view the related entities, present the related entities, and / or sell the collectible digital asset.

11. The method according to claim 9, wherein: The one or more conditions include a first condition and a second condition, wherein the first condition is that the digital wallet includes a dedicated digital asset, wherein the second condition is that the digital wallet is linked to an account of an external member system, wherein the account is associated with the user, and the method further includes: Upon determining that the digital wallet is not linked to any account of the external member system associated with the user, enabling the user to generate the account and / or link the digital wallet to the account.

12. The method according to claim 11, wherein: The dedicated digital asset represents an agreement to hold a set of rights associated with the relevant entity, the agreement being an agreement between a given user and an original holder of the set of rights.

13. The method according to claim 12, wherein: When it is determined that the digital wallet does not include the dedicated digital asset, the method further includes: Presenting an interface to the digital asset distribution platform is achieved to facilitate the user to accept the agreement, and then the digital wallet obtains the dedicated digital asset through the digital asset distribution platform.

14. The method according to claim 12, further comprising: An agreement indication is received from the digital asset distribution platform that the user accepts the agreement and that the digital wallet does not include the dedicated digital asset.

15. A method for managing digital asset functionality based on satisfaction of standards, the method comprising: receiving, from a digital asset distribution platform, an indication that a digital wallet associated with a user has acquired a collectible digital asset, wherein the collectible digital asset is associated with a related entity, wherein the digital wallet corresponds to an address tracked by a decentralized ledger; In response to the indication, determining whether one or more conditions associated with the digital wallet are satisfied; Upon determining that the one or more conditions are not satisfied, restricting a set of permissions of the related entity; and Upon determining that the one or more conditions are satisfied, the set of permissions for the related entity is allowed.

Images