Patent ID: 12186668

DETAILED DESCRIPTION

FIG.1illustrates a system100configured to provide ledger-specific utilities for unique digital articles and other digital assets that are not fungible in an online gaming platform105, in accordance with one or more implementations. As used herein, the term “unique digital article” may refer to digital articles that are uniquely identified and/or uniquely identifiable, e.g., by an identifier or by identifying information. For example, in some implementations, an identifier or identifying information may include or be based on a combination of different types of information, including but not limited to information regarding the type of a digital article, a serial number or other numerical identifier of the digital article, and/or other types of information. As used herein, ownership of unique digital articles may be tracked, recorded, and/or otherwise registered on one or more decentralized ledgers. As such, a unique digital article may be a ledger-tracked unique digital article.

Individual unique digital articles may be associated and/or correlated with another entity (which may be referred to as a “correlated entity”) by virtue of technology provided and/or supported by the one or more decentralized ledgers on which the ownership of the individual unique digital articles is tracked (including but not limited to smart contracts and/or other executable code on the one or more decentralized ledgers). Accordingly, ownership of a unique digital article may correlate to the provision of one or more rights with respect to the correlated entity (e.g., control and/or other rights). Transactions involving a unique digital article recorded on a decentralized ledger may correlate to certain transactions (or modifications) of the correlated entity, and/or vice versa.

In some implementations, correlated entities may be (or include) virtual items configured to be used within online-gaming platform105(such as, for example, a user-controllable in-game virtual character that is usable within an instance of a game within online gaming platform105). Other types and/or combinations of correlated entities are envisioned within the scope of this disclosure, including but not limited to physical and/or virtual objects, items, rights, memberships, permissions, etc. The use of the singular “entity” or “correlated entity” is not intended to be limiting, as multiple different objects, items, rights, memberships, permissions, etc. may be correlated to a single unique digital article. By way of non-limiting example, a correlated entity may be an art work, a ticket to an event, a subscription to certain media content, a bundle of rights related to captured audio and/or video information, rights to distribution gains, and so forth. As used herein, the term “non-fungible token” or “NFT” may be used to refer to a combination of a particular unique digital article and a particular correlated entity that is correlated to the particular unique digital article.

As used herein, the term “utility” refers to different types of usage provided to users123by unique digital articles (and other digital assets that are not fungible) in instances of games, or within online gaming platform105. As brief examples, these types of usage may include displaying the unique digital article, using the unique digital article to play in an instance of a game, receiving distribution gains due to owning distribution rights, and/or other types of usage, as explained in greater detail elsewhere in this disclosure. For example, these type of usage may be different for or on different decentralized ledgers (or blockchains), hence the term “ledger-specific”. For example, the same unique digital article may have a first utility while recorded on a first decentralized ledger, but not while recorded on a second decentralized ledger. Conversely, the same unique digital article may have a second utility while recorded on the second decentralized ledger, but not while recorded on first decentralized ledger.

System100may include one or more online gaming platforms105, decentralized ledger server(s)111, administration servers115, one or more client computing platform(s)104, user interfaces125, servers102, one or more external resources138, and/or other components. Users123(also referred to as players) may include one or more of a first user, a second user, a third user, a fourth user, an administrative user, and/or other users. Users123may include players who play and/or otherwise interact on online gaming platform105. As used in descriptions herein, any use of the term “user” may refer to user(s)123. Electronic storage130aand electronic storage130bmay be similar to electronic storage130as described elsewhere in this disclosure, though included in administration servers115and decentralized ledger servers111, respectively, as depicted inFIG.1.

Instances of games may be executed within one or more online gaming platforms105. As used herein, online gaming platform105may refer to either an individual game (e.g., an interactive online game), a type of gaming console and its ecosystem, and/or both. Online gaming platform105may be configured to host (and/or execute instances of) the one or more (online) games. Online gaming platform105may be operated, hosted, and/or owned by one or more stakeholders of online gaming platform105. For example, a platform operator (and/or another stakeholder) may sell in-game digital assets (e.g., characters, weapons, resources, etc.) to users123of online gaming platform105.

Referring to the game and to online gaming platform105, in some implementations, individual players may own individual virtual items, and exchange these items with (or to) other individual players. As used herein, exchanges refer to individual players winning, losing, auctioning, selling, purchasing, trading, bartering, wagering, staking, and/or otherwise exchanging digital assets (directly, without a store or store interface under control of online gaming platform105) to other individual players or with other individual players (including exchanging virtual items and/or other assets through player-to-player challenges). Due to an exchange, ownership rights of a digital asset may transition from an original owner to a new owner (even if there may, in some implementations, be one or more intermediary and/or temporary owners during the process of performing the exchange). In some implementations, digital assets may be associated with other rights than ownership rights, such as, by way of non-limiting example, distribution rights.

In some implementations, distribution rights of digital assets may reflect rights held by the individual ones of the users to receive certain distributions of benefits upon exchanges involving particular digital assets. That is, the individual users may own/hold rights to particular digital assets that guarantee them benefits upon (future) exchanges involving those digital assets regardless of whether the individual users owns/hold the ownership rights for those digital assets. In some implementations, the distribution gains may result from a particular action or activity (such as, e.g., a sale of a particular digital asset), e.g., within the online gaming platform105, of a particular digital asset. As used herein, a distribution gain resulting from a particular action or activity may include one or more of a portion of the proceeds of the particular action or activity, a fee related to the particular action or activity, a minimum payment triggered by the occurrence of the particular action or activity (or a set of particular actions or activities), and/or another arrangement for payment and/or compensation, including but not limited to combinations of fixed fees, minimum fees, percentages of sales, percentages of profits, and/or other arrangements. The term “portion” does not imply or require a percentage or ratio, but rather is intended to signify that beneficiaries (i.e., the users that hold the distribution rights) may receive something of value and/or use. The distribution gains may include one or more virtual currencies such as virtual tokens, virtual stars, virtual points, virtual real-world currencies (e.g., US Dollars), and/or other gains that are based on the particular digital assets.

