CitadelAI Docs
  • BACKGROUND OF THE PROJECT
    • 2023 is the first year of AI LLM
    • The synergistic emergence of AI and cryptocurrency
    • Robots and artificial intelligence are so powerful
  • PROJECT INTRODUCTION
    • Why artificial intelligence?
    • What is Citadel?
    • About Citadel AI
    • Why Citadel's new license to use OpenAI's ChatGPT
  • CCAI ROBOT
    • Robotics and artificial intelligence in the context of investment portfolios
    • CCAI Robot Introduce
    • CCAI Robot application
    • CCAI Robot and encryption
  • CCAI CHAIN
    • CCAI Chain Introduction
    • DPoS consensus mechanism
    • PoT consensus mechanism
    • AI zero-knowledge learning
    • CCAI-SUPER Model
  • Ecosystem Development
    • CCAI Game
    • Quantitative Financial Management
    • Lifestyle and Entertainment
    • SocialFi
  • Others
    • Team Structure
    • CCAI Tokenomics
    • Development Roadmap
    • Disclaimer
    • Risk Warning
Powered by GitBook
On this page
  1. CCAI CHAIN

PoT consensus mechanism

PreviousDPoS consensus mechanismNextAI zero-knowledge learning

Last updated 8 months ago

In addition, we designed a PoT (Proof Of Training) consensus mechanism for model training and operation.

The PoT consensus mechanism is divided into the following stages:

  • Initialize: Each node publishes the model and data they want to train to the network.

  • Assign tasks: Tasks are assigned to various nodes in the network according to a certain strategy (for example, random or resource-based). The historical performance and reputation of nodes are taken into account when assigning tasks. For example, if a node has shown high efficiency and honesty in past training tasks, it may be prioritized in future task allocations. Efficient nodes should be given priority to AI models that run in real time. There is no guarantee that nodes required by the operating environment will only be used for model training.

  • Train: Each node uses their computing resources to start a training task, while recording key training metrics (e.g., loss per iteration, GPU utilization, etc.) in a secure log. In order to prevent nodes from tampering with training indicators, zero-knowledge proof technology is used to verify the correctness of the training process.