Architecture
Last updated
Last updated
FIG.1 illustrates the architecture of a composite unit.
Composite unit 100 includes content addressed model 102, interface specification 104, and token pointer 106 (which associates the composite unit 100 with an NFT stored on decentralized ledger 110.
Elements 102, 104, and 106 are data elements stored as a data structure. The elements can be linked in various manners, such as with pointers, by being stored in a single data structure, or through relational tables.
Additionally, the elements can store the corresponding data or code, or can otherwise specify the data or code through a URL or other address. For example, content addressed model 102 can include the model code for executing the model or, as illustrated in FIG. 1, include an address to the storage location of the model code.
Decentralized ledger 110 can be part of a decentralized environment such as a blockchain network.
The NFT is a unique token that can be used to identify and represent ownership of composite unit 100, regardless of the executing environment in which composite unit 100 is being used at the time.
FIG. 2 illustrates multiple composite units, one for each arena, coupled to an input value matrix.
Each composite unit, 300a, 300b, and 300c in this example, has a corresponding arena agent 302a, 302b, and 302c.
Input value matrix 304 is coupled to each composite unit through the corresponding arena agent.
FIG. 3 illustrates a complex input value matrix.
A set of variables can be related to a category of attributes. For example, attributes 602 represent strength of the player entity with respect to the relevant arena, attributes 604 represent intelligence of the player entity with respect to the relevant arena, and attributes 606 represent agility of the player entity with respect to the relevant arena.
Each set of values in input value matrix can be mapped to an array of variables in model code or each variable can be mapped to an individual variable in the model code.
