Claim stakes

A claim stake is a player’s claim on a celestial body, producing resources over time rather than in a single action.

A Claim Stake turns land into a base

A Claim Stake lets a player take an available plot on a planet controlled by their faction. They can build extraction, processing, power, and other facilities there, turning empty land into a working base. Placing the stake costs resources and keeping the plot requires ongoing ATLAS rent. If the player’s faction loses control of the system, the buildings can be lost and the Claim Stake asset is returned.

Reading them

By owner, which is the usual direction:

const stakes = await character.claimStakes.all();

Or by the body, when you want to know who holds a particular place:

const stakes = await sage.claimStakes.byBody(bodyAddress);

Lifecycle is a state, not a flag

A stake’s state.kind is one of design, active, or deactivated. Those are genuinely different situations rather than degrees of the same one:

if (stake.state.kind === 'active') {
  // Producing. Other kinds are not.
}

Reading a stake and assuming it is producing is the mistake this shape exists to prevent.

Instances have no derivable address

Like crafting processes, claim stake instances cannot be computed from the character and the body — the address is assigned at creation. That is why the reads are byCharacter and byBody rather than a derivation, and why finding one you have no reference to needs discovery.

Gotchas

A stake in design is not yet producing. It exists, it is yours, and it yields nothing. Filter on state before summing output.

Capacity and yield come from definitions. What a stake produces depends on the body and the Game account’s rules, not on fields stored in the stake account alone.

A body can hold stakes from several players. byBody returns an array for that reason.

Reference

• claim-stakes — every export in this entry
• world — the bodies stakes are placed on
• crafting — the other capability with non-derivable instances