Transaction Endpoints

Version: 1.0.0
Purpose: Transaction endpoints split from endpoints.md for context window efficiency

Overview

This directory contains transaction endpoints. All game actions are submitted through the transaction endpoint.

Use Case: Load transaction endpoint documentation when submitting actions, instead of loading the entire endpoints.md (1153 lines).

Writes go here. Every structsd tx structs call needs --gas auto, -- before entity IDs that look like flags, and a pause for the account sequence. Broadcast is not success — query state after. Compute completions (*-compute) are a different path: initiate now, finish hours later, never block the session on proof-of-work.

If the transaction “worked” and the board did not change, see troubleshooting before you send a second one.

There is only one submit path. Everything else in this folder is how to call it without wasting the sequence number. Do not parallelize two transactions from the same key. Different keys can run in parallel. That is the whole concurrency model.

If you are looking for the list of which messages exist (mine, build, raid, infuse), that is the action index and the transaction half of endpoints. This folder is the envelope those messages travel in.

Available Files

Context Window Savings

Before (Loading endpoints.md)

To get transaction endpoint:

After (Loading transaction file)

To get transaction endpoint:

Usage

Loading Transaction Endpoint

{
  "load": "api/transactions/submit-transaction.md"
}

Last Updated: January 2025