in_game_id.move

The in_game_id.move module is a Layer 1 Composable Primitive that provides a standardized identity system for all entities within EVE Frontier. It enables the creation of deterministic and unique identifiers that bridge the gap between off-chain game systems and on-chain Sui objects.

1. Core Component Architecture

The module is centered around the TenantItemId struct, which serves as the primary key for object identification across the entire ecosystem.

classDiagram
    class TenantItemId {
        +u64 tenant_id
        +u64 item_id
    }

Key Data Structures

• TenantItemId: A simple but critical copy, drop, and storeable struct. It combines:
• tenant_id: Identifies the specific game instance or administrative domain.
• item_id: A unique identifier for the specific asset within that tenant’s scope.

2. Identity Derivation Logic

The primary purpose of this module is to provide a consistent way to represent and verify identities. It acts as the “Social Security Number” system for game assets.

flowchart LR
    A[Tenant ID] -- Combine --> C(TenantItemId)
    B[Item ID] -- Combine --> C
    C -- Seed --> D[ObjectRegistry]
    D -- Derive --> E[Sui Object ID]

• Deterministic IDs: By using TenantItemId, the game can predictably derive the same Sui ObjectID for a specific game asset across different transactions.
• Uniqueness Guarantee: The combination of tenant and item ID ensures that no two assets can share the same identity, even if they are different types of objects (e.g., a character and a solar array).

3. Integration with Object Registry

While in_game_id.move defines the format of the identity, the object_registry.move module uses it to manage the actual on-chain existence of these objects.

sequenceDiagram
    participant Game as Game Engine
    participant ID as in_game_id.move
    participant Registry as object_registry.move

    Game->>ID: Create TenantItemId(tenant, item)
    ID-->>Game: Return TenantItemId struct
    Game->>Registry: object_exists(Registry, TenantItemId)
    Registry-->>Game: true / false

• Registry Key: The ObjectRegistry uses TenantItemId as the key to verify if a game asset has already been instantiated on-chain.
• Global Singleton: The registry is a shared object, allowing any system to verify the identity and existence of any asset.

4. Why This Pattern Matters

• Off-Chain Alignment: It allows EVE Frontier’s backend databases to stay perfectly synchronized with the blockchain without needing to store mapping tables for every single ObjectID.
• Namespace Isolation: The tenant_id allows multiple “worlds” or administrative layers to exist on the same smart contract without ID collisions.
• Minimal Footprint: The primitive itself is extremely lightweight, focusing solely on the data structure and basic creation logic, adhering to the principle of Atomic Logic for Primitives.