Forge Pool

Appearance

Providers Guide ​

Operating Execution Nodes on the Planetary Network ​

Forge Pool Providers contribute execution capacity to the deterministic compute network.

This guide explains how to:

  1. Register a node
  2. Install and configure the Forge Agent
  3. Understand trust boundaries
  4. Monitor performance and earnings
  5. Operate reliably in production

Why Become a Provider? ​

Providers supply compute capacity to a globally distributed execution system.

When your node executes billable workloads:

  • your hardware performs deterministic shard execution
  • results contribute to institutional-grade computation
  • credits are earned and recorded in the ledger

Idle hardware becomes structured execution capacity.

This is not speculative mining. It is compensated execution of real workloads.

See: → Credits → Payouts

1. Node Registration Model ​

Nodes authenticate using Node Tokens.

Each Node Token:

  • is scoped to your organization
  • defines billing association
  • establishes trust boundary
  • can limit number of nodes
  • can be revoked at any time

Node Tokens are generated in:


HQ → My Nodes

https://forgepool.io/hq/nodes/mine

2. Generate a Node Token ​

In My Nodes:

  1. Click Generate Node Token
  2. Provide:
    • Token label (optional, e.g. datacenter-1)
    • Max nodes (optional)
  3. Click Generate

You will receive:

  • a NODE_TOKEN (prefix ntk_)
  • installation commands

The token must remain private.

3. Install the Agent (Linux) ​

bash
curl -sL https://forgepool.io/install.sh | sudo bash

During installation you will configure:

  • Node name
  • Region
  • Visibility (PUBLIC / PRIVATE)
  • Allow BILLABLE operations
  • Allow TEST operations
  • NODE_TOKEN

Installer actions:

  • downloads agent binary
  • creates /opt/forge-agent
  • writes .env
  • configures systemd
  • starts the service

4. Install the Agent (Windows) ​

Run PowerShell as Administrator:

powershell
Set-ExecutionPolicy Bypass -Scope Process -Force
iwr https://forgepool.io/install.ps1 -UseBasicParsing | iex

Configuration prompts are identical.

5. Trust & Authentication Model ​

NODE_TOKEN:

  • binds node to organization
  • authenticates against Hub
  • connects execution output to ledger
  • defines billing eligibility

If compromised:

  1. Revoke token in HQ
  2. Generate a new one
  3. Update .env
  4. Restart agent

Agents cannot join without valid token.

6. Node Configuration ​

The .env file includes:

  • NODE_NAME
  • NODE_REGION
  • NODE_VISIBILITY
  • ALLOW_BILLABLE_OPS
  • ALLOW_TEST_OPS
  • NODE_TOKEN

NODE_VISIBILITY ​

  • PUBLIC → eligible for global workloads
  • PRIVATE → restricted to organization / private hubs

ALLOW_BILLABLE_OPS ​

  • true → eligible for compensated workloads
  • false → excluded from billable jobs

ALLOW_TEST_OPS ​

  • true → can execute sandbox workloads
  • false → production-only

These flags allow risk and revenue control.

7. Node Lifecycle ​

After startup:

  1. Agent connects to Hub
  2. Token validated
  3. Public key registered
  4. Hardware capabilities reported
  5. Node appears in HQ
  6. Scheduler assigns compatible shards

Execution begins automatically when workloads match your configuration.

8. Earnings Model ​

Providers earn credits for executing shards.

Compensation depends on:

  • workload type
  • execution duration
  • hardware profile (CPU / GPU)
  • verification participation
  • uptime reliability

Credits accumulate in your provider ledger.

Payout options and thresholds: → Payouts

Stable, reliable nodes receive:

  • higher scheduling priority
  • greater workload allocation
  • improved credit flow

Reliability directly influences earnings.

9. Monitoring & Performance ​

In:

HQ → Providers → Nodes

You can inspect:

  • online status
  • health score
  • shard throughput
  • verification ratio
  • latency metrics
  • credits earned

Health score reflects:

  • uptime
  • shard correctness
  • verification consistency

High-quality nodes become preferred execution targets.

10. Updating or Rotating Token ​

To rotate token:

  1. Update NODE_TOKEN in .env
  2. Restart:
bash
sudo systemctl restart forge-agent

Node reconnects under new trust context.

11. Operational Best Practices ​

  • Use stable hardware
  • Avoid aggressive overclocking
  • Ensure consistent uptime
  • Monitor logs:
bash
journalctl -u forge-agent -f
  • Separate production vs test nodes
  • Use PRIVATE visibility for internal compute
  • Maintain secure host environment

Provider Philosophy ​

Providers are not miners.

They are execution participants in a deterministic compute substrate.

Your hardware contributes to:

  • institutional risk simulations
  • climate ensembles
  • probabilistic logistics
  • numeric pipelines
  • distributed compute workloads

Execution capacity is compensated because it produces verifiable value.

Providers form the execution backbone of Forge Pool.