U.S. Pat. No. 11,484,796

DETAILED DESCRIPTION

FIG. 1illustrates a system100configured for facilitating distribution of in-game instructions pertaining to a gaming platform105(e.g., an online gaming platform), in accordance with one or more implementations. In some implementations, system100may include one or more of electronic storage132, one or more servers102, one or more client computing platforms104, one or more gaming platforms105, one or more blockchains111(e.g., a distributed blockchain), one or more external resources130, and/or other components. 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. Users123may access system100via client computing platform(s)104. Users123may include one or more of a first user, a second user, a third user, a fourth user, and/or other users. In some implementations, users123may include one or more creating users, requesting users, selling users, buying users, owning users, and/or other users. In some implementations, one or more users123do not need to be players of any gaming platform.

In some implementations, system100and/or servers102may be configured to communicate with one or more of (online) gaming platform(s)105, users123, blockchain(s)111, and/or other components. As used herein, gaming platform105may refer to either an individual game, a type of gaming console and its ecosystem, and/or both. Gaming platform105may be operated, hosted, and/or owned by a stakeholder of gaming platform105. Users123may include players who play on gaming platform105.

In some implementations, a distributed blockchain such as blockchain111may be maintained by a distributed computing platform (not shown inFIG. 1). In some implementations, the distributed computing platform may be implemented by a set of client computing platforms and/or servers. 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. In some implementations, the distributed computing platform may include electronic storage configured to store part or all of blockchain(s)111. The smart contracts may be stored on blockchain(s)111. In some implementations, the distributed computing platform may be the EOSIO platform. In some implementations, the distributed computing platform may be Ethereum. In some implementations, the virtual machine may be a Turing-complete and decentralized virtual machine.

A distributed blockchain may act as a (decentralized) database that stores a registry of assets and transactions across one or more networks. A given asset may be owned by a particular user. An asset may include anything of material value or usefulness that is owned by or on behalf of a person or company, including but not limited to assets created by asset creating component108, and/or other assets. In some implementations, a right pertaining to an object may be an asset, the object being a physical or a virtual item. Multiple rights may form a set of rights or a bundle of rights that may be transferred and/or otherwise acted on or operated on together. For example, rights may include a right to use, a right to sell, a right to destroy, and/or other rights. In some implementations, tokens may be a type of asset. In some implementations, tokens may include one or more of security tokens, utility tokens, payment tokens, initial coin offering (ICO) tokens, virtual currency tokens, crypto tokens, ERC-20 tokens, EOS tokens, and/or other tokens. In some implementations, tokens not only represent value, but may have a specific use in a particular distributed computing platform, e.g., in the operation of blockchain111.

In some implementations, blockchain(s)111may record and/or register ownership of assets. Alternatively, and/or simultaneously, blockchain(s)111may register transactions that modify ownership of assets. A smart contract may be a type of asset. In some implementations, once a smart contract has been added to a blockchain, the smart contract may be referred to as published, posted, registered, and/or recorded. Elements of blockchain(s)111may 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.

Blockchain(s)111may be publicly accessible and append-only. In some implementations, existing blocks of a distributed blockchain can substantially not be altered or deleted, unless multiple copies of the distributed blockchain are altered. This is unlikely to happen provided that multiple copies of the distributed blockchain are stored on different computing platforms, e.g., in different geographical locations. The distributed blockchain may be replicated on multiple computing platforms, preferably in multiple different geographical locations.

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 asset creating component108, transformation request component110, verification performance component112, transformation component114, asset sales component116, sale confirmation component118, asset registering component120, transfer registering component122, recipe component124, recipe receipt component126, user notification component128, and/or other instruction components.