In some implementations, the digital assets may include and/or be virtual items that are not fungible and may be usable within an online gaming platform105. In some implementations, the digital assets may represent (three-dimensional) in-game user-controllable characters that can interact with other (in-game) virtual items within online gaming platform105. By way of non-limiting example, digital assets may represent virtual items. In some implementations, virtual items may include one or more of weapons, toys, characters, abilities, skills, tools, pets, clothing, vehicles, game levels, missions, assignments, chapters, tasks, mini-games, restricted areas within a virtual space, restricted modes of gameplay, access rights within an online game, and/or other virtual items. In some implementations, virtual items may refer to any item or object within online gaming platform105for which a user may use, own, sell, trade, destroy, and/or otherwise effectuate a change of ownership (including exchanging virtual items and/or other assets through challenges). As used herein, a digital asset is fungible if it is functionally and/or physically indistinguishable from another digital asset. For example, a payment token such as a Bitcoin is a fungible digital asset. A digital asset may be non-fungible if it is unique, or one-of-a-kind. For example, a specific individual CryptoKitty™ may be a non-fungible digital asset. A digital asset may be semi-fungible if there is a set of a limited number of similar but distinguishable digital assets. For example, a limited-edition Blanko™ or another in-game character may be a semi-fungible digital asset. For example, one of a limited number of 2-dimensional or 3-dimensional in-game virtual items may be a semi-fungible digital asset. For example, a digital ticket to a show, concert, exhibition, and/or other event may be a semi-fungible digital asset. For example, a piece of art or jewelry (e.g., as a virtual item or as representing a physical item) may be a semi-fungible digital asset. As used herein, semi-fungible digital assets are considered as “not fungible” or non-fungible digital assets. In some implementations, digital assets may be usable within one or more games.

Decentralized ledger server(s)111(e.g., decentralized ledger server111a, decentralized ledger server111b, and so forth) may be used to implement one or more decentralized ledgers, including but not limited to blockchain117a, blockchain117b(partially visible inFIG.1), and so forth. In some implementations, blockchain117aand blockchain117bmay be maintained by distributed computing platforms (not shown inFIG.1). In some implementations, a distributed computing platform may be implemented by a set of client computing platforms and/or servers (including, for example, one or more decentralized ledger servers111). The distributed computing platform may support a virtual machine (not shown inFIG.1). The distributed computing platform and/or the virtual machine may form a runtime environment for smart contracts and/or other executable code. A distributed computing platform may include electronic storage configured to store part or all of blockchain117a. The smart contracts may be stored on blockchain117a, blockchain117b, and/or another decentralized ledger. In some implementations, the distributed computing platform may be the 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 decentralized virtual machine.

In some implementations, at least one of the decentralized ledgers implemented by decentralized ledger servers111is a private permissioned decentralized ledger. The private permissioned decentralized ledger may be configured to record information. The recorded information may pertain to unique digital articles that are associated with in-game user-controllable characters that are configured to be used in the instance of the game. The recorded information may include ownership of the unique digital articles. Implementing the in-game actions in the instance of the game may include, for at least some of the in-game actions implemented in the instance of the game, effectuating modifications to the recorded information pertaining to the unique digital article. For example, ownership rights and/or other rights may be modified. In some implementations, a unique digital article may be removed from one decentralized ledger and added or recorded on another decentralized ledger. In some implementations, at least one of the decentralized ledgers implemented by decentralized ledger servers111is a public decentralized ledger. The public decentralized ledger may be configured to be part of either EOSIO mainnet, Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 that is configured to perform transactions of Ether (ETH) between accounts, or a derivative of EOSIO that is configured to perform transactions of EOS between different accounts.

Elements of blockchain117aor another decentralized ledger may be grouped together in units that are referred to as blocks. For example, an individual block may include one or more assets and one or more transactions. For example, an individual block may be linked to one or more other individual blocks. Individual blocks may be linked or chained together to form a structure of blocks and/or a hierarchy of blocks, such as, e.g., a chain of blocks. An individual block may include one or more assets, one or more transactions, and/or other information.

As depicted inFIG.1, decentralized ledger server111amay include one or more of electronic storage130b, processor(s)132b, machine-readable instructions106b, (node of) blockchain117a, and/or other components. Machine-readable instructions106bmay include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of transaction component134, receipt component136, and/or other instruction components. In some implementations, an individual decentralized ledger server may be dedicated to a particular node of a decentralized ledger. Typically, different nodes are included in (or implemented by, or hosted by) different servers or different computer systems to increase the safety and security of transactions on a decentralized ledger. The consensus protocol used for a particular decentralized ledger will be harder to falsify or circumvent when the different nodes are in different geographical locations, on different types of computing platforms, and/or otherwise distributed and diverse. As depicted inFIG.1, blockchain117amay include a unique digital article15(by way of non-limiting example, unique digital article15may be associated with a user-controllable in-game character, as depicted, and unique digital article15may have been recorded on blockchain117a, as depicted). Decentralized ledger server111bmay include similar components as decentralized ledger server111a, including but not limited to blockchain117band/or other components.

In some implementations, one or more decentralized ledgers implemented by decentralized ledger servers111may be publicly accessible. In some implementations, one or more decentralized ledgers implemented by decentralized ledger servers111may be private and/or permissioned. In some implementations, one or more decentralized ledgers implemented by decentralized ledger servers111may be append-only. In some implementations, existing blocks of one or more decentralized ledgers implemented by decentralized ledger servers111can substantially not be altered or deleted, unless multiple copies are altered. This is unlikely to happen provided that the multiple copies stored on different computing platforms, e.g., in different geographical locations. Decentralized ledgers may be replicated on multiple computing platforms, preferably in multiple different geographical locations. Additionally, individual blocks may be linked together in a manner that prevents tampering, such as, e.g., using a hash chain and/or digital signatures. In particular, hash values may be generated using fixed-output-length one-way hashing functions that take variable-length input, and may be effectively impossible (or, at least, computationally infeasible) to reverse. As such, a hashing function may provide one-way encryption. By way of non-limiting example, the hashing function may be SHA-256, BLAKE2, SHAKE256, and/or another hashing function. Contents of individual blocks, transactions, and/or assets may be digitally signed in a manner that proves integrity and/or prevents tampering, e.g., by providing authentication, as well as repudiation.

Server(s)102may be configured to communicate with one or more client computing platforms104according to a client/server architecture and/or other architectures. Client computing platform(s)104may be configured to communicate with other client computing platforms via server(s)102and/or according to a peer-to-peer architecture and/or other architectures. Users may access system100via client computing platform(s)104. In some implementations, system100and/or decentralized ledger server(s)111may be configured to communicate with one or more of online gaming platform(s)105, users123, and/or other entities and/or components, e.g., through one or more networks13.

