Alliance Games Litepaper
  • Introducing Alliance Games
    • Introducing Alliance Games
    • Problem Statement
    • Mission
    • Vision
  • Product Offerings
    • Game Cloud
      • Asset Vault
      • GameFront
      • NetFlow
    • Game AI
  • Technical Structure
    • Overview
    • Worker Nodes
    • Edge Node
      • Overview
      • Key Features
      • Reward Mechanism
    • Micro Node
      • Overview
      • Key Features
      • Reward Mechanism
    • Lite Node
      • Overview
      • Key Features
      • Reward Mechanism
    • Verifier Nodes
    • Delegator Nodes
    • Security Features
  • API and SDKs
    • API and SDKs
  • Tooling
    • Tooling
    • Node Provider Dashboard
    • Game Developer Dashboard
    • User Dashboard
  • TOKENOMICS
    • Tokenomics
Powered by GitBook
On this page
  1. Technical Structure

Verifier Nodes

PreviousReward MechanismNextDelegator Nodes

Last updated 6 months ago

In order to ensure that worker nodes comply with protocol requirements and are executing the tasks correctly, Alliance Games also has verifier nodes in the network. To become a verifier node, the requirement would be more stringent in terms of tokens at stake as well as machine types; since verifier nodes are the crucial component in securing the network.

To validate transactions, verifier nodes would perform two actions. Firstly, they would randomly select tasks that are being executed in the network, run the same tasks and compare the results that are being submitted to the blockchain. In the meantime, they would also create dummy tasks and include them in the tasks pool; after worker nodes complete the dummy tasks, verifier nodes could compare the results and seek for discrepancies, which implies misbehavior of worker nodes. Taking data storage as an example: after a worker node stores a file locally, it will generate a hash or zk proof of the file and upload the proof to blockchain. Verifier nodes validate the job by storing the same file and producing a proof. If the proofs do not match, worker nodes will be flagged and are subjected to penalties.

Verifier nodes also need to download a client, which encapsulates the test scripts and automates the validation process.