Star Atlas terms

Terms as this SDK uses them. Game vocabulary is checked against the game; Solana vocabulary is deliberately kept to the minimum you need.

Growing with the guides

This glossary is seeded from the introduction pages. It fills out as the capability guides land, so terms specific to mining, crafting, or markets are not here yet.

Game

SAGE — the part of Star Atlas where fleets fly, mine, craft, and trade. The SDK reads SAGE state.

C4 — the current generation of SAGE. Runs on its own program with its own account layouts; earlier generations are not compatible.

z.ink — the public test realm SAGE C4 runs on. A separate network from Solana mainnet.

Profile — a player’s on-chain identity. Created by the player, so there is no way to derive it from a wallet address; it has to be discovered or supplied.

Character — a profile’s presence inside SAGE. Owns fleets and accrues progress. One per profile.

Fleet — a group of ships travelling together. Ships move as fleets, never individually. A fleet has a state: docked, in transit, mining, and so on.

Starbase — a station where fleets dock, trade, and craft. Shared starbase data belongs to the world; a player’s own state at a starbase is separate.

Claim stake — a claim on a planet or other body that yields resources over time.

ATLAS — the in-game currency used for rewards and market settlement.

Faction — one of the three allegiances: ONI, MUD, and Ustur. Affects standing, economics, and diplomacy.

Solana

Account — a slot of on-chain storage with an address, an owning program, and raw bytes. Everything the SDK reads is an account.

Address — the identifier for an account. The SDK uses the Address type from @solana/kit.

Program — deployed on-chain code. SAGE C4 is one program, and it owns the accounts the SDK reads.

RPC endpoint — a server that answers questions about the chain. You supply one; see setting up your RPC.

PDA — an address derived deterministically from known inputs rather than stored. When an account has one, it can be computed instead of searched for. Several SAGE account types do not have one, which is why some lookups need discovery.

Discriminator — the leading bytes identifying an account’s type. The SDK checks it before decoding, so a wrong account fails cleanly.