Server(s)102may include electronic storage130, processor(s)132, machine-readable instructions106, and/or other components. Server(s)102may be configured by machine-readable instructions106. Machine-readable instructions106may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of a game component108, an interaction component110, an account component112, a recording component114, a grouping component116, a performance component118, a ledger-analysis component120, a notification component122, a distribution component124, an adjustment component126, a ledger component128, a population component129, a reward component131, a presentation component133, a transaction component134, a receipt component136, an input component135, a communication component137, and/or other instruction components. Processor(s)132aand processor(s)132bmay be similar to processor(s)132as described elsewhere in this disclosure, though included administration servers115and decentralized ledger servers111, respectively, as depicted inFIG.1. Machine-readable instructions106aand machine-readable instructions106bmay be similar to machine-readable instructions106as described elsewhere in this disclosure, though included in administration servers115and decentralized ledger servers111, respectively, as depicted inFIG.1.

Game component108is configured to execute, via online gaming platform105, one or more instances of one or more games. An instance of a game may facilitate presentation of the game to users123. For example, the instance of the game may be an online game executed with online gaming platform105. Game component108may be configured to implement in-game actions in the instance of the game, e.g., in response to action requests for the in-game actions by the users. In some implementations, game component108may be arranged, organized, and/or otherwise included in online gaming platform105. As used herein, the term “game” may refer to one or more games within online gaming platform105. In some implementations, the game may be provided via a virtual space, and may include a plurality of resource types and/or maps.

The presentation of the game may be based on the views of the game that are determined during execution of the game, e.g., as based on instructions and/or other input from users. In some implementations, the view may be communicated (e.g., by streaming, via object/position data, and/or other information) from online gaming platform105, decentralized ledger server(s)111, and/or other sources to client computing platforms104for presentation to users123. The view determined and transmitted to a given client computing platform104may correspond to a location in the virtual space (e.g., the location from which the view is taken, the location the view depicts, and/or other locations), a zoom ratio, a dimensionality of objects, a point-of-view, and/or view parameters. In some implementations, one or more view parameters may be selectable by a user.

The instance of the game may include a simulated space that is accessible by users123by clients (e.g., client computing platforms104) that present the views of the virtual space to a user. The simulated space may have a topography, express ongoing real-time interaction by one or more users123, and/or include one or more objects positioned within the topography that are capable of locomotion and/or movement within the topography. In some implementations, the topography may be a 2-dimensional topography. In some implementations, the topography may be a 3-dimensional topography. The topography may include dimensions of the simulated space, and/or surface features of a surface or objects that are native to the simulated space. In some implementations, the topography may include a surface (e.g., a ground surface) that runs through at least a substantial section of the simulated space. In some implementations, the topography may describe a volume with one or more bodies positioned therein. The instance executed by the computer components may be synchronous, asynchronous, and/or semi-synchronous.

Within the instance of the game, users123may control characters, objects, simulated physical phenomena, and/or other elements within the virtual space to interact with the virtual space and/or each other. The user characters may include avatars. As used herein, the term “user character” may refer to an object or group of objects present in the virtual space, that correspond(s) to an individual user. A particular user character may be controlled by the particular user with which it is associated. Such user characters may be referred to as user-controlled characters. User-controlled element(s) may move through and interact with the virtual space (e.g., non-user characters in the virtual space, other objects in the virtual space, etc.). In some implementations, user-controlled characters may be capable of locomotion within the topography of the simulated space that is included in the instance of the game. In some implementations, user-controlled elements controlled by and/or associated with a given user may be created and/or customized by the given user. Individual users123may have or control an “inventory” of virtual goods and currency (e.g., resources of the plurality of resource types) that the individual user can use (e.g., by manipulation of a user character and/or other user-controlled elements) and/or other items, to perform in-game actions within the virtual space. By way of non-limiting illustration, users123may include the first user and the second user that interact with online gaming platform105. The first user and the second user may control digital assets (e.g., characters) in a game hosted by online gaming platform105. In some implementations, account inventories may be managed (at least in part) using blockchain117a. For example, ownership rights (and/or other types of rights) of individual virtual items included in an individual account inventory may be recorded on blockchain117a. In some implementations, individual account inventories may correspond to individual smart contracts stored on blockchain117a.

Interaction component110may be configured to enable, facilitate, and/or implement in-game actions by users123in instances of games. In some implementations, interaction component110may be configured to operate in response to instructions and/or action requests by users123. For example, one or more users may interact within online gaming platform105to build, create, gather, find, combine, and/or otherwise generate content (i.e., user-generated content). In some implementations, operations may be accomplished by interaction component110through user interfaces125. In particular, operations pertaining to a particular user may be accomplished through a particular user interface125of a particular client computing platform104, where the particular client computing platform104is associated with the particular user. In other words, the particular user may interact with an instance of a game through interaction component110and/or the particular user interface125. For example, interaction component110may be configured to receive indications of acceptance from users, through associated client computing platforms104(or, e.g., a particular user interface125of a particular client computing platform104). For example, an acceptance may accept a particular offer to partake in an activity or agreement. In some implementations, interaction component110may be configured to receive indications of agreements from users, through associated client computing platforms104(or, e.g., a particular user interface125of a particular client computing platform104).

In some implementations, interaction component110may be configured to facilitate interaction of users123with system100. In some implementations, interaction component110may be configured to facilitate interaction by users123through user interfaces125. For example, a particular user may be associated with a particular client computing platform104, which may include a particular user interface125. In other words, an individual user interface may be user-specific and/or specific to a particular client computing platform. In some implementations, interaction component110may facilitate entry and/or selection through (presentation of) one or more user interfaces125(such as, by way of non-limiting example, any of the interfaces described in this disclosure).

Account component112is configured to manage user accounts. User accounts may be associated with users123. User accounts may include and/or be associated with account inventories of virtual items. For example, the user accounts may include a first user account associated with a first user, and so forth. For example, the first user account may include a first account inventory of one or more virtual items, and so forth. Individual users may control one or more virtual items in their individual account inventories. In some implementations, the first account inventory includes a first unique digital article. The first unique digital article may be associated with a first in-game user-controllable character configured to be used (e.g., played with) in the instance of the game.

