ZopToken Docs

English

简体中文

English

简体中文

Theme

How the Platform Works ​

The basic workflow of ZopToken can be summarized in six steps:

flowchart TD
    A(User provides device) --> B(Device connects to the ZopToken network)
    B --> C(Platform identifies device status and resource capabilities)
    C --> D(Platform assigns suitable AI workloads)
    D --> E(Device executes tasks and reports results)
    E --> F(Platform records task results and revenue data)

1. Device Onboarding ​

Device providers complete device onboarding through the macOS App, the console, or other platform-designated methods.

Device onboarding typically requires:

  • Platform account
  • Group Key
  • Available network environment
  • Compliant hardware device
  • Running client or onboarding program

Once onboarding is complete, the platform records basic device information and online status.

2. Device Identification ​

The platform needs to identify the basic capabilities of a device, such as:

  • Device type
  • System version
  • CPU / GPU / memory and other resource conditions
  • Online status
  • Runtime environment
  • Whether the device is currently available to receive tasks

This information is used for subsequent task scheduling and operation monitoring.

3. Task Assignment ​

The platform assigns suitable AI workloads to devices based on task type, device status, and resource conditions.

Different tasks have different requirements for devices. Some tasks are suitable for independent execution, while others may require more stable network connectivity, VRAM, runtime environment, or dedicated model support.

4. Task Execution ​

After receiving a task, the device runs it within the execution environment permitted by the platform and reports status, logs, or results back to the platform.

Task statuses may include:

  • Pending: awaiting assignment or execution
  • Running: currently executing
  • Completed: finished successfully
  • Failed: execution failed
  • Cancelled: cancelled

Actual statuses are subject to the platform's current implementation.

5. Result Verification ​

The platform may perform result verification, status checks, or exception handling depending on the task type.

Verification methods may include:

  • Task execution status
  • Runtime logs
  • Output results
  • Report-back time
  • Device online records
  • Platform-side review mechanisms

6. Revenue Recording ​

When a device completes a valid task recognized by the platform, the platform records the corresponding contribution data.

Revenue may be affected by the following factors:

  • Task type
  • Task completion volume
  • Device performance
  • Online stability
  • Task quality
  • Platform settlement rules

This document does not provide any fixed revenue commitment. Specific rules are subject to platform announcements, console displays, or formal agreements.