Asset creating component108may be configured to create assets, including but not limited to assets that may be used on one or more (online) gaming platform(s)105. In some implementations, an asset may include and/or refer to a set of in-game instructions. In some implementations, in-game instructions may be provided by users123of gaming platform105, including but not limited to a first user. Execution of the set of in-game instructions may facilitate a transformation of one or more in-game assets into one or more transformed and/or new in-game assets. For example, a particular set of instructions may facilitate a transformation of a sword into an enchanted sword, within gaming platform105. For example, a particular set of instructions may facilitate a transformation of a particular quantity of steel, wood, and string into a crossbow, within gaming platform105. For example, a particular set of instructions may facilitate a transformation of particular quantities of building materials into a house, within gaming platform105. In some implementations, sets of instructions may operate as a blueprint and/or recipe. A set of in-game instructions may specify one or more steps within the online gaming platform that perform a transformation of one or more in-game assets. As used herein, the term “step” refers to one or more operations that can occur or be performed within gaming platform105. In some implementations, an individual step may include an operation that users of gaming platform105can perform manually, e.g., under certain conditions and/or with certain prerequisites. In some implementations, an individual step may include an operation within gaming platform105that users of gaming platform105cannot perform manually. In some implementations, in-game assets may include avatars, characters, and/or the appearance of users123within gaming platform105. In some implementations, assets that facilitate transformations may be implemented as smart contracts on blockchain111. In some implementations, assets that facilitate transformations may use smart contracts on blockchain111.

In some implementations, completion of a transformation as described by a particular set of in-game instructions may require ownership of the asset that includes and/or refers to the particular set of in-game instructions. In some implementations, completion of a transformation as described by a particular asset may require ownership of the particular asset. In some implementations, completion of a particular transformation may require ownership of at least one of an in-game capability, a given in-game asset, and/or one or more other objects. For example, the transformation of a sword into an enchanted sword within gaming platform105may require certain magical skills, as well as a non-enchanted sword (perhaps of a particular type that can be enchanted). For example, the transformation of a set of building materials into a house within gaming platform105may require one or more of carpentry, drywall, plumbing, roofing and electrician skills, as well as a variety of (power) tools. In some implementations, completion of a transformation may require effort, time, and/or (virtual) currency. In some implementations, transformations may be irreversible. For example, once eggs, flour, and sugar are transformed into a dessert within gaming platform105, such a transformation may be irreversible.

Transformation request component110may be configured to receive requests for execution of sets of in-game instructions. In some implementations, transformation request component110may be configured to receive a particular request, from a particular user of gaming platform105, for execution of a particular set of in-game instructions. In other words, the particular user may request a particular transformation of one or more particular in-game assets. In some implementations, transformation request component110may receive requests within gaming platform105. In some implementations, transformation request component110may receive requests within a distributed computing platform, in particular blockchain111. In some implementations, transformation request component110may receive requests through other components of system100.

In some implementations, a transformation may be performed (e.g., by transformation component114) responsive and/or subsequent to one or more verifications, including but not limited to verifications by verification performance component112. For example, a particular transformation may be performed and/or completed responsive to verifying that the requesting user owns the asset describing the transformation. For example, a particular transformation may be performed responsive to verifying that the requesting user owns the required in-game assets. In some implementations, receiving the request from a requesting user may imply consent to transform one or more particular in-game assets currently owned by the requesting user.

Verification performance component112may be configured to perform one or more verifications, including but not limited to a first verification, a second verification, a third verification, and/or other verifications. In some implementations, one or more verifications may pertain to ownership of assets, abilities, and/or other objects. In some implementations, a first verification may verify whether the requesting user owns a particular asset that includes and/or refers to a particular set of in-game instructions. In some implementations, a second verification may include verifying whether the requesting user owns the one or more particular in-game assets. In some implementations, a third verification may verify whether the requesting user owns at least one of a required in-game capability (e.g., a skill) and/or a given in-game asset (e.g., a tool). In some implementations, performance and/or completion of transformations may be conditioned on the results of one or more verifications by verification performance component112. For example, performance and/or completion of a particular transformation may be responsive to verifying that the requesting user owns at least one of a required in-game capability and a given in-game asset. In some implementations, performing a transformation may not destroy the asset that includes and/or refers to a particular set of in-game instructions. In some implementations, performing a transformation may not destroy a particular required in-game capability. In some implementations, performing a transformation may not destroy a given required in-game asset. In some implementations, completing a transformation may not destroy the asset that includes and/or refers to a particular set of in-game instructions. In some implementations, completing a transformation may not destroy a particular required in-game capability. In some implementations, completing a transformation may not destroy a given required in-game asset.