Recording component114is configured to record assets on decentralized ledgers. In some implementations, recording component114may record ownership of assets. In some implementations, recording component114may be configured to receive requests to perform a recordation. For example, recording component114may receive, on behalf of a first user, a recordation request to record ownership of a first unique digital article on a first decentralized ledger (such as, e.g., blockchain117a). In some implementations, recording component114may receive such requests from online gaming platform105and/or other components of system100. For example, a particular request to record a particular unique digital article may correspond to the issuance and/or creation of that particular unique digital article. When a unique digital article or other digital asset that is not fungible is issued and/or created, recording component114may record its ownership on a particular decentralized ledger.

Grouping component116may be configured to receive action request to use unique digital articles and other digital assets that are not fungible in particular manners in the instance of the game. The particular manners may include a first type of usage, a second type of usage, a third type of usage, and/or other types of usage. For example, a unique digital article may be used in a first unique digital article type of usage. Grouping component116may be configured to group and/or select under which type of usage a requested manner of usage falls. For example, a first action request may be to use a first unique digital article in a first manner of usage (or more specifically, a first requested manner of usage). For example, a second action request may be to use a second unique digital article in a second manner of usage (or more specifically, a second requested manner of usage), and so forth. Grouping component may group a requested manner of usage in a particular type of usage (e.g., the first type, the second type, the third type, etc.). In some implementations, different types of usage may be mutually exclusive, such that a single requested manner of usage cannot be grouped under more than one type of usage. In some implementations, the different types of usage may include passive manners of usage including display of unique digital articles or associated in-game user-controllable characters (e.g., in account inventories). In some implementations, the different types of usage may include active manners of usage including interactive gameplay in the instance of the game using unique digital articles or associated in-game user-controllable characters as being controlled by users123. In some implementations, the different types of usage may include different types of exchanges, including but not limited to selling a unique digital article. One or more types of exchanges may be considered passive manners of usage (e.g., selling a unique digital article), whereas other types of exchanges may be considered active manners of usage (e.g., using a unique digital article in a player-to-player challenge). Grouping different types of usage (including different types of exchange) in a first type, a second type, a third type, and so forth may be configurable and/or modifiable by an administrative user.

In some implementations, the different types of usage may include receiving one or more participation rewards or attendance awards for either a particular unique digital article participating in an online event or attending an online event (e.g., during a particular time-limited duration). Alternatively, and/or simultaneously, the different types of usage may include receiving one or more participation rewards or attendance awards for a particular user (e.g., who owns the particular unique digital article) participating in a real-world event or attending a real-world event (e.g., during a particular time-limited duration). In some implementations, the different types of usage may include receiving distribution gains by virtue of owning distribution rights for one or more particular unique digital articles. In some implementations, grouping component116may receive a particular action request to use a particular unique digital article in a particular manner of usage in the instance of the game due to (or effectuated by, or caused by) a user attempting to use the particular unique digital article in the particular manner. In some implementations, grouping component116may receive a particular action request to use a particular unique digital article in a particular manner of usage in the instance of the game caused by a user attempting to use the particular unique digital article in the particular manner. In some implementations, receipt of a particular action request to use a particular unique digital article in a particular manner of usage in the instance of the game may be effectuated by a user using or attempting to use the particular unique digital article in the particular manner. For example, grouping component116may receive such action requests from online gaming platform105and/or other components of system100.

Performance component118may be configured to permit and/or perform requested manners of usage of unique digital articles. In some implementations, permission to use a particular unique digital article in accordance with a particular action request may be granted responsive to the particular manner of usage (as requested in the particular action request) being grouped (e.g., by grouping component116) in a particular type of (unique digital article) usage. For example, permission may be granted for requested manners of usage that are grouped in the first type of usage, but not the second type of usage. For example, requested manners of usage may be performed if grouped in the first type of usage, but not the second type of usage. In some implementations, performance component118may permit and/or perform some types of usage (e.g., first and third type of usage), but not other types of usage (e.g., second and fourth type of usage). In some implementations, permission and/or performance may be prevented for certain types of usage (e.g., second and fourth type of usage), unless the pertinent unique digital article (or other digital asset that is not fungible) is currently recorded on a particular decentralized ledger (or type of decentralized ledger, such as a private permissioned decentralized ledger).

In some implementations, permission and/or performance by performance component118may require not only a particular type of requested usage, but additionally may require the pertinent unique digital article (or other digital asset that is not fungible) currently be recorded on a particular decentralized ledger (or type of decentralized ledger). For example, a requirement for permission or performance may include recordation on a private permissioned decentralized ledger. In some implementations, actions by performance component118may be performed responsive to particular actions or results from other components of system100, including but not limited to grouping component116and/or ledger-analysis component120.

Ledger-analysis component120may be configured to determine whether one or more unique digital articles are recorded on a particular decentralized ledger. For example, ledger-analysis component120may determine whether a first unique digital article is currently recorded on a private permissioned decentralized ledger. In some implementations, ledger-analysis component120may be configured to analyze recordations and other transactions on one or more decentralized ledgers, e.g., by retrieving recorded information from the one or more decentralized ledgers and analyzing whether any of the recorded transactions pertain to a particular unique digital article, or a set of unique digital articles. In some implementations, determinations by ledger-analysis component120may be performed responsive to particular actions or results from other components of system100, including but not limited to grouping component116. In some implementations, ledger-analysis component120may be configured to determine whether ownership of a particular unique digital article (or other digital asset that is not fungible) has ever been recorded on a public decentralized ledger. For example, actions by other components of system100, including but not limited to distribution component124, may be responsive to determinations by ledger-analysis component120.

Notification component122may be configured to notify users. For example, notification component122may notify users in response to action requests. In some implementations, a user may be notified responsive to a requested manner of usage of a particular unique digital article (as requested through an action request) not being permitted or performed by performance component118. In some implementations, actions by notification component122may be performed responsive to particular actions, results, determinations, or decisions from other components of system100, including but not limited to grouping component116, performance component118, and/or ledger-analysis component120. For example, notification component122may respond to a particular action request (by a particular user, and pertaining to a particular unique digital article) with a particular response such that, responsive to the particular manner of usage, as requested in the particular action request, being grouped under a particular type (e.g., the second type) of unique digital article usage, and further responsive to determining the particular decentralized ledger on which the particular unique digital article has been recorded is a public decentralized ledger, the particular response notifies the particular user that the particular user is not permitted to use the particular unique digital article according to the particular action request.

