https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/index.html 1. Architectural Strategy: The Three-Layer Model The solution adopts a three-layer architecture to balance core “digital physics” with player-driven moddability. This design emphasizes composition over inheritance. graph TD subgraph Layer3 ["Layer 3: Player Extensions"] Mod["Third-Party Smart Contracts"] end subgraph Layer2 ["Layer 2: Game-Defined Assemblies"] SU["Storage Unit"] Gate["Stargate"] Turret["Smart Turret"] MU["Manufacturing Unit"] end subgraph Layer1 ["Layer 1: Composable Primitives"] Loc["location.move"] Inv["inventory.move"] Fuel["fuel.move"] Stat["status.move"] Energy["energy.move"] Meta["metadata.move"] ID["in_game_id.move"] end Layer3 -- Authenticated via Witness --> Layer2 Layer2 -- Composed of --> Layer1 Layer 1: Composable Primitives These are low-level, focused Move modules that implement fundamental game logic. Hugo en-us Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/events/index.html Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/events/index.html This page provides a complete index of every event emitted by the world-contracts. Events are the primary mechanism for off-chain indexers, game clients, and third-party tools to observe state changes on-chain. All event structs carry the has copy, drop abilities, and are emitted via Sui’s event::emit. Access Control Source: access/access_control.move Full documentation: access_control.move OwnerCapCreatedEvent Emitted when a new OwnerCap is created for an object. Field Type Description owner_cap_id ID The ID of the newly created OwnerCap. authorized_object_id ID The ID of the object this capability authorizes. OwnerCapTransferred Emitted when an OwnerCap is transferred to a new owner. https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/primitives/index.html Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/primitives/index.html In the EVE Frontier world-contracts architecture, a Primitive is a foundational building block that implements low-level game mechanics and data structures for a specific domain. They represent the “digital physics” of the game world, designed to be composed into more complex structures. 1. Role in the Three-Layer Architecture Primitives reside at Layer 1, serving as the base for all higher-level interactions. graph TD subgraph Layer2 [Layer 2: Assemblies] Assembly[Smart Assembly] end subgraph Layer1 [Layer 1: Primitives] direction LR P1[Energy] P2[Fuel] P3[Location] P4[Inventory] end Assembly --> P1 Assembly --> P2 Assembly --> P3 Assembly --> P4 Layer 1 (Primitives): Focused modules implementing logic like spatial positioning, resource management, and item storage. Layer 2 (Assemblies): Complex game entities (e.g., Stargates or Storage Units) created by composing multiple Primitives. Layer 3 (Extensions): Custom player-built logic that interacts with Assemblies. 2. Key Characteristics of a Primitive The design of a Primitive follows strict principles to ensure the game remains secure and scalable: https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/assemblies/index.html Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/assemblies/index.html The contracts/world/sources/assemblies/ folder contains the Layer 2: Game-Defined Assemblies of the EVE Frontier architecture. These modules act as the orchestration layer, composing various Layer 1 Primitives (like fuel, energy, and inventory) into functional in-game structures. Folder Overview: Core Components This folder defines the “Smart Assemblies” that players interact with on-chain. Each assembly is implemented as a Sui Shared Object, allowing for concurrent access by multiple players and game systems. File Description assembly.move The base logic for all generalized assemblies, handling fundamental lifecycle operations like anchoring, un-anchoring, and toggling online/offline states. storage_unit.move A specialized assembly representing a programmable, on-chain storage structure that allows players to manage items under custom-designed rules. gate.move A programmable structure enabling travel across space, with support for linking, distance verification, and extension-controlled access via jump permits. turret.move A programmable defense structure for space control, with support for custom targeting priority logic and energy reservation. 1. assembly.move: The Generalized Framework This module provides the template for any physical structure deployed in the game world. https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/entities/index.html Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/entities/index.html Entities are predominately used to manage data persistence and shared state in the EVE Frontier world. They are the primary way to store configuration, track state across transactions, and enable cross-assembly interaction. This chapter covers the core entity patterns used across world contracts, including: killmail.move character.move object_registry.move Tip Use the menu on the left hand side to find the article you are looking for. You can also use search at the top to search for specific terms. https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/crypto/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/crypto/index.html The contracts/world/sources/crypto/ folder contains cryptographic utility modules used across the EVE Frontier world contracts. These modules provide signature verification and address derivation functionality essential for validating off-chain proofs on-chain. Folder Overview File Description sig_verify.move Ed25519 signature verification and Sui address derivation for validating off-chain signed messages (e.g., location proofs). sig_verify.move Tip Use the menu on the left hand side to find the article you are looking for. You can also use search at the top to search for specific terms. https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/extension-examples/index.html Sun, 08 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/extension-examples/index.html The contracts/extension_examples/ package contains Layer 3: Player Extension examples that demonstrate how builders can extend EVE Frontier assembly behavior using the typed witness pattern. These are reference implementations showing common extension patterns. How Extensions Work Extensions are custom Move packages that interact with world assemblies (Gates, Storage Units, Turrets) through a typed authentication witness pattern: The assembly owner registers an extension’s witness type on their assembly. The extension module creates instances of its witness type to call assembly functions. The assembly verifies the witness type is registered before allowing the operation. sequenceDiagram participant Owner participant Assembly participant Extension Owner->>Assembly: authorize_extension of Auth Note over Assembly: Auth TypeName added to allowlist participant Player Player->>Extension: call custom entry function Extension->>Assembly: pass Auth witness Assembly->>Assembly: verify Auth is registered Assembly-->>Extension: operation succeeds Modules in This Section Module Description config.move Shared configuration object with dynamic field helpers for extension rule storage. tribe_permit.move Gate extension using shared ExtensionConfig — tribe-based jump permits with dynamic fields. corpse_gate_bounty.move Combined Storage Unit + Gate extension — bounty collection grants gate access. turret.move Turret extension — custom targeting priority logic using the OnlineReceipt hot potato pattern. Tip These examples can be used as starting points for your own extensions. The builder-scaffold repository provides a complete project template for building and testing extensions locally. https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/access/access_control.move/index.html Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/access/access_control.move/index.html Deep dive into the hierarchical capability model and the digital laws governing object mutation in EVE Frontier. https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/world.move/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/world.move/index.html The world.move module is the root entry point of the EVE Frontier world contracts package. It is responsible for bootstrapping the entire access control hierarchy by creating the GovernorCap during package initialization. Core Component classDiagram class GovernorCap { +UID id +address governor } GovernorCap The GovernorCap is the top-level authority in the EVE Frontier access control hierarchy. It is created once during the package init function and transferred to the deployer’s address.