Transformation component114may be configured to transform one or more in-game assets into one or more transformed and/or new in-game assets. In some implementations, transformations performed by transformation component114may be in accordance with a set of in-game instructions. In some implementations, transformations performed by transformation component114may be in accordance with a request for a transformation. In some implementations, transformations performed by transformation component114may be performed responsive to (particular results of) one or more verifications by verification performance component112.

In some implementations, transformations may be performed using similar rather than identical in-game assets. For example, a particular asset may include a set of in-game instructions to transform a vehicle in a prescribed manner, including lowering the suspension, increasing the size of the rims, adding tinted windows, adding a custom paint job, changing the upholstery on the seats, upgrading the exhaust system, etc. Certain transformations may be available for a variety of vehicles. In some implementations, transformations may include one or more of aesthetic changes, functional changes, performance changes, and/or other changes.

By way of non-limiting example,FIGS. 3A-3Billustrate an exemplary transformation of an in-game character as may be performed by system100.FIG. 3Adepicts a mythical creature31that may be some type of fire-breathing winged dragon. For example, a particular asset may include a particular set of in-game instructions to transform an in-game character, in this case mythical creature31, into a transformed mythical creature32as shown inFIG. 3B. The particular set of in-game instructions may transform a creature, such as mythical creature31, in a prescribed manner, by making the legs shorter, the tail shorter, the coat or fur longer, the body longer, the eyes and mouth friendlier, modifying the ratio of the head and the body, adding or changing dog-like ears, adding a dog-like happy tongue, etc. This particular transformation may mimic the effect of cross-breeding a creature with a corgi.

Referring toFIG. 1, asset sales component116may be configured to offer assets for sale, e.g., to users123of gaming platform105. By way of non-limiting example, assets offers for sale may include assets that include and/or refer to a set of in-game instructions, such as, e.g., assets created by asset creating component108. In some implementations, assets may be offered for sale through a user interface. For example, in some implementations, such a user interface may be part of gaming platform105. In some implementations, assets may be offered for sale in a store that is external to system100. In some implementations, assets may be offered for sale through a store interface that is external to system100. In some implementations, assets may be offered for sale within gaming platform105. In some implementations, assets may be offered for sale within blockchain111. In some implementations, assets may be offered for sale in a store or through a store interface that is included in system100.

Sale confirmation component118may be configured to receive information reflecting sales, including but not limited to sales of assets created by asset creating component108. In some implementations, sale confirmation component118may be configured to obtain confirmation of occurrences of sales of assets. In some implementations, sale confirmation component118may be configured to receive information reflecting a sale of the asset to a particular user of gaming platform105. Responsive to the sale of a particular asset, the particular asset may have been added to an inventory of the purchasing user. In some implementations, an inventory may be maintained within gaming platform105on behalf of the purchasing user. In some implementations, verifications by verification performance component112may verify whether a particular inventory of a particular user (e.g., the purchasing user) includes a particular asset.

Asset registering component120may be configured to register assets and/or other information on blockchain111. The assets may include, but are not limited to, assets created by asset creating component108. In some implementations, asset registering component120may be configured to register ownership of assets on blockchain111. In some implementations, assets may include (and/or be associated with) ownership addresses of owners of the assets. For example, a transfer of ownership (e.g., due to a sale) may be registered on blockchain111, e.g., by a change in a particular ownership address. In some implementations, verification by verification performance component112may include verifying whether a particular ownership address of a particular asset is associated with a particular user.