Distribution component124may be configured to distribute and/or otherwise provide one or more of information, access to in-game content, access to game-specific communication channels, certificates, rewards, awards, prizes, distribution gains, and/or virtual items to users123. Distributions by distribution component124may be adjusted, e.g., by adjustment component126. In some implementations, distributions may be responsive to determinations by reward component131. In some implementations, distributions may be based on and/or responsive to actions by other components of system100, including but not limited to ledger-analysis component120. For example, online gaming platform105may determine a particular user is eligible to receive one or more rewards or awards. Distribution component124may distribute the one or more rewards or awards in accordance with the determined eligibility. For example, a reward may be a participation reward. For example, an award may be an attendance award. For example, a certificate may be a certificate of completion or accomplishment, which may be specific to actions within the instance of the game. For example, a prize may be for effort, time, and/or resources spent, specifically in the instance of the game. For example, particular unique digital articles may be associated with distribution rights, and the particular user who owns those distribution rights may receive distribution gains in accordance with those distribution rights. For example, distribution gains may result from a particular action or activity (such as, e.g., a sale of a particular digital asset), e.g., within the online gaming platform105, involving the particular digital asset.

Adjustment component126may be configured to adjust and/or modify distributions, including (planned or expected) distributions by distribution component124. In some implementations, adjustment component126may adjust and/or modify one or more certificates, rewards, awards, prizes, distribution gains, and/or virtual items that have been determined by reward component131(also referred to as the determined distribution or the eligible distribution). Upon such adjustment and/or modification, this determined distribution (or eligible distribution) may be referred to as the adjusted distribution. Distribution component124may distribute the adjusted distribution. In some implementations, adjustments and/or modifications by adjustment component126may increase the value of one or more elements of the eligible distribution (this may provide a positive incentive to users to record particular unique digital articles on a particular decentralized ledger). Alternatively, and/or simultaneously, adjustments and/or modifications by adjustment component126may decrease the value of one or more elements of the eligible distribution (this may provide a negative incentive to users to record particular unique digital articles on a particular decentralized ledger). In some implementations, actions by adjustment component126may be performed responsive to particular actions or results from other components of system100, including but not limited to ledger-analysis component120.

Ledger component128may be configured to generate sets of instructions for decentralized ledger servers111(e.g., decentralized ledger server111a) and/or one or more decentralized ledgers (e.g., blockchain117a). In some implementations, ledger component128may be configured to transfer the generated sets of instructions to decentralized ledger servers111and/or one or more decentralized ledgers. In some implementations, one or more of these instructions may instruct the formation of a smart contract and/or the recording of the smart contract on the one or more decentralized ledgers (e.g., blockchain117a). In some implementations, these instructions may instruct decentralized ledger servers111to record and/or modify unique digital articles, assets, transactions, and/or rights on one or more decentralized ledgers. For example, ledger component128may transfer a particular set of instructions that, upon execution by blockchain117aand blockchain117b, remove a particular unique digital article from blockchain117aand add the particular unique digital article to blockchain117b.

Population component129may be configured to determine the size of a set of unique digital articles. In some implementations, a set of unique digital articles may have a common user in control. In some implementations, a set of unique digital articles may have common visual characteristics as in-game user-controllable characters. For example, all semi-fungible digital assets from one or more limited sets may form a set of unique digital articles. For example, all digital assets (that are not fungible) that are issued (or that may be issued) by the same smart contract may form (part of) a set of unique digital articles. For example, all “Dazzle Blankos” that could be or have been issued may form a particular set of unique digital articles. As another example, the combination of all “Boss Dino Blankos” and all “Dazzle Blankos” that have been issued to date may form a specific set of unique digital articles. In some implementations, population component129may be configured to determine fractions of sets of unique digital articles for which ownership is recorded on a particular decentralized ledger (e.g., on the private permissioned decentralized ledger). In some implementations, population component129may be configured to determine fractions of sets of unique digital articles for which ownership is not recorded on a particular decentralized ledger (e.g., on the private permissioned decentralized ledger). In some implementations, the specific definition used by population component129to determine a population may be modified (e.g., by an administrative user) to include and/or exclude certain types of unique digital article, or unique digital article having certain characteristics, and/or to otherwise apply a filter to a larger set of unique digital article in order to create a subset of unique digital article that is smaller.

Reward component131may be configured to determine eligibility for unique digital articles, other digital assets that are not fungible, and/or users123to receive one or more of information, access to in-game content, access to game-specific communication channels, certificates, rewards, awards, prizes, distribution gains, and/or virtual items. In some implementations, these types of determinations may be based on and/or responsive to actions by other components of system100, including but not limited to ledger-analysis component120. In some implementations, online gaming platform105may determine a particular user is eligible to receive one or more rewards or awards. Distributions in accordance with the determined eligibility may be made by distribution component124. In some implementations, (one or more elements of) such eligible distributions may be adjusted and/or modified by adjustment component126prior to being distributed.

Presentation component133may be configured to present interfaces (e.g., user interfaces125) to users, e.g., through client computing platforms104associated with the respective users. In some implementations, presentation component133may be configured to effectuate presentations of interfaces to users. The presented interfaces may include challenge interfaces, as described in this disclosure. In some implementations, presentations by presentation component133may be performed jointly (or at least in some cooperative manner) with one or both of game component108and/or interaction component110. Presentation component133may present offers (from other users) to particular users, as described elsewhere in this disclosure.

Receipt component136may be configured to receive (sets of) instructions to add, modify, and/or remove recorded rights in blockchain117a. For example, receipt component136may receive one or more sets of instructions from ledger component128, online gaming platform105, and/or other components of system100. Receipt component136may provide received sets of instructions to record component134for execution. In some implementations, execution of individual ones of the instructions received may include invoking one or more function calls of an Application Programming Interface (API)107. For example, API107may be configured to provide interactive communication between blockchain117aand other components of system100. For example, in some implementations, API function calls may be implemented as function calls to smart contracts stored on blockchain117a. In some implementations, receipt component136may be arranged, organized, and/or otherwise included in decentralized ledger server111and/or blockchain117a.

