Node Operation Rules

This page explains the responsibilities of participants after they have been selected for the Astar Peers Program.

1. Operate an Archive Node

The node registered with the program must be an Astar archive node.

Participants are responsible for maintaining the machine, operating system, node software, storage, and internet connection needed to keep the node synchronized and active.

2. Connect to Polkadot Telemetry

Every participating node must be connected to Polkadot Telemetry.

Telemetry allows the program to confirm that the node is visible, synchronized, and actively participating in the network. Participants should regularly check that:

  • Their node appears under the expected node name
  • The node remains synchronized
  • The node has not disappeared because of a service, machine, or connection failure

3. Aim for at Least 80% Uptime

Continuous 100% uptime is not required. However, participants are expected to operate their nodes without major interruptions and maintain at least 80% uptime as the program target.

Reward eligibility is reviewed using the previous month's operating status. The current reward wording grants the full availability-based reward when uptime is 80% or more and a reduced reward when it is below 80%.

See Rewards and Payments for the payment categories.

4. Monitor the Node

Participants should regularly confirm:

  • The machine is running
  • The node process or service is active
  • The node is synchronized
  • Sufficient storage remains available
  • Memory usage is within a stable range
  • The node remains visible in Polkadot Telemetry

The program does not require enterprise-level monitoring, but participants must be able to identify and respond to a stopped or unhealthy node.

5. Handle Interruptions and Resynchronization

If a node stops because of a machine failure, software problem, storage issue, or network interruption, the participant should begin recovery as soon as reasonably possible.

A node that is actively being restored or resynchronized may receive 30% of the standard reward for the relevant assessment period.

Participants should keep the program administrator informed when:

  • A node will be offline for an extended period
  • Hardware must be repaired or replaced
  • A full resynchronization is required
  • The node cannot return to service

6. Avoid Long-Term Inactivity

No reward is provided when a node is not operating or is considered inactive.

Nodes may also become ineligible for rewards if they:

  • Remain inactive for a long period
  • Go offline frequently
  • Repeatedly fail to maintain synchronization

7. Register an On-Chain Identity

Participants must register the required on-chain identity for the Astar account used in the program.

Follow the official Astar documentation to register your on-chain identity.

If the required on-chain identity is not registered, no reward will be provided, even if the node meets the uptime requirements.

If multiple reward conditions apply, the priority rules defined in the Rewards and Payments page will be used.

8. Participate in Program Reviews

Regular reviews are conducted to evaluate the current season’s achievements, the remaining reward budget, and any continuation proposals in preparation for the next season.

Monthly Operating Checklist

  • [ ] My archive node is running.
  • [ ] My node is synchronized.
  • [ ] My node is visible in Polkadot Telemetry.
  • [ ] My machine has sufficient free storage.
  • [ ] My node has not experienced an unexplained long-term outage.
  • [ ] I have reported any major interruption or resynchronization.
  • [ ] My required on-chain identity is registered.