Galagames nodes for licensed workloads and daily rewards
Galagames nodes run licensed software workloads that support the Gala ecosystem and qualify eligible operators for rewards. A license grants access to a particular workload, while the Gala Node client supplies the software that runs it. Founder’s Nodes support the wider ecosystem; game-specific nodes have narrower roles and separate requirements. Daily reward eligibility involves recorded workload activity and the applicable distribution rules. For Founder’s Nodes, eligible GALA balances became an additional reward input in June 2025. Operators also manage the host’s availability and the workload’s platform requirements, which can differ from the base client’s requirements.
Which license does a Gala Node workload require?
Each workload requires its matching node license, and the installed client must run that workload to earn operating credit. Installing the software alone does not establish eligibility. The account’s available licenses identify the workloads that it can support, and the selected program determines the work that the machine performs. A Founder’s Node license and a game-specific license authorize different participation.
Founder’s Nodes provide ecosystem support and participate in governance. Common Ground World’s V2 Node Workload NFT enables guild creation and management when held in a GalaChain wallet. Last Expedition nodes host game servers, with server profiles holding their configuration. These roles explain why a general node-client installation cannot establish compatibility or reward rules for every workload.
The client connects account licenses with workload programs
The Gala Node client launches workload programs and manages their network connection, while pairing links their contributions to a license. A workload is a separate program inside that installation. This arrangement lets one client support different licensed tasks.
An API key connects the software with the account’s node information. The client uses it to identify available licenses and attribute participation. Selecting a workload enables that program within the client. The account’s license inventory, the selected workload, and the machine’s connection each affect whether the installation can contribute under that license.
Each license pairs with one node at a time. A node can pair with one license of each workload type.
Uptime points and eligible balances govern different reward inputs
The workload point system introduced in 2024 assigns Founder’s Node credit in proportion to recorded online time. Its May 2024 schedule specifies up to 4 points over 24 hours. This replaced the earlier pass-or-fail six-hour model, so an old minimum-uptime description does not explain the later points calculation. In the point-based distribution, a node’s share reflects its points relative to the total earned across participating nodes. A point therefore has no fixed GALA value.
Founder’s Node rewards gained a separate balance requirement on June 16, 2025. The June 2025 holdings policy sets full-reward qualification at 1 000 000 eligible GALA per Founder’s Node. Smaller eligible holdings scale rewards proportionally. Uptime establishes operating credit, and the balance policy supplies an additional reward condition. The June 2025 plan also described GSTAKE as an alternative qualification token, with separate later phases for locking and lending.
A daily distribution appears in inventory as a GalaChain mint allowance before redemption. The allowance records an entitlement to tokens; minting creates the corresponding on-chain tokens. That status differs from both the node license and the client’s runtime.
GALA holdings and eligible liquidity positions
Eligible GALA can come from holdings or designated liquidity positions under the December 2025 snapshot policy. That update retained the per-node qualification requirement. The listed pool options concern eligible GalaSwap positions, and only their GALA component contributes toward the node balance.
| Eligible balance option | GALA included in snapshot | Qualification boundary |
|---|---|---|
| Direct GALA holdings | GalaChain wallet GALA or mint allowances | A node license remains necessary |
| GALA / ETH pool | GALA portion | ETH portion excluded |
| GALA / BTC pool | GALA portion | BTC portion excluded |
| GALA / XRP pool | GALA portion | XRP portion excluded |
| GALA / SOL pool | GALA portion | SOL portion excluded |
| GALA / USDT pool | GALA portion | USDT portion excluded |
| GALA / USDC pool | GALA portion | USDC portion excluded |
Pool fees and node rewards arise from different mechanisms, and liquidity can incur impermanent loss as prices change. The position’s total market value is not itself a GALA quantity. Changes in pool composition can alter the GALA amount that a later snapshot counts.
What hardware supports a Gala Node installation?
A standard client installation needs compatible hardware, a supported operating system, Docker, and a stable connection, with extra resources for demanding workloads. The published Gala Node client baseline specifies 4 GB of RAM. It also lists 2 CPU cores and 60 GB of disk space. The client supports Windows desktop, macOS, and 64-bit Linux on operating-system releases that their vendors still support.
The Last Expedition game-server workload has a higher baseline: 8 GB of RAM and 4 CPU cores, with 60 GB of disk space. It requires x86/x64 hardware and does not support macOS or ARM processors. Without correctly configured port forwarding, the Last Expedition workload will not start. The base client’s support for Apple ARM processors therefore does not establish Last Expedition compatibility. Windows installations also need CPU virtualization and Docker’s Linux environment; the Windows installation guide excludes Windows Server and Windows 10 Home.
Workload status distinguishes online, standby, and offline
The dashboard reports each workload’s state, so a running client can coexist with a workload that has no active license pairing. Green indicates online, orange indicates standby, and red indicates offline. Standby means that the workload is running while the available licenses already pair with other nodes.
Node Last Seen concerns the machine’s connection, while Workload Last Seen concerns a particular workload. These fields can describe different problems. A responsive host can still have a failing workload, and its overall availability does not establish that every selected program contributed. Online Today and Online Yesterday provide additional operating-time context alongside the individual workload indicators.
Client logs help separate a software connection problem from a workload-specific failure when the dashboard shows different states.
Local computers and virtual servers change the operating burden
A home computer uses the operator’s hardware and internet connection; a virtual private server moves computation to rented infrastructure. The home host must stay awake while its workload operates. A virtual server adds hosting charges and provider constraints around resources or network access. Different workload types can share an installation when its resources support them, while additional licenses of the same type need separate machines. Relevant costs include electricity, hosting where used, and applicable asset-operation fees. Daily GALA quantities and cash expenses use different units, so token-price changes affect their monetary relationship.
How does transferring a license affect node operation?
A transfer-ready Founder’s Node cannot operate or receive daily GALA distributions until reactivation. Common Ground World Nodes remained reward-eligible in the transfer-ready state under the October 2024 framework. The node type therefore changes how that state affects eligibility.
A Founder’s Node license can stay active as either a GalaChain allowance or a redeemed NFT before transfer readiness. Redemption alone leaves the NFT non-transferable. Reactivation restores operating eligibility under the workload’s applicable requirements.
The October 2024 framework includes fees for tokenization, transfer preparation, and reactivation, alongside applicable GalaChain transaction fees paid in GALA. The recipient acquires the operating right and assumes responsibility for its own installation. Under this framework, operation requires the NFT to be in the wallet associated with that recipient’s Gala account.
Founder’s Node votes can change reward policy
Founder’s Node license holders can participate in ecosystem polls, including decisions that adjust reward distribution. The April 30, 2026 vote result approved replacing gap-based emissions with a disinflationary model and gas-fee sharing. The approved design allocated 50% of GalaChain gas fees to node operators, with the remaining share burned. That percentage describes a network-wide allocation, rather than a fixed payment to each license. The approval authorized the transition and identified implementation as the next stage. Implementation determines when the new accounting applies, while the applicable eligibility and distribution rules determine individual node credits.
Things people ask about Galagames nodes
Does a more powerful computer earn extra Founder’s Node uptime points?
The May 2024 workload formula awards uptime points from recorded online seconds, without a CPU-performance term. More computing capacity helps meet the requirements of demanding workloads. It does not change the published conversion between operating time and Founder’s Node uptime points.
Can a Gala Node API key move GALA or NFTs from my wallet?
The Gala Node API key cannot move NFTs or cryptocurrencies from the associated wallet. It lets the client retrieve node-license information, configure workloads, and attribute participation to the account. Wallet asset transfers require separate authorization, so the node credential and wallet credentials have different access scopes.
Why can the client and workload show different version numbers?
The client and each workload are separate programs with separate releases. Workload updates occur automatically, while client updates usually require operator action. A version number identifies the particular program that displays it, so the client’s version and a workload’s version do not need to match.
Can I restart a Gala Node through its dashboard?
Node Management provides remote stop and restart controls on Gala Node software version 3.3.5 or later. The interface also exposes workload selection and certain network-port settings. These controls manage the node software remotely without requiring direct interaction with its host computer.
What recovery is available after sending a Founder’s Node NFT to the wrong wallet?
The Founder’s Node transfer feature provides no recovery after a completed transfer. The recipient receives the legal right to operate that node. Confirming the destination wallet before completing the transfer matters because moving the NFT also moves the associated operating right.
Must a Founder’s Node NFT be bridged to Ethereum before transfer?
The Founder’s Node license-transfer process runs on GalaChain and requires no Ethereum bridge. NFT redemption, the transfer-ready setting, and reactivation belong to that GalaChain license framework. The October 2024 framework did not support bridging Founder’s Node NFTs to Ethereum.
Where are offline email notifications configured for Gala Node operators?
Offline email notifications are managed in the account’s Notifications settings. The node dashboard separately shows last-seen information and workload status. An email alerts the operator to node availability; it does not establish the reward amount credited for that day.
How are multiple Founder’s Node licenses handled in a vote?
The voting interface lets an account allocate all or some of its Founder’s Node licenses to the selected poll option. For the April 2026 economic vote, every active Founder’s Node carried one vote. This voting unit concerns node licenses, rather than the account’s GALA quantity.