Transaction component134may be configured to record (ownership) rights pertaining to digital assets, e.g., on blockchain117a. In some implementations, transaction component134may record rights on electronic storage130b. In some implementations, transaction component134may record rights on blockchain117a. The rights may include ownership rights, distribution rights, and/or other rights. For example, particular recorded rights may reflect ownership of a particular digital asset by a particular user or group of users. For example, the particular digital asset may be not fungible, and may represent a three-dimensional in-game user-controllable item or character that can interact with other virtual items within online gaming platform105. Recorded rights may be asset-specific. For example, distribution rights for a particular digital asset may designate rights to certain distributions of benefits upon a specifically defined in-game action (e.g., an exchange between users) involving the particular digital asset.

In some implementations, transaction component134may be configured to record rights in blockchain117a. In some implementations, transaction component134may add, modify, and/or remove recorded rights. For example, in accordance with received instructions from receipt component136, transaction component134may transfer ownership of a particular digital asset from a first owner to a second owner (e.g., from an original owner to a new owner, or from a loser of a challenge to a winner of the challenge) such that the recorded rights on blockchain117ano longer reflect the ownership of the particular digital asset by the first user. In some implementations, in accordance with received instructions, transaction component134may transfer ownership of a particular digital asset temporarily, e.g., from a first owner to a temporary second owner such as a smart contract. In some case, a temporary owner may be a holding account that is merely used until ownership is transferred to either the original owner or a new owner. As used herein, the term “temporary” (and derivatives thereof) refers to a transfer or to ownership that is either known to be changed and/or modified within a predetermined period, or expected to be changed and/or modified within a predetermined period. Conversely, a non-temporary transfer from a first owner to a second owner (due to a particular exchange) can conceivably be changed and/or reverted (back from the second owner to the first owner) due to a separate and new exchange that is independent of the first particular exchange. In some implementations, in accordance with received instructions, transaction component134may transfer ownership of a particular digital asset non-temporarily from a first owner to a second owner, e.g., when a particular exchange is not reversible or no longer reversible. In some implementations, transaction component134may be arranged, organized, and/or otherwise included in blockchain117a.

In some implementations, transaction component134may be configured to obtain asset-specific rights (e.g., ownership rights, distribution rights, and/or other rights) for particular digital assets. In some implementations, transaction component134may be configured to access blockchain117ato obtain the asset-specific rights (that are recorded on blockchain117a, e.g., in one or more smart contracts).

Input component135may be configured to receive user input from administrative users. For example, the user input may include entry and/or selection of particular information, unique digital articles, virtual items, and/or any entity or object that interacts with any part of system100and/or plays a part in the operation of system100. For example, an administrative user may select a particular set of unique digital articles (e.g., all “Dazzle Blankos” that have been issued) as the input set of unique digital articles for other components of system100, such as population component129. Additionally, the administrative user may select a particular adjustment to be enacted by adjustment component126(e.g., increase the value of one or more elements of the eligible distribution) for one or more types of determinations by reward component131(e.g., an eligible distribution of a reward of 100 virtual coins for leveling up a unique digital article in the selected set of unique digital articles, provided that the particular unique digital article is currently recorded on the private permissioned decentralized ledger, as determined by ledger-analysis component120). Based on these inputs and/or selections by the administrative user, system100may provide a ledger-specific utility for (a set of) unique digital articles that incentivizes recording these unique digital articles on a specific decentralized ledger.

As another example, the administrative user may select a different set of unique digital articles (e.g., all “Boss Dino Blankos” that have been issued) as the input set of unique digital articles for other components of system100, such as population component129. Additionally, the administrative user may select a particular adjustment to be enacted by adjustment component126(e.g., decrease the value of one or more elements of the eligible distribution) for one or more types of determinations by reward component131(e.g., an eligible distribution may be receiving the distribution gains based on particular in-game actions for unique digital articles in the selected set of unique digital articles, provided that the particular unique digital article is currently recorded on the public decentralized ledger, as determined by ledger-analysis component120). Based on these inputs and/or selections by the administrative user, system100may provide a ledger-specific utility for (a selected set of) unique digital articles that incentivizes recording these unique digital articles on the private permissioned decentralized ledger.

Communication component137may be configured to facilitate communication and/or interaction between administration server115and the rest of system100. For example, communication component137may communicate user input received by input component135to other components of system100, particularly of online gaming platform105.

Referring toFIG.1, user interfaces125may be configured to facilitate interaction between users123and system100and/or between users123and client computing platforms104. For example, user interfaces125may provide an interface (e.g., a challenge interface) through which users123may provide information to and/or receive information from system100. In some implementations, user interface125may include one or more of a display screen, touchscreen, monitor, a keyboard, buttons, switches, knobs, levers, mouse, microphones, sensors to capture voice commands, sensors to capture body movement, sensors to capture hand and/or finger gestures, and/or other user interface devices configured to receive and/or convey user input. In some implementations, one or more user interfaces125may be included in one or more client computing platforms104. In some implementations, one or more user interfaces125may be included in system100. In some implementations, user interface125may be a type of interface that facilitates the exchange of virtual items between users.

FIG.3illustrates an example implementation of a user interface300as may be used by system100, in accordance with one or more implementations. User interface300may enable a particular user to view and/or use an account inventory and/or one or more unique digital articles controlled by the particular user. User interface300may include a section or field for account inventory31, and/or other graphical user interface elements. As depicted, account inventory31may include a list of different virtual items and/or assets currently controlled by the particular user, including virtual items 1-2-3-4-5. Account inventory31further depicts item information regarding these virtual items, as indicated by item information 1-2-3-4-5, which correspond to virtual items 1-2-3-4-5, respectively. Account inventory31as depicted may further include graphical user interface elements such as, by way of non-limiting example, an action button32(which initiates an action request). Upon engagement by the particular user, action request button32may request “virtual item 1” to be used for an action the particular user can select (e.g., through a text field or a dropdown menu, as indicated by a triangle in a box). For example, the particular user may request the action that displays unique digital article15, which may be associated with a user-controllable in-game character that is also depicted in user interface300. Action requests for this manner of usage (displaying the unique digital article) may be grouped under a first type of usage that includes passive manners of usage, which may be permitted and subsequently performed, as requested by the particular user, regardless of the current decentralized ledger this unique digital article is recorded on.