By way of non-limiting example,FIG. 4Aillustrates a blockchain111athat implements a blockchain including a block 0, a block 1, and a block 2. As time progresses, more blocks may be added to blockchain111a. The blocks within blockchain111aare ordered. In block 0, three assets (indicated by a capital “A”) are generated and/or assigned to three users or participants: a first asset is assigned to user i (Ui), a second asset is assigned to user j (Uj), and a third asset is assigned to user k (Uk). These assets may be individual tokens manifested, deployed, and/or instantiated through an asset creating component similar to asset creating component108(seeFIG. 1). Block 1 is connected to block 0 (as indicated by a link40a), 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 link40b.

In block 1, one asset (labeled Ax) is generated and/or assigned to user q (Uq). For example, the asset in block 1 may be an individual token created by an asset creating component similar to asset creating component108(seeFIG. 1). Additionally, block 1 includes two transactions (indicated by a capital “T”): a first transaction from user i to user j, and a second transaction from user j to user k. Block 2 includes a first transaction from user j to user m, and a second transaction from user j to user n. In some implementations, based on the contents of the blocks, any user of blockchain111amay determine the current assets of blockchain111a, and the balances of any user. In some implementations, the balance of a particular user may be verified prior to adding a transaction that reduces that particular user's balance. For example, an individual user may not be allowed to transfer assets the individual user does not own.

Referring toFIG. 1, transfer registering component122may be configured to register transfers of assets on blockchain111. Transfers may occur due to sales and/or other reasons. In some implementations, transfer registering component122may be configured to register transfers of ownership of assets on blockchain111. In some implementations, a transfer of the ownership of a particular asset to a particular user may be registered by modifying the ownership address of the particular asset on blockchain111to an address associated with the purchasing user.

Recipe component124may be configured to create set of in-game instructions. For example, a particular user may perform, record, and/or otherwise describe a particular set of in-game instructions. In some implementations, recipe component124may be configured to create a particular asset that includes and/or refers to the particular set of in-game instructions. In some implementations, asset creating component108may be configured to create a particular asset that includes and/or refers to the particular set of in-game instructions. For example, in some implementations, recipe component124may facilitate interaction through a user interface such that a user can assemble, organize, and/or otherwise modify one or more in-game instructions.

Recipe receipt component126may be configured to receive sets of in-game instructions from users123. In some implementations, recipe receipt component126may be configured to receive sets of in-game instructions through recipe component124, asset creating component108, and/or other components of system100. For example, a creating user may use an external resource to assemble a particular set of in-game instructions, and provide the particular set to system100through recipe receipt component126.

User notification component128may be configured to notify users123, e.g., regarding verifications by verification performance component112. For example, user notification component128may be configured to present a notification to a particular user, responsive to a first verification verifying whether the particular user owns a particular asset. Such a notification may include the result of the first verification, a recommendation to remedy the source of the verification failure, and/or other information. For example, user notification component128may be configured to present a notification to a particular user, responsive to a second verification verifying whether the particular user owns at least one of a required in-game capability and a particular in-game asset. Such a notification may include the result of the second verification, a recommendation to remedy the source of the verification failure, and/or other information.

