https://f76f6398.frontier-scetrov-live.pages.dev/develop/index.html If you are new to developing Smart Contracts, I strongly recommended reading the Getting Started section first. World Contracts Introduction to Smart Contracts Interfacing with the World Object Model Ownership Model Smart Assemblies Overview Builder Scaffold Sui Basics Coordinate Systems Frontier World API Static Data 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. Hugo en-us Fri, 13 Mar 2026 00:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-contracts/index.html Fri, 13 Mar 2026 00:00:00 +0000 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. https://f76f6398.frontier-scetrov-live.pages.dev/develop/smart-contracts-intro/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/smart-contracts-intro/index.html Overview of smart contracts in EVE Frontier — what they are, how Frontier uses them, and key Move patterns. https://f76f6398.frontier-scetrov-live.pages.dev/develop/interfacing-with-world/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/interfacing-with-world/index.html How to read and write on-chain state in the EVE Frontier world using the Sui TypeScript SDK, GraphQL, and gRPC. https://f76f6398.frontier-scetrov-live.pages.dev/develop/object-model/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/object-model/index.html How in-game items are deterministically mapped to Sui objects using the ObjectRegistry and TenantItemId system. https://f76f6398.frontier-scetrov-live.pages.dev/develop/ownership-model/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/ownership-model/index.html Capability-based access control hierarchy in EVE Frontier — GovernorCap, AdminACL, OwnerCap, and the borrow-use-return pattern. https://f76f6398.frontier-scetrov-live.pages.dev/develop/smart-assemblies-intro/index.html Sat, 21 Feb 2026 12:23:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/smart-assemblies-intro/index.html Introduction to modding programmable Smart Assemblies in EVE Frontier — Gates, Storage Units, Turrets, and the extension pattern. https://f76f6398.frontier-scetrov-live.pages.dev/develop/builder-scaffold/index.html Sat, 28 Feb 2026 12:00:00 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/builder-scaffold/index.html Templates and tools for building on EVE Frontier — Docker and host flows, Move contract examples, dApp template, and zkLogin CLI. https://f76f6398.frontier-scetrov-live.pages.dev/develop/sui-basics/index.html Thu, 09 Oct 2025 20:50:00 +0100 https://f76f6398.frontier-scetrov-live.pages.dev/develop/sui-basics/index.html Introduction The Sui Blockchain is a Layer-1 smart contract platform developed by Mysten Labs, designed to deliver low-latency, horizontally scalable transaction processing. Unlike the majority of blockchains that rely on total ordering of all transactions, Sui introduces an object-centric data model built around a directed acyclic graph, or DAG, combined with Byzantine-Fault-Tolerant (BFT) consensus mechanisms. This architectural shift allows the network to execute independent transactions in parallel without consensus bottlenecks, improving throughput and responsiveness especially suited to games. Sui is built in Rust and leveraging the Move programming language, Sui offers strong safety guarantees through Move’s resource-oriented type system, ensuring exactly one of an object exists - i.e. preventing inadvertent duping or loss. https://f76f6398.frontier-scetrov-live.pages.dev/develop/coordinate_systems/index.html Mon, 16 Jun 2025 21:20:00 +0100 https://f76f6398.frontier-scetrov-live.pages.dev/develop/coordinate_systems/index.html The EVE Frontier game happens in three-dimensional space. Every object has a corresponding vector (x, y, z), measured in meters. Each component can be positive or negative. The origin (0, 0, 0) is close to the galactic center. There are five distinct sources of three dimensional coordinates: The /v2/solarsystems and /v2/solarsystems/{id} endpoints in the World API, in addition to the solarSystem object on various other payloads this states the coordinates in absolute terms relative to the galactic center, however only in limited precision (double-precision floats have a 52-bit mantissa, corresponding to roughly 15–17 decimal digits of precision, stored as an 8-byte value). The location of individual assemblies in the /v2/smartassemblies and /v2/smartassemblies/{id} endpoints in the World API, these are relative to the center of the local star and have a similar limited precision (double-precision floats have a 52-bit mantissa, corresponding to roughly 15–17 decimal digits of precision). The location of individual assemblies on-chain in the Location table; these are highly precise absolute values stored as uint256; however, they have had 1 << 255 added to them. The starmapcache.pickle resource file contains the absolute positions of all solar systems in the map with a very high degree of precision, however as it exists within the ResFiles it needs to be decoded from Python Pickle format a process that must be repeated each time the star map is updated. The mapObjects.db resource file contains the relative (to the star) position of celestial objects (Planets, Moons) again as they are in the ResFiles and needs to be read using a SQLite database browser or by writing code to extract the rows from the tables. Note Many tools struggle with the axes employed by the CCP data as it results in the stars being rended with the plane of the galaxy in an Up-Down orientation which seems unnatural and can result in Gimbal Lock. This fairly easy to fix, as [WOLF] lacal found out on Discord: https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-api/index.html Wed, 11 Jun 2025 17:04:29 +0000 https://f76f6398.frontier-scetrov-live.pages.dev/develop/world-api/index.html CCP have published a REST API giving access to a wide range of endpoints, in each case they have published an OpenAPI compliant specification: Stillness (Closed Alpha): https://blockchain-gateway-stillness.live.tech.evefrontier.com/ (Swagger) Nova (Builder Sandbox): https://world-api-nova.live.tech.evefrontier.com/ (Swagger) API Reference (Stillness) The following reference is auto-generated from the Stillness Swagger spec (data/world-api-stillness.json). API Version: v1.0.1 |  Spec: Swagger 2.0 Meta GET /config get config retrieve all the config needed to connect to our services Responses StatusDescriptionSchema 200 OK models.ChainConfig 400 Bad Request — 404 Not Found — 500 Internal Server Error — GET /health health endpoint https://f76f6398.frontier-scetrov-live.pages.dev/develop/static-data/index.html Sun, 29 Jun 2025 13:10:00 +0100 https://f76f6398.frontier-scetrov-live.pages.dev/develop/static-data/index.html Static Data is the data that is downloaded by the EVE Frontier Launcher and used by the client to display information in the game without downloading information from servers. Inherently static data is unchanging, and is stored on-disk in an immutable form, however the use of that data will vary with patches. Important The availability and correctness of these files is entirely down to CCP, if they choose to remove something from static data, change the format or use it in a different way they will likely do so without informing the community. These are effectively internal data structures and not intended to be destructured and read.