FIG.4Aillustrates an example implementation of a user interface300aas may be used by system100, in accordance with one or more implementations. User interface300ais similar to user interface300inFIG.3. User interface300amay enable a particular user to view and/or use an account inventory and/or one or more unique digital articles controlled by the particular user. User interface300amay include a section or field for account inventory31, and/or other graphical user interface elements. As depicted, account inventory31may include a list of different virtual items and/or assets currently controlled by the particular user, including virtual items 1-2-3-4-5. Account inventory31further depicts item information regarding these virtual items, as indicated by item information 1-2-3-4-5, which correspond to virtual items 1-2-3-4-5, respectively. Account inventory31as depicted may further include graphical user interface elements such as, by way of non-limiting example, an action button32. Upon engagement by the particular user, action request button32may request “virtual item 1” to be used for an action the particular user can select (e.g., through a text field or a dropdown menu, as indicated by a triangle in a box). For example, the particular user may request the action to play in the instance of a game using the user-controllable in-game character, also depicted in user interface300a, that is associated with unique digital article15. Action requests for this manner of usage (playing with the user-controlled character associated with the particular unique digital article) may be grouped under a second type of usage that includes active manners of usage, which may be only permitted responsive to this unique digital article being currently recorded on a particular decentralized ledger (e.g., a private permissioned decentralized ledger). User interface300aas depicted may further include graphical user interface elements such as, by way of non-limiting example, a notification element33a. Upon engagement by the particular user of action request button32, and responsive to this unique digital article failing to be currently recorded on the particular decentralized ledger, notification element33ais displayed to the particular user, labeled “You can't play with this character until you move him to Blockchain X.” For example, this “Blockchain X” may be the private permissioned decentralized ledger. In this case, the requested manner of usage is not permitted and the response to this particular action request includes displaying notification element33a.

FIG.4Billustrates an example implementation of a user interface300bas may be used by system100, in accordance with one or more implementations. User interface300bis similar to user interface300ainFIG.4A. User interface300bmay enable a particular user to view and/or use an account inventory and/or one or more unique digital articles controlled by the particular user. User interface300bmay include a section or field for account inventory31, and/or other graphical user interface elements. As depicted, account inventory31may include a list of different virtual items and/or assets currently controlled by the particular user, including virtual items 1-2-3-4-5. Account inventory31further depicts item information regarding these virtual items, as indicated by item information 1-2-3-4-5, which correspond to virtual items 1-2-3-4-5, respectively. Account inventory31as depicted may further include graphical user interface elements such as, by way of non-limiting example, an action button32. Upon engagement by the particular user, action request button32may request “virtual item 1” to be used for an action the particular user can select (e.g., through a text field or a dropdown menu, as indicated by a triangle in a box). For example, the particular user may request the action to gain a particular experience in the instance of a game using virtual item 1 (which may be a unique digital article). Action requests for this manner of usage (gaining the particular experience in the instance of the game using virtual item 1) may be grouped under a type of usage for which a reward may be adjusted and/or increased responsive to the particular unique digital article being currently recorded on a particular decentralized ledger (e.g., a private permissioned decentralized ledger). User interface300bas depicted may further include graphical user interface elements such as, by way of non-limiting example, a notification element33b. Upon engagement by the particular user of action request button32, and responsive to this unique digital article failing to be currently recorded on the particular decentralized ledger, notification element33bis displayed to the particular user, labeled “You earned100gold coins for leveling up. Next time, you can earn150gold coins if you move this character to Blockchain X.” For example, this “Blockchain X” may be the private permissioned decentralized ledger. In this case, the requested manner of usage is permitted (the particular experience is gained, and subsequently rewarded by 100 gold coins) and the response to this particular action request further includes displaying notification element33b. Notification element33bexplains how the reward would be increased in the future if this unique digital article would be moved to and recorded on “Blockchain X”. This type of adjustment of a reward (whether announced in advance or after actually occurring) may provide a positive incentive to players to record particular unique digital articles on a particular decentralized ledger (e.g., on the private permissioned decentralized ledger).

FIG.5Aillustrate exemplary blockchain117cas may be used by system100, in accordance with one or more implementations.FIG.5Aillustrates a blockchain117cthat includes a block 0, a block 1, and a block 2. As time progresses, more blocks may be added to blockchain117c. The blocks within blockchain117care ordered. In block 0, three assets (indicated by a capital “A”) are generated and/or assigned to three users or participants: a first digital asset is assigned to user “i” (Ui), a second digital asset is assigned to user “j” (Uj), and a third digital asset, smart contract15a, is assigned to user “q” (Uq), which may be an administrative user. For example, smart contract15amay be or include a template for issuing a particular type of unique digital article. Smart contract15amay have been posted to blockchain117cby a component similar to record component134.