By way of non-limiting example,FIG. 4Billustrates a blockchain111bthat includes the same blocks as blockchain111aofFIG. 4A, plus additional blocks (block 3, block 4, block 5) that have been appended to the blockchain. Block 3 may be connected to block 2 (as indicated by a link40c), block 4 may be connected to block 3 (as indicated by a link40d), and block 5 may be connected to block 4 (as indicated by a link40e). In block 3, a smart contract41(indicated by a capital “C”) is posted. For example, smart contract41may have been generated to implement a transformation in accordance with the set of in-game instructions included in asset Ax. For example, smart contract41may perform one or more verifications pertaining to a transformation. InFIG. 4B, a function call to a function defined by smart contract41may be depicted and/or implemented as a transaction. Smart contract41may have been posted to blockchain111bby a component similar to asset registering component120(shown inFIG. 1). Referring toFIG. 4B, for example, smart contract41may include asset Ax and record that asset Ax is currently owned by user q (Uq). In block 4, one asset is generated and/or assigned to user p (Up). Additionally, block 4 includes a transaction (indicated by a capital “T”): a transaction from user i to user n. For example, the transaction may represent a purchase of a first virtual item by user n. Additionally, block 4 includes a transaction from user q to the same smart contract as depicted in block 3. For example, the transaction may represent user q requesting a transformation in accordance with the set of in-game instructions included in asset Ax. Block 5 includes two transactions (indicated by a capital “T”): a first transaction of ownership of smart contract41from user q to user p, and a second transaction may represent user p requesting another transformation in accordance with the set of in-game instructions included in asset Ax. For example, the first transformation (responsive to the transaction in block 4) may operate on one or more in-game assets owned by user q. For example, the second transformation (responsive to the transaction in block 5) may operate on one or more in-game assets owned by user p. Referring toFIG. 1, in some implementations, the performance of a transformation and/or a verification may be outside of a blockchain, e.g., within gaming platform105.

Referring toFIG. 1, in some implementations, server(s)102, client computing platform(s)104, and/or external resources130may 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 networks13, including but not limited to 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 server(s)102, client computing platform(s)104, and/or external resources130may 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 resources130, 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 smart watch, a gaming console, and/or other computing devices.

External resources130may include sources of information and/or services outside of system100, external entities participating with system100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources130may be provided by resources included in system100. In some implementations, external resources130may include a store and/or store interface that offers assets for sale, including but not limited to assets that include and/or refer to sets of in-game instructions.

Server(s)102may include electronic storage132, one or more processors134, and/or other components. 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 storage132may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage132may 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 storage132may 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 storage132may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage132may store software algorithms, information determined by processor(s)134, 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)134may be configured to provide information processing capabilities in server(s)102. As such, processor(s)134may 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)134is shown inFIG. 1as a single entity, this is for illustrative purposes only. In some implementations, processor(s)134may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s)134may represent processing functionality of a plurality of devices operating in coordination. Processor(s)134may be configured to execute components108,110,112,114,116,118,120,122,124,126, and/or128, and/or other components. Processor(s)134may be configured to execute components108,110,112,114,116,118,120,122,124,126, and/or128, 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)134. 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, and/or128are illustrated inFIG. 1as being implemented within a single processing unit, in implementations in which processor(s)134includes multiple processing units, one or more of components108,110,112,114,116,118,120,122,124,126, and/or128may 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, and/or128described 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, and/or128may provide more or less functionality than is described. For example, one or more of components108,110,112,114,116,118,120,122,124,126, and/or128may 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, and/or128. As another example, processor(s)134may 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, and/or128.

FIG. 2illustrates a method200for facilitating distribution of in-game instructions pertaining to 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.

An operation202may include creating an asset that includes and/or refers to a set of in-game instructions provided by a first user of the online gaming platform. Execution of the set of in-game instructions may facilitate a transformation of one or more in-game assets into one or more transformed and/or new in-game assets. The set of in-game instructions may specify one or more steps within the online gaming platform that perform the transformation of the one or more in-game assets. Completion of the transformation may require ownership of the asset. Operation202may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to asset creating component108, in accordance with one or more implementations.

An operation204may include receiving a request, from a second user of the online gaming platform, for execution of the set of in-game instructions to facilitate a first transformation of one or more particular in-game assets. Operation204may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to transformation request component110, in accordance with one or more implementations.

An operation206may include performing a first verification whether the second user owns the asset. Operation206may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to verification performance component112, in accordance with one or more implementations.

An operation208may include transforming the one or more particular in-game assets into one or more particular transformed and/or new in-game assets in accordance with the set of in-game instructions and the request for the first transformation, responsive to the first verification verifying that the second user owns the asset. Operation208may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to transformation component114, in accordance with one or more implementations.

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. For example, 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 one or more features of any other implementation.