For example, the assets in block 0 may be individual ownership rights recorded for particular digital assets within an online gaming platform. Block 1 is connected to block 0 (as indicated by a link50a), for example by including an address of block 1 in block 0, or vice versa. Likewise, block 1 is connected to block 2, as indicated by a link50b. In block 1, a transaction to smart contract15a(indicated by “Ax”) is recorded. Transaction Ax to smart contract15amay issue a unique digital article to user “q”, the unique digital article being defined by metadata52(here, including a unique digital article named “Dazzle Blanko”, having identifier “#001”, as depicted by a linked image of unique digital article15, as well as including various other fields of information). In block 2, several transactions may be recorded: a transaction from user “j” to user “n”, and a transaction from user “q” to smart contract15a. For example, this transaction may represent user “q” using the particular unique digital article with identifier “#001” in some manner. Based on the particular blockchain or decentralized ledger this unique digital article is currently recorded on (here, blockchain117c), a reward user “q” may be eligible for may be adjusted (e.g., decreased in value) or eliminated, because the preferred blockchain may be a different blockchain, such as, e.g., blockchain117d.

By way of non-limiting example,FIG.5Billustrates a blockchain117dthat includes several blocks (block 3, block 4, block 5). Block 4 may be connected to block 3 (as indicated by a link50d), and block 5 may be connected to block 4 (as indicated by a link50e). In block 3, another transaction to smart contract15a(indicated by “Ax”) is recorded, which issues a unique digital article to user “p”, the unique digital article being defined by metadata54, and having identifier “#002”. Block 4 includes a transaction (indicated by a capital “T”) from user “i” to user “n”. For example, the transaction may represent a purchase of a first virtual item by user n from seller user “i”. Additionally, block 4 includes a transaction from user “p” to smart contract15a. For example, this transaction may represent user “p” using the particular unique digital article with identifier “#002” in some manner. Block 5 includes a transaction (by smart contract15a) representing a transfer of a reward to user “p”, based on the particular blockchain this unique digital article is currently recorded on (here, blockchain117d, which may be the preferred blockchain).

Referring toFIG.1, in some implementations, online gaming platforms105, server(s)102, client computing platform(s)104, administration servers115, decentralized ledger servers111, and/or external resources138may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via one or more networks13such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which online gaming platforms105, server(s)102, client computing platform(s)104, administration servers115, decentralized ledger servers111, and/or external resources138may be operatively linked via some other communication media.

A given client computing platform104may 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 platform104to interface with system100and/or external resources138, and/or provide other functionality attributed herein to client computing platform(s)104. By way of non-limiting example, the given client computing platform104may 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.

Administration server(s)115may include one or more of servers102a, processors132a, machine-readable instructions106a, electronic storage130a, and/or other components. Server(s)102amay be configured by machine-readable instructions106a. Machine-readable instructions106amay include one or more instruction components. The instruction components may include one or more of input component135, communication component137, and/or other instruction components. Administration server115may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. In some implementations, administration servers115may be used by one or more administrative users, e.g., to configure and/or control operation of system100. In some implementations, administrative servers115may include or user one or more user interfaces to receive user input and/or otherwise interact with one or more administrative users.

External resources138may include sources of information outside of system100, external entities participating with system100, external providers of computation and/or storage services, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources138may be provided by resources included in system100. In some implementations, external resources138may include one or more blockchain oracles (as may be used by monitoring component118to determine results for challenges).

Server(s)102may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s)102inFIG.1is not intended to be limiting. Server(s)102may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s)102. For example, server(s)102may be implemented by a cloud of computing platforms operating together as server(s)102.

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

Processor(s)132may be configured to provide information processing capabilities in server(s)102. As such, processor(s)132may 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. Although processor(s)132is shown inFIG.1as a single entity, this is for illustrative purposes only. In some implementations, processor(s)132may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s)132may represent processing functionality of a plurality of devices operating in coordination. Processor(s)132may be configured to execute components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137, and/or other components. Processor(s)132may be configured to execute components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s)132. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137are illustrated inFIG.1as being implemented within a single processing unit, in implementations in which processor(s)132includes multiple processing units, one or more of components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137may be implemented remotely from the other components. The description of the functionality provided by the different components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137described below is for illustrative purposes, and is not intended to be limiting, as any of components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137may provide more or less functionality than is described. For example, one or more of components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137may be eliminated, and some or all of its functionality may be provided by other ones of components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137. As another example, processor(s)132may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components108,110,112,114,116,118,120,122,124,126,128,129,131,133,134,135,136, and/or137.

FIG.2illustrates a method200to provide ledger-specific utilities for unique digital articles in an online gaming platform, in accordance with one or more implementations. The operations of method200presented below are intended to be illustrative. In some implementations, method200may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method200are illustrated inFIG.2and described below is not intended to be limiting.

In some implementations, method200may be implemented in 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 mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method200in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method200.

At an operation202, an instance of a game is executed, within the online gaming platform, to facilitate presentation of the game to users, and in-game actions are implemented in the instance of the game in response to action requests for the in-game actions by the users. Presentation of the game is based on views of the game that are determined during execution of the instance of the game. The users include a first user. In some embodiments, operation202is performed by a game component and/or an interaction component the same as or similar to game component108and/or interaction component110(shown inFIG.1and described herein).

At an operation204, user accounts are managed that are associated with the users. The user accounts include account inventories of virtual items. The user accounts include a first user account associated with the first user. The first user account includes a first account inventory of one or more virtual items. The first user controls the one or more virtual items in the first account inventory. The first account inventory includes a first unique digital article that is associated with a first in-game user-controllable character configured to be used in the instance of the game. In some embodiments, operation204is performed by an account component the same as or similar to account component112(shown inFIG.1and described herein).

At an operation206, on behalf of the first user, a first recordation request is received to record ownership of the first unique digital article on a first decentralized ledger. In some embodiments, operation206is performed by a recording component the same as or similar to recording component114(shown inFIG.1and described herein).

At an operation208, on behalf of the first user, a first action request is received to use the first unique digital article in a first manner of usage in the instance of the game. The first manner of usage is grouped under at most one of (i) a first type of unique digital article usage and (ii) a second type of unique digital article usage. The first type of unique digital article usage includes passive manners of usage including display of the first in-game user-controllable character in the first account inventory. The second type of unique digital article usage includes active manners of usage including interactive gameplay in the instance of the game using the first in-game user-controllable character as being controlled by the first user. In some embodiments, operation208is performed by a grouping component the same as or similar to grouping component116(shown inFIG.1and described herein).

At an operation210, responsive to the first manner of usage, as requested in the first action request, being grouped under the first type of unique digital article usage, the first action request is responded to by permitting the first user to use the first unique digital article according to the first action request. In some embodiments, operation210is performed by a performance component the same as or similar to performance component118(shown inFIG.1and described herein).

At an operation212, responsive to the first manner of usage, as requested in the first action request, being grouped under the second type of unique digital article usage, it is determined whether the first decentralized ledger on which the first unique digital article has been recorded is a private permissioned decentralized ledger. In some embodiments, operation212is performed by a ledger-analysis component the same as or similar to ledger-analysis component120(shown inFIG.1and described herein).

At an operation214, responsive to the first manner of usage, as requested in the first action request, being grouped under the second type of unique digital article usage, and further responsive to determining the first decentralized ledger on which the first unique digital article has been recorded is the private permissioned decentralized ledger, the first action request is responded to by permitting the first user to use the first unique digital article according to the first action request. In some embodiments, operation214is performed by a performance component the same as or similar to performance component118(shown inFIG.1and described herein).

At an operation216, responsive to the first manner of usage, as requested in the first action request, being grouped under the second type of unique digital article usage, and further responsive to determining the first decentralized ledger on which the first unique digital article has been recorded is a public decentralized ledger, the first action request is responded to with a response. The response notifies the first user that the first user is not permitted to use the first unique digital article according to the first action request. In some embodiments, operation216is performed by a notification component the same as or similar to notification component122(shown inFIG.1and described herein).

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. It is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with features of any other implementation.